|
⇤ ← Revision 1 as of 2019-01-06 16:36:59
Size: 3546
Comment: Migrate page from DebConf wiki
|
Size: 2984
Comment: modernize
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| Line 6: | Line 5: |
| Line 8: | Line 6: |
* debian-sponsors Git repository (Please send email to sponsors@debconf.org, with your Alioth info, and request to join the project in Alioth) * Git URL: git+ssh://git.debian.org/git/debian-sponsors/debian-sponsors.git * Request Tracker (RT) at [http://rt.debconf.org rt.debconf.org]. Mails to sponsors@debconf.org go there and from there to the mailing list. For anything else the use of RT is optional. If you like it, use it. If you don't, you don't have to. * To get RT access, contact sponsors@debconf.org with a request. |
* debian-sponsors Git repository (Please send email to sponsors@debconf.org, with your Salsa info) * Git URL: `git@salsa.debian.org:debconf-team/sponsors/sponsors.git` |
| Line 19: | Line 10: |
| '''You should avoid saying sponsors' names publically until they have committed. This includes not including names in the svn or git commit logs.''' | '''You should avoid saying sponsors' names publically until they have committed.''' |
| Line 22: | Line 13: |
* check the sponsors-table file in order to see the status of the potential sponsor and adresses * send an email with a cover letter and the brochure (cover letter is optional as long as you include it in the body of your email). * the cover letter is available as [http://anonscm.debian.org/viewvc/debconf-data/dc13/cover-letter/ TeX sources] or [http://anonscm.debian.org/viewvc/debconf-data/dc13/script/ email] in the SVN repository * the brochure is available as [http://anonscm.debian.org/viewvc/debconf-data/dc13/sponsorship-brochure/ TeX sources] in the SVN repository or as [http://media.debconf.org/dc13/ PDF] on media.debconf.org * update the sponsors-table |
* check the files in the current year's sponsors-list directory in the git repository in order to see the status of the potential sponsor and addresses * send an email to the contact and CC sponsors@debconf.org. This email should include: * a modified version of the email template for the current year (available in the git repository) * the current year's sponsorship flyer (usually available at https://media.debconf.org/dcYY/fundraising/debconfYY_sponsorship_flyer_en.pdf) * a link to the current year's sponsorship brochure (usually available at https://media.debconf.org/dcYY/fundraising/debconfYY_sponsorship_brochure_en.pdf) * update the sponsor file in git |
| Line 30: | Line 21: |
| * check the sponsors-table file in order to see the status. * update the sponsors-table |
* check the sponsor file in order to see the status. * update the sponsor file when you communicate with them |
| Line 59: | Line 50: |
== See also == [https://debian-administration.org/users/rkd/weblog/8 DebConf Fundraising] by Pablo Duboue, DebConf10 fundraising team |
General resources
- IRC: #debconf-sponsors@oftc
mailing list:debconf-sponsors-team@lists.debian.org
debian-sponsors Git repository (Please send email to sponsors@debconf.org, with your Salsa info)
Git URL: git@salsa.debian.org:debconf-team/sponsors/sponsors.git
How to do the sponsor file: https://wiki.debconf.org/wiki/Sponsors-list-format-2.0
You should avoid saying sponsors' names publically until they have committed.
Initial contact
- check the files in the current year's sponsors-list directory in the git repository in order to see the status of the potential sponsor and addresses
send an email to the contact and CC sponsors@debconf.org. This email should include:
- a modified version of the email template for the current year (available in the git repository)
the current year's sponsorship flyer (usually available at https://media.debconf.org/dcYY/fundraising/debconfYY_sponsorship_flyer_en.pdf)
a link to the current year's sponsorship brochure (usually available at https://media.debconf.org/dcYY/fundraising/debconfYY_sponsorship_brochure_en.pdf)
- update the sponsor file in git
Follow-up
- check the sponsor file in order to see the status.
- update the sponsor file when you communicate with them
Finalizing the deal
- Ask for a physical mail address (invocing information), contact person, and preferably email address. Invoice media preferences (email with a pdf or post mail) Record this in git.
- Ask for a physical mail address and person (most probably our contact) to send the thank you letter and "sponsor bag" (containing a t-shirt and other items all the attendees get) after the conference
Ask for a logo to place on our website or T-Shirt, a vectorized logo graphic with transparent background (SVG is best, pdf and eps are ok).
- place a note with the confirmed amount into the sponsors-table and move the entry to the correct section
- place the sponsors logo in the correct section on the website
- Write an invoice (work with the budget folks for this - where are we going to get money sent)
- Send it via email or post
- Confirm money is well received
At the end of the conference
Send a "sponsor bag" and "thank you" letter to every sponsor, including:
- Thank you letter
- T-shirt
- conference bag
- other items given to all attendees
This is best done during the conference and not afterwards. It's much easier to pack everything during the conference and to collect the missing contact info.
Updating the sponsor-table
ALWAYS: when you add / update a sponsor's entry, add your name and the date so that we can see at a glance where things are up to. If you're pinging a company contact without responses, still list those so that we know what's going on. We don't want to flood-ping people by accident!
?Category:DebConf_ Manual