<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffcc" text="#000000"> Matt Zimmerman wrote: <blockquote cite="mid:20081008080541.GE11181@perseus" type="cite"> <pre wrap="">On Mon, Oct 06, 2008 at 11:14:57AM +0100, Mark Shuttleworth wrote: </pre> <blockquote type="cite"> <pre wrap="">Matt Zimmerman wrote: </pre> <blockquote type="cite"> <pre wrap="">For my part, I think it's completely appropriate to grant Romain access to upload these packages to universe rather than a PPA. </pre> </blockquote> <pre wrap="">+1 </pre> </blockquote> <pre wrap=""> We discussed this at yesterday's technical board meeting, and decided that this case is sufficiently different from what we've dealt with in the past that further discussion with the MOTU council is appropriate. Adding extra ACLs for existing Ubuntu developers to upload specific packages in main is one thing, but in this case, the request is for someone who is not officially an Ubuntu developer to upload. This is a fairly specialized package, and it's hard to envision anything going particularly wrong with emacs-snapshot (given that it's intended to be a fast-moving snapshot of upstream), but this will set a precedent and we will need to be prepared to handle this case. I suggest we set up a conference call with the TB and the MC to discuss. </pre> </blockquote> Quite happy to join that if it can be coordinated with Claire, otherwise please just brief u-d-a on the results of the discussion and the precedent you'd like to set. I do agree that it runs the risk of inviting people to upload specific packages who have specialist skills in that upstream but no insight into the pulse and processes of Ubuntu itself. My feeling is that we should have some standard documentation which we can provide to such developers, and then a phone conversation or other interaction to establish that they have got the basics understood would be sufficient to get going. Key issues for me would be awareness of the cycle, and awareness of our emphasis on team and collaborative maintenance. Mark </body> </html>