[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Debconf-team] attendee bursary status



Hi everyone,

We are one month away from Debconf and not a single person has received
confirmation about reimbursements for travel or food. This is bad due to
the nature of flight costs and travel arrangements. I hate to be gone
for a week+ and then run back in the room screaming about emergencies,
but I i think we are past the point where we should have notified people
about sponsorship requests.

For your reference, these are the different queue definitions we were
operating under:

  Queue A: - we will work on fulfilling the requests.
  Queue B: - we will work on fulfilling the requests but not necessarily
             at 100% (although we will try hard to work with you to
             ensure your attendance).

Our current budget.ods (which we know is not accurate and could be off
by ± 10k) includes funding Queue A 100%, funding for food for everyone
who requested it, and leaves us in an OK state (-$4138). This is before
any requests for funds from Debian. 

Can we go ahead and notify those people that they are receiving
sponsorship for travel and food? If not, why not? I think we should go
ahead, and unless someone says something in by (*spinning arbitrary
deadline wheel*) Monday, I will propose to at the global team meeting we
do this.

For Queue B we need to make some decisions. If we funded 70% of Queue B
we would be approximately -$14k. This seems like a large number to be in
the hole, so we likely would need to request money from Debian. If we
requested 20k, and funded 70% of Queue B, we would have +$5820, if we
did 100% of Queue B we would be +$1515. Remember that we are expecting
unexpected expenses. 

So this set of questions is: a. do we request an amount from debian on
the order of 20k or more (if more, what is it)?  b. do we fund x% of
Queue B? (where x would be somewhere between 70% or 100%)

Ideal world I would say lets 100% Queue B, but I dont know how to make
this decision. Its a hard one, and we've been putting it off. We need to
make this decision now.

micah


Attachment: pgpArft1cqzRi.pgp
Description: PGP signature


Reply to: