<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Matthew,     I can see how it could go that way.  But I can also see how Launchpad can act as a filter between editors and contributors.  One doesn't HAVE to accept contributors to the ranks of the team.  However, those that are or will be long time contributors might just as well be called editors.  And, as with any team, there can be leadership, and controls on those who have been welcomed to the ranks of editor.  I think, perhaps, at this time there's little evidence that it is being abused or needs to be changed. Craig Tyche Matthew East wrote: <blockquote cite="mid:3bd91160810250626n3e8a86aw22d8ebc4ea448298@mail.gmail.com" type="cite"> <pre wrap="">On Sat, Oct 25, 2008 at 1:54 PM, Nick Ali <a class="moz-txt-link-rfc2396E" href="mailto:nali@ubuntu.com"><nali@ubuntu.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Matthew East wrote: </pre> <blockquote type="cite"> <pre wrap="">If the ubuntu-fridge team is for editors, then shouldn't the permission structure be that anyone can log in with their Launchpad id, and then the members ubuntu-fridge team can review and approve the story? If contributors have to join the ubuntu-fridge team, then that kind of misses the point in distinguishing between contributors and editors. </pre> </blockquote> <pre wrap="">The way Fridge <-> LP integration is set up right now, joining the ubuntu-fridge team makes you a contributor. The editor permissions are given on the Fridge backend. </pre> </blockquote> <pre wrap=""> Yes, I see that. I was just making the point that it doesn't make much sense... It shouldn't be necessary to join a team to be a contributor, and making it necessary also makes the team itself redundant, because there is now no team of editors. </pre> </blockquote> </body> </html>