• Intro
• Downloads
• Community
• Development
• News
• TALK

Wiki gardeners

This group was originally founded as a focusing point for the migration and editing of content from an older wiki to this one.

Its current mission is to be a centralized organization point for all Maemo wiki related improvement efforts.

Right now, the primary goal of this group is to ensure that we maintain a good editorial standard for content which gets added to the wiki, that the organisation and linking of the articles on the wiki is coherent, and that generally, the wiki is a nice place for Maemo users and developers to come to find information.

Maemo Wiki Principles

• Page names should be short and to the point. The page name is a label, not a sentence. No more "How to EASILY boot from an MMC Card". "MMC card boot" (or similar) will do.
  • Page names should also be capitalized like a sentence instead of a title ("MMC card boot", not "MMC Card Boot") and should contain spaces ("MMC card boot", not "MMCCardBoot").
• The front page must remain clean. Each section will have 4 to 5 front-page links, with a category link (hidden behind "More topics") to all of the other pages in the category. We can use subcategories too, for sections that get cumbersome (personal opinion of cumbersome: more than 20 articles).
• Pages should be split or consolidated so that they are roughly 1 to 2 browser page-lengths long. There's nothing worse than a 3-sentence wiki-page, or a 20-page document.
• We will link to the content outside the wiki which someone browsing to the wiki is likely to want to find.

Tasks

This is a summary of the group's current tasks. This list will evolve over time.

• Get the word out.
• Bring in people to help with the group's projects and begin defining task forces with certain realms of responsibility.

Pruning

• Edit old pages to update them for Fremantle
• Start grouping Diablo and Brora information together behind version-specific sections, to clean up primary navigation path for visitors
• Identify pages with information that could be organised differently, rewritten or edited

Weeding

• Identify duplicate or redundant pages, and merge them
• Create a list of pages here which people can merge if they have a few minutes
  • Companies in Maemo development and Maemo professionals (same thing)
  • Networking (Diablo), USB networking Bluetooth networking, USB to ethernet networking - suggest merging to a new Networking article or folding Networking (Diablo) into the USB and Bluetooth articles.
  • Maemo5 101, Maemo For Beginners, Os2008 101, and possibly customizing Maemo
  • Q&A - SDK and Scratchbox, Q&A Porting to Fremantle and Autobuilder FAQ - I suggest merging these to a developer FAQ (name "Developer Frequently Asked Questions", and a redirect from "Developer FAQ")
  • Questions and answers, Frequently asked questions, Troubleshooting - these should be merged to a user FAQ (with the name "Frequently Asked Questions")

Landscaping

• Revisit navigation in wiki for the top 3 levels of links (front page, and pages linked to from front page) to improve discoverability of useful documentation, tutorials and team workspaces.
• Help various teams using wiki for web content to make their content ore visible & better organised (Sprints, Mer, etc)
• Ensure that all orphaned pages are linked from somewhere or deleted.

Candidates for merging or organising under a hierarchy:

• Everything to do with the organisation of maemo.org staff - sprints, roles, bios
• New users pages, including Maemo basics, Questions and answers, Frequently asked questions, setting up an email account, and so on. Basic subjects gathered under here would be thinks like getting started with the N810 and N900, migrating old data to new devices, simple stuff like playing media, typing special characters, user interface quirks, using wifi in universities, ...
• Project roadmap - bringing together the 100 days initiative, the 2010 agenda, Objectives and Tasks
• Mer - they're in pretty good shape already, but should move from "Hot topics" to "Community" or "Developers", I think.
• Community Council - governance, role, election material, rules, news, etc
• Summer of Code participation - past participations, link to project pages, description of who's who (admins, students), collect reports on completed projects...

Planting

• See Documentation wishlist

Templates

• Put together a set of templates to assist in the categorization, tagging and expansion of articles, and help maintain a uniform style and format across the wiki.
• Set up a template reference page.
• Categorize all templates.

Categorization

• Revise categories to aid the organization of articles.
• Place articles into the correct categories.
• Put together an categorical index with cover content/article.

Members

New members should simply add their name to the bottom of the list and jump right into the project.

1. generalantilles 21:41, 2 June 2008 (UTC)
2. dneary 10:16, 3 June 2008 (UTC)
3. qgil 19:45, 4 June 2008 (UTC)
4. lcuk 22:27, 4 June 2008 (UTC)
5. jaffa 07:09, 5 June 2008 (UTC)
6. andrewfblack 10:36, 11 June 2008 (UTC)
7. Baloo 22:26, 19 July 2008 (UTC)
8. Tim Samoff 02:37, 24 July 2008 (UTC)
9. Sebastian Lauwers 00:32, 13 September 2008 (UTC)
10. Qole June 2009
11. Randall Arnold 19:24, 14 October 2009 (UTC)
12. Kai Thomsen 19:36, 14 October 2009 (UTC)
13. Tom "tom2" Waelti 20:20, 14 October 2009 (UTC)
14. mve 19:10, 23 October 2009 (UTC)
15. guaka 10:40, 26 October 2009 (UTC)