[maemo-developers] Repositories mess: conclusions and actions

[From: Krischan Keitsch]

Am Mittwoch, 24. Oktober 2007 schrieb 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)
...
>
> - 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.
>
Sounds good. What kind of rules do you have in mind yet? How would the whole 
process look like?

Krischan