Strategic working group/needs

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Strategic working group/needs
Afrikaans Alemannisch aragonés asturianu azərbaycanca Bahasa Indonesia Bahasa Melayu Bân-lâm-gú Basa Jawa Baso Minangkabau bosanski brezhoneg català čeština dansk Deutsch eesti English español Esperanto estremeñu euskara français Frysk Gaeilge Gàidhlig galego Hausa hrvatski Igbo interlingua Interlingue isiXhosa isiZulu íslenska italiano Kiswahili Kreyòl ayisyen kréyòl gwadloupéyen kurdî latviešu Lëtzebuergesch lietuvių magyar Malagasy Malti Nederlands Nedersaksies norsk norsk nynorsk occitan Oromoo oʻzbekcha/ўзбекча Plattdüütsch polski português português do Brasil română shqip slovenčina slovenščina Soomaaliga suomi svenska Tiếng Việt Türkçe Vahcuengh vèneto Wolof Yorùbá Zazaki српски / srpski беларуская български қазақша македонски монгол русский тоҷикӣ українська Ελληνικά Հայերեն ქართული नेपाली मराठी हिन्दी অসমীয়া বাংলা ਪੰਜਾਬੀ ગુજરાતી ଓଡ଼ିଆ தமிழ் తెలుగు ಕನ್ನಡ മലയാളം සිංහල ไทย မြန်မာဘာသာ ລາວ ភាសាខ្មែរ ⵜⴰⵎⴰⵣⵉⵖⵜ አማርኛ 한국어 日本語 中文(简体)‎ 吴语 粵語 中文(繁體)‎ ייִדיש עברית اردو العربية پښتو سنڌي فارسی ދިވެހިބަސް

To start, what do we all think are the priorities and needs. My suggestion is to brainstorm, open ended without critique.

  • What needs budgeting / funding? (to inform the sections below)
    • Estimates for future expenditures on existing line items (e.g: hardware, events, legal/accountancy)
    • What should OSMF be doing that it currently isn't? How would it benefit the community?
    • For which of the above would OSMF funding be appropriate and the best use of resources?
    • Which can be better funded/resourced by the community itself, or local chapters?

Generic OSM(F) needs

  • Legal
    • Consultancy to maintain and translate license
    • Consultancy to fight breach of license
    • Corporate users FAQ for new license usage
    • Consultancy to verify license compliance with national laws
    • "Making" donated data compliant with OSM license
  • Data privacy
    • Auditing role, which user data and geo-information can be captured
  • Operational
    • Establishing and working with service levels to encourage corporate usage (eventually a business idea to have OpenStreetMap Ltd that runs the same service with service levels and professional services like MySQL)
  • Stimulation of adoption
    • Developer awards
    • "Certified" programs to establish quality professional services around OSM
    • Hall of Fame for applications based on OSM, regions with excellent coverage, interesting derived maps
  • Sponsored Research & Development projects
    • Preventive recognition of false data manipulation
    • Quality assurance mechanisms to "certify" (important) roads and amenities
  • Professional services
    • Implementation of donated geodata
    • Quality assurance for OSM documentation
  • Communication
    •  ??

Operational fundraising needs

  • A summary paper for funders
    • explaining the OpenStreetMap project
    • explaining what happens to donations
    • describing success stories like Haiti
    • statistics of the OpenStreetMap project per region
    • extrapolation of how OpenStreetMap might evolve per region
    • describing the place where funders are presented
    • "wishlist" for projects that OpenStreetMap would like to execute but are on hold due to lack of resources (with money requirements by projects)
  • Facilitating donations
    • Donation receipts
    • Easy accessable donation web page - seperated for individuals and for corporations
    • Different payment systems
    • Offering of separate projects for targeted donations
    • Easily accessable Hall of Fame for funders/donors
  • Incentive ideas for donations
    • Hall of Fame
    • Projects/Initiatives called after key funders

Financial needs that cannot be fixed by volunteer hours

  • Hardware
  • Travel
  • Government Fees

Benchmarks