Hi there, There's been a some discussion on IRC about this, but I think it makes sense to discuss this here, and hopefully at one of the IRC meetings to come. One gripe users have with CRUX are outdated ports. Here's an idea on how to improve the current situation. this is meant as a starting point for a discussion, please comment and suggest alternative ideas! Also, please note that I'm still assuming that we want to keep the 1:1 relationship maintainer : port; alternatively, we could move to a group maintenance model similar to what we do with core, where everyone can update all ports. Anyway, here's the idea: 1. write some better guidelines for users on how to submit bug reports, i.e. to set the severity high if the download is broken etc. We should encourage the users to submit updated ports to flyspray. 2. go through all the "outdated ports" requests at the casual IRC meetings. We should have a way for maintainers to day "I'm working on this", or "I won't have the time soon, please 'causual meeting guys' look at it". I'd suggest that for trivial updates, it's okay to have another maintainer's acknowledge to commit the port; however we shouldn't ack changes of ports we didn't test. For major changes, I'd always commit it back to Flyspray and ask the original maintainer to comment, and the submitter to test. 3. for ports with non-working downloads, there should probably be a separate policy; I'd say every maintainer should be allowed to commit a Pkgfile with an updated URL if .md5sum isn't touched. However, we have to find a way to avoid duplicate work (i.e. by adding a note on flyspray, stating "I'm looking into that"). If there's a version bump needed, I'd again like to see some acknowledge step of that change. Since it take up to a week to the next IRC meeting, it might make sense to post these to the mailing list. There's a number of open points: - review methods for these changes - how long should one wait before touching other people's ports - will we maintainer accept that others update our ports? - will the users register a flyspray account to report outdated versions? Alternatively, we could use a separate tracking system for outdated ports Looking forward to hearing your comments. Best wishes, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch