-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guillaume Rousse wrote: > Ainsi parlait Denis HAVLIK : > >>+ directory for 9.0 on mirrors shows they are actually many packages >>+ there that are totally new: see enclosed list. >> >>RPM-voting is an attempt to move from the model where >>everyone contributes packages he/she likes without thinking about others >>to a model where users ask for something, and packagers do the packaging >>because someone else needs it. Of course, nothing stops the "volunteers" >>from producing packages they simply like to package too... > > What is > true however is we don't have a formal way to express a desire for a certain > package, except a mail on cooker list,
We were discussing what we could learn from Debian (before we were interrupted by the make-Mandrake-a-Debian-subproject people). Maybe one of those is a method to have a Request For Package? Should it be Club-based or not though? > nor do contributers have access on > incoming directory of ftp.linux-mandrake.com, maing uploaded packages only > accessible for Lenny. Well, that should be fixed IMHO. Such as when someone uploads an updated package which Lenny is not maintainer for (happened with gdal recently). > > >>In adition to this "customer-oriented packaging", rpm-voting also offers a >>simple mechanism for quality control, and works basically on its own with >>no need for constant supervising. > > Constant automated supervising, restricted commiting access and strict > packaging policy provides higher QA ensurance IMHO. > But Club does provide simple (thumbs up/thumbs down) positive (or negative, but cooker provides negative also ...) feedback also, which helps in maintaining packager morale ;-). > >>In short, Clubs RPM-voting is clearly superior to current "contributions" >>from users point of view, and I hope that everyone will use it in the >>future - both for "stable" releases, and for cooker. > > My point is not so much about "how" new packages are elected, neither "who" > creates them, but "where". In current situation, if someone want to package > something for mdk, either for its own needs or because someone else asked > him, he has to dig in cooker _and_ in club (BTW, is there a spec CVS > repository for club ?) No, there currently is not cvs, which would be nice. > to find if the work has already been done. And before that, one had to check 1)contrib 2)plf 3)texstar 4)ranger.dnsalias.com/mandrake 5)Danny's s site 6)Austin's site 7)thac's stuff 8)rpmfind 9)etc etc etc Club is mainly to combine all the personal sites into one package repository, so we don't end up duplicating even more work that without it. > > So i don't disagree with the voting systement, but with the content overlap. > Juste preventing new package introduction at club level would solve this > issue, and forwarding any request to contributers would solve the issue. Somehow, I think you miss the RPMs that would be randomly distributed across the internet, which all now find a place in club, and hopefully since they are all in one place, will find their way into cooker more easily. Regards, Buchan - -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+Y3WarJK6UGDSBKcRAhDbAKCwuxaX1IoPlUTg67zkLM8Wc7wn5wCeMhCw LBpRNYbOA9tB7vlUMqVQgAM= =E/rr -----END PGP SIGNATURE-----
