Task:Consolidation of Extras
| Line 2: | Line 2: | ||
The Extras repository needs to become the single reference for developers willing to reach end users at large. | The Extras repository needs to become the single reference for developers willing to reach end users at large. | ||
| + | == Extras Process == | ||
| + | {{main|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). | * 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. | ** 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. | ||
Revision as of 12:06, 30 June 2008
 |
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.
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.
"Application Store"
- Use gronmayer's scripts to create a web site that merges applications from all known repositories into a single list and lets you browse them with MicroB using HTML UI similar to N-Gage, Apple Store, etc. While it sounds ambitious, it is not difficult to do, as we always have app descriptions and icons (form .deb files) and we also have screenshots for apps hosted at Garage. Reformatting this data in a format that can be nicely presented in tablet browser is not difficult.
- Effectively replace "itTSS" with this website.
- Make sure that all applications which are actually available in the repositories can be found in the Maemo.org downloads section.
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)