Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


In order to improve the management of the marketing/community budget for
2017, we ask native language communities to provide the following:

1. A list of objectives you would like to pursue in 2017. Please avoid
wishful thinking, and stick to realistic objectives. A few examples:
organize a meeting with public administrations to educate them about
LibreOffice and ODF; organize a local LibreOffice Conference; reimburse
volunteers travelling around the country to present LibreOffice and ODF
at local events.

2. For each objective, provide a rationale and a sensible amount of
money. Again, we are spending donations money, and we must be extremely
cautious both with requests and with approvals. Requests missing a
rationale or easy to understand details will not be approved.

3. For requests equal or exceeding 1,000 euro, you must provide the
outline of a project, because a large amount of money is probably
covering different expenses (people, suppliers, events) and budget
approvers should be allowed to have a clear picture of what they
approve.

Examples of activities which TDF will provide a budget for:

1. community events (aimed at getting face-time for community contributors)

2. marketing activities (aimed at representing the project to the
outside world)

3. targeted projects (for instance, promoting LibreOffice in schools)

In addition, we ask you to provide a list, if any, of infrastructure
related requests, such as - for example - additional computing power or
new services for your native language community.

The idea is to keep the administrative overhead as low as possible, and
have two authorizers responsible for each budget.

TDF BoD will provide a budget bucket for marketing and one for
community. Budget requests will be associated to the relevant budget,
and then approved by budget approvers (according to the availability of
funds).

As a sample, a request could look like this:

##

We'd like to request a 2017 budget of 1000 € for community events and
1500 € for marketing.

Expenses we envision are

1. marketing: attendance at XYZ trade show to show LibreOffice to ABC
user group (700 € booth costs, 300 € for collaterals and 500 € of
travel, totalling to 1500 €),

2. community: a community weekend to discuss tasks and ideas (600 €
hotel, 100 € for snacks and 300 € travel, totalling to 1000 €).

##

Before sending any budget request, please read carefully TDF policies:

Travel: https://wiki.documentfoundation.org/TDF/Policies/Travel
Refunding: https://wiki.documentfoundation.org/TDF/Policies/Refunding
Community Refunding:
https://wiki.documentfoundation.org/TDF/Policies/Community_Refunds

Deadline for submissions is January 20, 2017, in order to have amounts
approved during FOSDEM meetings.

Submission should be sent to treasurer@documentfoundation.org.

-- 
Italo Vignoli - LibreOffice Marketing & PR
mobile/signal +39.348.5653829 - email italo@libreoffice.org
hangout/jabber italo.vignoli@gmail.com - skype italovignoli
GPG Key ID - 0xAAB8D5C0
DB75 1534 3FD0 EA5F 56B5 FDA6 DE82 934C AAB8 D5C0

-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.