Allan McRae wrote: > Last time I organised this was actually a bit of a disaster. A bunch > of packages were added by the community to be cleaned up but when it > came time for TUs to review the list and make removals, not much got done... > > The current system with emails to this list with brief explanations why > packages should be removed is working well. Why not just stick with that? > > Allan
Not much got done as in there were loads of false positives and thus nothing to do, or TUs just didn't hold up their end? I would expect a deluge of false positives for something like this unless someone draws up *very* clear guidelines for volunteers to follow. As Allan stated, the current system works rather well. If you want a better system, add deletion and orphan request buttons to the AUR interface that send an email to this list automatically or, even better, create a TU dashboard for the AUR where TUs can view submitted requests, along with reasons, how long packages have been flagged out-of-date, whether the maintainer has been emailed, etc. Packages could be automatically added to the dashboard for consideration when certain conditions are met, e.g. no updates or downloads in over a year. Regards, Xyne
