dag/kibr — Issue #9: Access control
Author: dag
Created: 2011-11-27 21:40:49+00:00
State: open
Labels: Important

* Require an account for any editing, but be permissive about what can be edited, relying on revision logs to deal with possible vandalism.
* Data that should not typically be changed can be hardcoded in the source code; e.g. grammatical classes.
* It might be necessary to restrict some edits to for example BPFK members only, such as making an experimental word official.