1 |
dabbott 10/02/21 22:23:41 |
2 |
|
3 |
Added: conference-funding-request.txt |
4 |
Log: |
5 |
Conference Funding blank form |
6 |
|
7 |
Revision Changes Path |
8 |
1.1 xml/htdocs/foundation/en/forms/conference-funding-request.txt |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/foundation/en/forms/conference-funding-request.txt?rev=1.1&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/foundation/en/forms/conference-funding-request.txt?rev=1.1&content-type=text/plain |
12 |
|
13 |
Index: conference-funding-request.txt |
14 |
=================================================================== |
15 |
Gentoo Foundation Conference Funding Request |
16 |
|
17 |
The purpose of this form is to allow the foundation to keep track of funding |
18 |
requests in an organized fashion, instead of having a collection of e-mails, |
19 |
IRC conversations, etc. |
20 |
|
21 |
This form has a specific format. All of the sections start at the left side of |
22 |
the form. They have a short name and a description. Insert your responses |
23 |
after the examples, one tab in. |
24 |
|
25 |
File a new bug in the Infrastructure product and assign it to |
26 |
trustees@g.o. Attach the request form, and make sure all lines are |
27 |
wrapped at 80 columns so it's easily viewable in a browser. |
28 |
|
29 |
Summary: One-line summary of your request |
30 |
|
31 |
Requesters: Names and nicks of people involved in this request. At least one |
32 |
of them must be a manager. If the foundation cannot directly purchase the |
33 |
request, the first requester will receive access to funding. |
34 |
|
35 |
Deadline (mandatory): Day Month Year. Request must be 6 weeks in advance. |
36 |
|
37 |
Priority: Urgent, High, Medium or Low (select one) |
38 |
|
39 |
Amount requested: Submitted in your local currency. |
40 |
|
41 |
Funding disbursement: Will the foundation directly purchase the items, or must |
42 |
the funds be given to a requester? If they must be given to a requester, state |
43 |
why. |
44 |
|
45 |
If the foundation is to purchase the items please email to trustees@g.o |
46 |
the delivery address and contact phone number. |
47 |
|
48 |
This information will not be public, and make a note on the bug that this has |
49 |
been done. |
50 |
|
51 |
Describe the conference, names of developers expected to attend, and the booth |
52 |
registration number if applicable. |
53 |
|
54 |
Vendors: |
55 |
|
56 |
Provide vendors name and itemised quotes. |
57 |
|
58 |
Itemized expense list: |
59 |
|
60 |
Justification: Provide any available information, conference purpose and |
61 |
goals. |
62 |
|
63 |
Supporting information: Put any additional relevant things here. Put the URL |
64 |
of the conference. |
65 |
|
66 |
The foundation requests that you provide a blog post about your experiences |
67 |
and contact the PR team to include a news item for the front page. |