Spam is a concern of mine, but I think option A is not a good solution. We can't do that because then we give everyone access to the security bugs, and basically admin access in the bug tracking system in general. They can also add and change downloads on the project, and it's just too much. I think the best solution is probably B, and we will just have to watch out for abuse.
On Fri, Sep 26, 2008 at 10:38 AM, Mike Belshe <[EMAIL PROTECTED]> wrote: > My only concern is spam. > I like option A just fine. > > If we don't think spam will be an issue, B is better. > > Mike > > On Fri, Sep 26, 2008 at 9:41 AM, Evan Martin <[EMAIL PROTECTED]> wrote: > >> >> On Fri, Sep 26, 2008 at 9:37 AM, Yarin <[EMAIL PROTECTED]> wrote: >> > B) Make http://code.google.com/p/chromium/w/ world-writeable. >> > There is no official support for this by Google Code, but this should >> > be possible somehow with the help of someone from Google Code. Evan, >> > one of the Chromium project members, is investigating this. >> >> I personally like this one, but I'm willing to hear arguments otherwise. >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
