On Sep 26, 12:37 pm, Yarin [EMAIL PROTECTED] wrote:
C) Independently host another wiki at some web server.
Would cause legal issues.
Not if it's titled Unofficial Chromium Wiki and hosted on some
random dude's webspace (where some random dude is any institution
other than Google). The
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
Let's do it.
On Fri, Sep 26, 2008 at 7:47 PM, Ian Fette [EMAIL PROTECTED] wrote:
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
It's also not necessarily desirable to have dev.chromium.org world-writable.
It's an authoritative site. We need a clear distinction (somehow) between
what content is authoritative and what is not. Whatever gets put there is a
likely target for speculation and other people to pick up. Hence, we
With that metric in mind, that means Yarin's option C now sounds the
best: make a user-contributed wiki somewhere that doesn't look
official (so probably not Google Code, either).
Any proposals? I don't know what options are good.
On Fri, Sep 26, 2008 at 3:53 PM, Ian Fette [EMAIL PROTECTED]
Peter informs me I misunderstood, and that perhaps just making
http://code.google.com/p/chromium/w/list would do the job.
On Fri, Sep 26, 2008 at 4:05 PM, Evan Martin [EMAIL PROTECTED] wrote:
With that metric in mind, that means Yarin's option C now sounds the
best: make a user-contributed
