On Sunday 31 October 2004 01:55, Stefano Mazzocchi wrote: > there are a few projects that gump builds that are not ASF projects and > are not used by any ASF project. I think the ASF already has enough > things to build for ourselves and gump is not a public service. > > I personally think that it is abusive for comitters to use their access > to add projects that are not required. > > Examples of such projects are Barcode4j, Antworks, Smartfrog, but I'm > sure I can found more (and, in fact, I'll write some code to outline > those and automate the checks). > > I propose that we remove those projects from the gump.xml profile that > is ran on brutus (we can keep the descriptors there, that doesn't hurt) > but I would like to remove all those "leaves" projects from using > cpu/disk space. > > WTDY?
What Think Do I? :o) First a bit off-topic; isn't this also becoming a scalability issue problem for the ASF model of oversight as well? The more external dependencies that are introduced into the codebase, the higher the risk that non-ASF projects are introducing trojan horses and other security-related issues. There seems to be various levels of desire among ASF committers to make external dependencies, even choosing external ones over viable ASF ones, often with the argument of level of community activity. Anyway, that aside, I think that as long as Gump is not a P2P federation of externally provided CPU resources, I don't see a reason why ASF should build any leaf nodes that no ASF projects are dependent upon. Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
