Ainsi parlait Denis HAVLIK :
> On Tue, 4 Mar 2003, Guillaume Rousse wrote:
>
> + Note if club restrict itself on backporting stuff from cooker contrib and
> main + to stable release, and forward new package introduction request to
> either + cooker or PLF (non-free stuff).
>
> Club does not restrict its volunteers in this way.
That's the reason of duplicated work.
> If there is demand for an aplication, and one of the volunteers (folks who
> are allowed to upload stuff) builds it, he/she can upload it and put the
> pack in "testing" status imediately. When testing is done, and the
> users are happy, he can move the packs to "done" area.
> Uploading for cooker contribs too is recomended, but I have no mean to
> enforce this.
Yes you can: just prevent new packages to appears by checking against main and
contrib in cooker branch. This will force them to either forward their
request to contributers, or ask for a contributer status themselves.
> There is absolutely no control on "what's uploaded" on my side, but
> volunteers need to pas a test before getting upload permissions, and we
> can also revoke the permission in case they start producing bad packs.
Same for contributers (aka: people with an account on klama)
> This is quite close to Debian way of doing things, and IMO much better
> than the system where one person is supposed to check all incoming
> packs...
I guess you're refering to the past when Lenny was alone. This isn't true
anymore.
--
All components become obsolete.
-- Murphy's Computer Laws n�8
