On 2009-08-11T19:21:48, Greg Freemyer
At a minimum it should be download activity that marks a project inactive, not packager activity. Even better a lack of both downloads and packager activity would be the best indicator.
The details of the method used to determine liveliness can be discussed further. Please don't argue about the color yet, lets first decide whether the bike shed gets build or not ;-) The key issue which needs addressing here is that the outdated/unused projects hog build service resources, which makes it impossibly slow to use for more active projects - the turn-around times can measure days if your unlucky, which is just not acceptable.
Also, is there a way to significantly drop the priority of these packages in the build sequence instead of totally shutting them down? Maybe have a "green" server that does not generate lots of heat just for compiling these low priority jobs?
That would also work of course. Adjusting the priority based on the commit activity, with a sliding scale or something. Just using the download frequency is not sufficient; that works for long-term trends and identifying projects which may be prunable, but the developer sitting there trying to build the next revision of a new project (which hasn't been downloaded much yet) is going to be throughly annoyed. Regards, Lars -- Architect Storage/HA, OPS Engineering, Novell, Inc. SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org