[maemo-developers] Repositories mess: conclusions and actions

[From: Quim Gil]

This is an invitation to resume all previous discussions about "the
repository mess" and come up with conclusions and actions. Please read
this through and have a say, specially if you are maintaining a
repository with maemo packages out of maemo.org


MISSION

To provide the simplest interface for end users to get good quality
third party software that downloads and installs flawlessly, without
compromising their default system. To provide maemo tools and
infrastructure to developers so they can check the quality of their
software, offer it to end users and promote it.


STEPS (the ones involving repositories)

- Cleaning old stuff
We plan to keep the repositories for Bora and Chinook (N800/N810) and
Gregale (770) and delete the older ones to avoid confusion (Scirocco,
Mistral...)

- Powering extras for 3rd party software
We encourage developers using the extras repository. extras is
pre-configured in the OS2008 Application Manager and users only need to
activate it manually (like i.e. Universe in Ubuntu). Nokia.com and
Tableteer are going to promote preferably applications with packages
available in extras. We plan to start testing new releases including
test cases with third party applications installed. The seamless
software update feature (upgrades via deb packages) will be also tested
considering upgrades of packages in extras...

- Improving the service around extras
There must be reasons why people have been creating their own repos
instead of joining extras. We have discussed about this in the past.
Now, make sure that whatever is missing is filed either as bug or
enhancement request in bugs.maemo.org (product Website, component
Repository). The objective is to leave you almost no excuses to keep
having your own repos, or at least no excuses to have your stable
packages in extras.

- Community governance on extras
We think the equation would work much better if the maemo community
would have control over the extras repository, filtering what has enough
quality to be there and what not. Who and how, we are totally open about
this. We consider the Quality Awareness documentation as a reference top
define quality. We don't want to give away the control of the repository
but we are happy discussing and agreeing with you the rules of a common
game. These rules would include other topics discussed in the past, like
i.e. the sections.

- extras-testing for experimentation and stabilization
If you think the previous idea makes sense, we could open then
extras-testing just to any developer having beta quality software and
willing to use the maemo infrastructure. Any developer willing to have
their packages in extras should go first through extras-testing for
review.

No deadlines, but the sooner we agree on a plan the sooner we can
execute it and the sooner it will benefit to users and developers.

-- 
Quim Gil - http://maemo.org