Re: Minutes of the Foundation Board, 1st May
- From: Max <sakanamax gmail com>
- To: Allan Day <aday gnome org>
- Cc: foundation-list <foundation-list gnome org>
- Subject: Re: Minutes of the Foundation Board, 1st May
- Date: Fri, 4 May 2018 03:44:38 +0800
Hi Allan and Board
I have some questions or suggestions to ask.
Question 1:
So the "The GNOME Foundation Travel and Reimbursable Expense Policy
[1] " will replace " Travel sponsorship [2] " or not?
Question 2:
With "The GNOME Foundation Travel and Reimbursable Expense Policy [1] "
---- for Easy Reference Guide, do travers need to give a report( Blog?
) or not?
--------- Because it doesn't list in Easy Reference Guide, but if you
have time to read the end of the page, you will see " Expense
Reporting "
Question 3:
Compare
* " Travel sponsorship [2] "
---- 45 lines 608 words ( I use wc command in linux )
and
* "The GNOME Foundation Travel and Reimbursable Expense Policy [1] "
---- 265 lines 4063 words
Do you think the traveler is easy to read, understand and know
difference env or information they must give to TC or Rosanna?
Does it make sense? if 265 lines and not many list item or give road
maps or something? ( I think it might be difficult to travelers)
Question 4:
How many staff will process the application? TC and Rosanna? or just Rosanna?
How do you think the traveler
---- They should send the application before 3 weeks? ( If they might
booking 2 weeks in advance )
-------- Sometimes, some of them send application before a week, and
some send application after the event.
------------ If the "The GNOME Foundation Travel and Reimbursable
Expense Policy [1] " too long or not easy to read, so they could not
give enough information to TC or Rosanna, how could they do?
----- if the application is long or hard to read, they will lose focus
to process,
---------for example, TC is waiting their report( because they didn't
receive the e-mail ) but traveler say " Hey, you should know my blog
already post in the world..... "
---- Is it easy to be execute by TC or Rosanna?
------ for example, if people read " Travel sponsorship [2] request
instructions " ( https://wiki.gnome.org/Travel/Request ), they will
know "Be patient, we are volunteers.".
------------ But sometimes you will receive " Hey TC, could you please
confirm my application? I already send to you for 3 days... "
------ I am afraid if the document is not easy to read, it will happen
again and again.
Still thanks board want to do things to help everyone
Max
--
[1] https://wiki.gnome.org/Foundation/TravelPolicy
[2] https://wiki.gnome.org/Travel
On Thu, May 3, 2018 at 7:54 PM, Allan Day <aday gnome org> wrote:
Germán Poo-Caamaño <gpoo gnome org> wrote:
...
FWIW, processing times for events like GUADEC are not usually processed
before the talks have been accepted. They cannot, as the speakers have
preference, and budget is limited.
That's a good point. Maybe we could look into how the budgets are
allocated for this.
There is a guideline for looking for reasonable prices. In my past
experience at the TC, among all people applying few of them actually
did their homework.
Correct me if I'm wrong, but doesn't the Travel Committee guideline
just say "find the cheapest option"?
The question the board was discussing is how to balance economy and
convenience (in other words, what counts as "reasonable"). For
example, do you have to take the cheapest flight, even if it takes
twice as long? The Foundation's staff travel policy [1] covers this.
For example, it says that it's acceptable to spend $100 extra on a
flight if it saves you 3 hours.
Regarding applicants not doing their homework, the Foundation staff
travel policy also specifies that the traveller should do a price
comparison search and save the results. Maybe this could be a way to
check whether the homework has been done or not...
Allan
--
[1] https://wiki.gnome.org/Foundation/TravelPolicy
_______________________________________________
foundation-list mailing list
foundation-list gnome org
https://mail.gnome.org/mailman/listinfo/foundation-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]