design for access privileges for 1.0

[GoogleCodeExporter]

User privileges needs to be modeled some way for both users schema and the
web UI.

The plan is to initially assign a 32-bit integer per user that has a bit
for each controllable privilege that we want to control per user.  An admin
user would have all these 32-bits set.  A normal user would have only a
small subset of these bits set.

Specification (see comments for further fields):

Bit | Default |       Description 
----+---------+----------------------------
0   | 0       | Allow to create new users
1   | 0       | Allow to edit other users
2   | 1       | Allow to edit wiki pages
3   | 1       | Allow delegation of other people's tasks
4   | 1       | Allow modification of other people's tasks

Original issue reported on code.google.com by [email protected] on 6 Dec 2007 at 9:40

[GoogleCodeExporter]

Original comment by [email protected] on 6 Dec 2007 at 9:40

• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

As a rule of thumb for reviewing the privileges, a privilege set of all zeros 
should
never be allowed to make any DB modifications.

Original comment by [email protected] on 6 Dec 2007 at 10:14

[GoogleCodeExporter]

Pushing to release 1.1.  Current user="admin" check should be fine in the first
version.  The current implementation will allow for relatively easy addition of 
more
fine-grained access control.

Original comment by [email protected] on 9 Dec 2007 at 11:36

• Added labels: Component-Logic, Milestone-Release1.1
• Removed labels: Milestone-Release1.0

[GoogleCodeExporter]

Pushing yet again to a later release.  Not needed yet.

Original comment by [email protected] on 31 Dec 2007 at 6:06

• Added labels: Milestone-Release1.2
• Removed labels: Milestone-Release1.1