Escalating privileges system

See also Escalating privileges: proposal for initial version

The administrative burden for running an Alaveteli website is high.

At the same time, a number of features have been discussed which might require some kind of authorisation levels in the website.

A Stack Overflow style system of earned points and privileges seems appropriate -- referenced, for example, in issue #9 and issue #10.

What might the system look like? As a starting point for discussion (points system designed to encourage good quality requests):

Earn points:

• fill in your profile (+1)
• make requests (+1 each for first 5)
• have a request enter a "finished" state (e.g. request successful, unsuccessful) (+3 each)
• have requests voted up (+5 each)
• play categorisation game (+5 for first 50 categorised, none after that)
• have comments voted up (+1 each)
• have a "summary of this request" type comment voted up (+3 each)

Lose points:

• have requests voted down (-2 each)
• have comments voted down (-1 each)

Privileges:

• 0 points: make one request per day
• 1 point: play the categorisation game
• 5 points: comment on requests
• 10 points: reveal emails when logged in
• 15 points: vote requests and comments up
• 20 points: make up to 20 requests per day
• 30 points: vote requests and comments down
• 50 points: ability to make identical request to multiple bodies
• 100 points: move requests from holding pen
• 200 points: full site sysadmin

Other things we may wish to open up:

• Updating the email address for an authority
• Adding the URL for an authority's publication scheme
• Adding a description for an authority
• Adding a completely new authority

These admin privs should probably fall out of scope for "full site sysadmin" granted via game playing, mainly to help the site owners abide by data protection or defamation laws:

• Editing user page or viewing users's private details: ban status, email addresses, personal statement or photo
• viewing others' requester-only / hidden requests
• setting request visibility status or permanently destroying requests
• editing or amending visibility of annotations
• editing outbound emails or title of requests
• adding / editing / deleting censor rules