Hi, since I'm committed to annoy all the people on this list, I remind there's a useful CLC Wiki page proposal by sten here: http://clc.morpheus.net:6999/clc/tktview?tn=38 In which a internal policy for clc ports is proposed (in particular to rule out what one should do if there are problems / updates to a port he does not maintain). Extract: ### - If any download is broken; feel free to fix it. One should then courteously notify the maintainer of the port. - For all other fixes, email a patch to the maintainer. - If the fix is security-related, and the maintainer does not respond after 48 hours, commit and tag. ### Just my 2c: - If there's a security update _AND_ a maintainer know what he's doing, I'd prefer an immediate update when available instead of waiting 2 days with an unpatched system. That could go just for remote vulns or in general. - I feel very small changes could be handled by a clc member that is not the maintainer, ie when the minor version for a port changes and there are no consequences on related ports (or no related port at all). See my today sox commit[1] as an example of what I'm blabbering of. So, If anybody would like to share his point of view, feel free to reply to this thread and / or add stuff to the ticket. Regards, Simone [1] http://clc.morpheus.net:6999/clc/chngview?cn=1289 -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com