Archive:Fundraising 2009

Contact people

Unless otherwise noted, these people can be contacted through flastnamewikimedia.org.

Anything

• Rand Montoya

Technology

• Tomasz Finc
• Fred Vassard

Translations, other language pages

• Casey Brown, mecaseybrown.org
• Alex Zariv, az1568gmail.com

OTRS

• Anya Shyrokova
• Ryan, rjd0060.wikigmail.com

To-do

See Wikimedia:To-do#Fundraising-related.

Translations

Publishing instructions

It's best to use a browser with tabs for this.

1. Open the English source (for example: core messages)
2. Open the translation in a tab next to the English pages.
3. Open up all the pages using the links below, they'll auto-fill the English source (or last year's translation for the footer) and open up the "destination".
4. Fill in the pages with the translations, for the most part they're in the proper sections. However...
   • "Ways to Give" (other-ways-link) and "Help protect it, now." (story-text-link) are two that are in "Other lines to translate"
   • non-profit-text, give-to-chapter-text, and validation-error-minimum should be in last year's page if it exists (Donate/Now/xx)
   • If we don't have a translation for something, leave it in English. There will be another request soon for the missing pieces.
5. Some specific "localizations" to keep in mind.
   • Links to FAQ/en, Chapters/en, Donate/Donor Privacy, Ways to Give/en, Stories2/en, etc. should link to the English pages.
   • Links to Special:ContributionHistory and DonateNonJS/en should link to translated pages (just add the language code for the special page; change DonateNonJS to Donate/Now/xx)
   • Currency should use something fitting for the language (it might also be on last year's page). Check Wikipedia to see what countries the language is common in and see if we support an applicable currency. If not, leave it in USD. If you notice that the country is on the poorer side, lower the default USD currencies.
6. CentralNotices. There are a lot.
   • Be sure to change "Wikipedia" in the local language to {{SITENAME}}. If it looks too complicated for you (weird script, seems like the letters at the end are different, etc.), leave a message for Alex or Casey.
   • Lowercase the words... make your best judgement by looking at what they do with "Wikipedia Forever" in Phase 3. Don't capitalize them by hand, use {{subst:lc:}} – a character may look like a Latin one, but could actually be something different.
7. Smile at your work, then move on to the next language.

Reminders for next year

At the moment, this is a bit of a whining list. However, the points raised on here are important and will be converted into something more clear when the fundraiser's over. Please expand this list.

1. Don't rush. Start putting things together earlier. If a deadline is nastily approaching, change it.
2. Do things properly with thought-out rationales — don't just redirect last year's page to the new page, move all of the pages at once (either with a bot or script) so we can keep them around. You never know when we'll need them again, either for translations, code, or just to see what last year was like.
3. Don't reinvent the wheel.
4. Communication amongst the team members could be better. A public fundraising channel on IRC is the best solution (we had something like this in 2008)... private things can be moved to IM or PM.
5. Use a testing platform/site (dev.donate.wikimedia.org) that's actually like the final destination... create draft notices *in* CentralNotice, so we don't have to re-invent things.
6. Numbers in the translation request are helpful (like in last year's request)
7. Quadruple^nth check that you have all the strings included in the translation request.
8. If we're going to have a link within a string, make sure that that's noted in the translation request.
9. Have working drafts available. Screenshots are better than nothing, but a working demo is <3.
10. Community feedback was weird this year: the beginning (donation buttons, etc.) was full of it and then the final result (WIKIPEDIA FOREVER) was just handed to the community without much say in the matter.
11. Be more diligent in responding to translator questions.
12. Staggered launches worked great.
13. Create a separate notice template with all the shared pieces that are specific to this fundraiser. (all donate-url's, all Support Wikipedia's, etc.)
14. Communal To do list worked well.
15. Cross-browser checking *while developing*.
16. Don't go half-way on the Wikipedia vs. Sister projects issue, it just leads to confusion.
17. Don't piss of the chapters.
18. Reuse. Multiple pages with exactly the same thousand characters (save for a few small changes) should be avoided (e.g. Support Wikipedia/en & Support Wikipedia2/en... but it could be even better, like just saying "if the page name starts with Support Wikipedia2, show these strings; if it doesn't, show these")

    An extension of this is stuff like Donate/Benefactors/en and Benefactors.

19. Making the page look like a wiki is b.a.d.

    Ugly page title.

    People are more likely to try to leave feedback on talk pages, get accounts to translate, etc. We didn't have these issues in the past.

    Did I mention ugly? ;-)

    ...

20. If you're going to use translations on another wiki, make sure those translations are kept up to date. (*cough*payments.wm.o*cough*) There are many ways to do this, but it should be an automated way like scary transclusions or a bot.
21. Don't use two templates that do the same thing. Merge them. (c.f. Template:2009/Donate-header/en, Template:2009/Donate-banner/en)
22. The fundraiser occurs during two big holidays: Thanksgiving and Christmas/Hanukkah. The world shouldn't end because people go away – we need to plan for that.
23. If you're too busy to make the changes, make it possible for someone else to do them. (i.e. updating extension codes on SVN to point to the correct pages)
24. The Launch feedback and Alternative banners pages worked well, but they should be easier to get to from Foundationwiki (people jump to the talk pages and reach a dead-end).
25. I liked how Meta-Wiki's sitenotice pointed people to the fundraising pages.
26. The fundraiser runs on CentralNotice, the bugs should be fixed and the extension should be cleaned up.
27. Before announcing any major fundraising campaign or slogan, register the domain first.
28. Not many people enjoy BEING SHOUTED AT. (eg. no caps lock)
29. ...