Task:Consolidation of Extras

This article is continued discussion from the maemo.org brainstorm
Please see the 100 Days agenda for more.
This is an ongoing task, planned to be completed during the current maemo.org development sprint. Any help is appreciated!
Please see the talk page for discussion.

The Extras repository needs to become the single reference for developers willing to reach end users at large.

[edit] Consolidation of wiki content

Extras information is scattered over several pages, and needs to be consolidated. A list of pages that should be merged is:

[edit] Extras Process

Main article: Extras repository process definition

  • Address the issues with current Extras acceptance and put together a plan for streamlining the acceptance system for Extras(-devel), (not necessarily easier or less stringent, but more straightforward and clear).
    • Clearly document the steps required to gain entry. Some sort of "Maemo Software Distribution Guide" (I know we already have something like this up, but make it prominent and bring it up to speed on everything) that the community (and maemo.org) can point developers to is important.
  • Lay out the groundwork for a peer-review system for Extras acceptance (or devel to Extras promotion) to help ensure good quality assurance on its packages.

[edit] Social Engineering

  • Put the pressure on developers:
    • Encourage developers not using a repository to package their applications and push them to Extras(-devel), and get developers with 3rd-party repositories to close them down and push their stuff into Extras(-devel).
    • Encourage developers to follow proper packaging guidelines (based on the draft here).
    • Encourage developers launching applications on Downloads to include as much information about the application as possible (screenshots, good descriptions, good changelogs).

At the end of the 100 Days direct uploads to extras should be disabled and use the promotion interface instead. --qgil 07:34, 10 June 2008 (UTC)