On Tuesday 04 March 2003 17:36, Guillaume Rousse wrote: > Ainsi parlait Denis HAVLIK : > > On Tue, 4 Mar 2003, Guillaume Rousse wrote: > > > > + > 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. > > > > I will not do so, sorry. I am very happy with the results of RPM-voting > > system, and I'm not going to do anything that could make it look like a > > "second choice" to Club Volunteers. > > I don't see what makes backporting a second-choice. Moreover, i never > pretended people should either have the right of backporting existing > package or have the right to introduce new ones. >
Ufff I don't understand what is so hard to understand ? People ask if they can have package xy . A volunteer wants to try out if he can do it. The normal situation is, that volunteer and people who ask have the same release (9.0, 8.2). They build it for that release and it will be tested with that release. If it works well it will go in done mode and people can urpmi it. full stop. Going to join CHRPM and Cooker mailinglist, advertising the package there, handle the mail load, waiting till a reply and maybe an upload comes, looking if it builds on Cooker (what a volunteer don't have to be able to test) and when rebuild it for stable , then lets test it where, rebuild if fixes are needed, waiting till upload and then rebuild. Why should it be made like this? The club is to please users and not something obvious, nobody understands. People that can't run cooker are able to help there. They are happy to help and get hopefully good feedback and people are happy with bleeding edge or rarely packaged applications. Extending cooker-contrib would be a nice side effect of it. Lets list the Pro and Contra I read till now: Pro: ----- happy user entry point for package maintainer money from the club !! suggestion for packages user want Contra: -------- a theoretical fear for doubled work that is not proven nor I have seen it in reality. > > On the contrary, all contributions should go trough RPM-voting system, > > which is superior to standard contributing path (automatic advertising of > > work, peer review, etc.), and the current "contributors" stuff should be > > merged with "club volunteers". > > That's not my point. I'm not arguing about the use of system x vs system y, > i'm arguing about the very point of introducing something new elsewhere > than in the develoment branch. You ask why , I would ask why should there not be new packages ? > You were refering to Debian in a previous mail, i don't think you could > introduce a new package in stable release for instance ... bad argument: Mandrake != Debian Club != main and contrib Debian has too a lot of alternative places there packages for stable are build. Why not seeing the club as collecting the different sites and enable to get all from one place with getting money from people for it. (of course not only for it, but in parts). As we are on debian. As far as I heard it is a big mess with all the different kde 3 packages for stable. A and another idea, since we speak from debian. What about make a pool of packages (If i remember right it was called orphaned ?) there source packages from club go in automatic. So it can be seen easily which packages are in club but not in main/contrib, a maintainer can pick such a package then. > > BTW, current contribution system also have automatic advertising system > (changelog list) and peer review (cooker list). reducing entry level is good to get more people in development process and this way the quality of cooker does not get worser. And please try to understand what the club is. -- Regards Steffen ____________________ counter.li.org : #296567. machine: 181800 vdr-box : 87 ____________________ Please dont CC me, since if I have replied I'll watch the tread. Both mails will be filtered to the ML-folder. Thanks
