On Wed, Mar 13, 2013 at 2:28 PM, Karen Coyle <[email protected]> wrote:
> So we are dependent > on someone (Anand?) to give privileges *individually* which just doesn't > scale. I'm pretty sure that's the way it works. > This is why I was hoping that it would be possible to create a > directory that was by definition public write (the way that the bib > pages are). That would give us a playground where privileges are not an > issue. > With the amount of Google juice OpenLibrary has it already attracts a fair amount of spam, even after requiring an account, so they may be reluctant to do that. > > If hosting on OpenLibrary isn't feasible, my second choice would > > probably be to flip the bit to turn on the Github wiki at > > https://github.com/internetarchive/openlibrary/wiki You can see what it > > would look like at my fork here: > > https://github.com/tfmorris/openlibrary/wiki This would have the > > advantage of being fully distributed with the ability to fork & merge as > > well as redundancy and distributed control by virtue of the multiple > copies. > > Again, how would privileges get set? Would someone have to give > privileges individually? > I believe I've got that set so that anyone can edit it. Were you not able to? It is possible to restrict edits to just collaborators (ie project members), but I've got that turned off (I thought). Tom
_______________________________________________ Ol-tech mailing list [email protected] http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech To unsubscribe from this mailing list, send email to [email protected]
