Appropedia:Fundraising/project proposals

There are many different projects that deserve support. We can make specific cases for funding on a particular project. link to concise cases for funding on separate pages.

• Upgrade servers for new features like Semantic MediaWiki.

Pay for work to be done (either internally or hiring people externally):

• Skin work
• Implementing UX & information architecture features: Appropedia:Usability grant request
• Porting work identify manageable size, dependency-free components:
  • Develop porting tools, esp for PDF and multiple image uploads
  • Porting helpers (knowledge sharing funding)
• Improve Bot work - the original Mozilla grant idea. (More suitable for a foundation grant, I think --Chriswaterguy 21:40, 13 April 2009 (UTC).)Reply[reply]
• Offline content bundles (Development funding)
• itinerant documenters (Development volunteer funding)
• student documenters for local projects (as with Arcata Marsh) (Ed funding)
• seek open license releases for valuable content (possible in connection with OLPC and/or Summer of Content).
• restructure content (along the lines of the Mozilla proposal)
• oversee development of OLPC content bundles
• pursue MoUs
• manage volunteers
• connection/PR project - engage with potential new users/stakeholders:
  • universities
  • NGOs
  • Bloggers
  • online communities
  • classes of user
• tech work

• do specific tech tasks and/or
• be responsible for all tech tasks and/or
• oversee technical work (UI, features, etc) incl managing volunteers and/or paid developers
• Improving translation tools for MediaWiki - possible joint grant proposal with other interested parties.

Writings and insights

Ten Nonprofit Funding Models^[1] talks about:

the need to understand both the donor value proposition and the recipient value proposition... (and) about all nonprofits being in two “businesses”—one related to their program activities and the other related to raising charitable “subsidies.”

Notes