On Fri, Jan 18, 2008 at 03:43:28PM +0100, Alessio Bolognino wrote:
On Fri 2008-01-18 16:25 , Grigorios Bouzakis wrote:
On Fri, Jan 18, 2008 at 02:50:31PM +0100, bardo wrote:
[...]
As i had also stated in my previous illiterate mail (sorry for that), IMHO yes, TU's should upload to community only packages that have high demand by users. This is also the case now for developers about uploading packages in extra too. I think i am one of the few people who dont use community anymore and that fact is one of the main reasons. The community repo has gone very big, with many high demand packages staying in unsupported, while many of the packages in community have low usage, are old projects with almost no updates for years and build in a couple of secs.
One of the worst thing a TU can do is to move a high demanded package that he doesn't use in [community]. This way he can't test it properly, and no, just trying if it runs one time, before committing it in the repo is not "proper testing".
Well, they should ask testing from the users of the application then. I clearly remember developers doing that numerous of times with many packages. Personaly, i consider developers to be the same as TU's when it comes to building packages for the repos. I am certain there are packages in extra their maintainer doesnt use. Yet they continue building them for having them available for the users. One example that can be seen in most TU application is the user stating the packages he maintains in unsupported and gonna move to community. Why should a TU move some/all of his maintained packages from unsupported and not instead grab others that have many more votes than his or take care of some already in the repo, orphans or from a TU with many maintained packages? I have to admit that many TU's follow the amount of votes principle and at the same time keep low used packages in unsupported too but others just maintain only what they want to maintain. At least a certain amount of moderation is needed on what goes to the repos. Greg