AAPG Wiki:Users
Jump to navigation
Jump to search
This article is in progress, under active development, and will change often (see all) |
The model we adopt for managing users will be informed by the governance model.
Decisions need to made on moderation before we can build out the detail for this User page.
User types or roles
User:Matt's experience is that having too many roles is difficult to manage and results in confusion and time wasting. People apply rules inconsistently, leave jobs, and do strange things. Here are some examples of roles we might apply, a sort of minimal set:
Role | Number | Authentication | User page | Privileges | Comments |
---|---|---|---|---|---|
Root | 3 | Login | No | All | The person or people who can log into the server and edit LocalSettings.php |
Administrator | 10 | Single sign-on | Yes | All | A handful of designated people who wield all power |
Moderator | 1000 | Single sign-on | Yes | Edit-plus | The editors, reviewers, moderators, SMEs |
Member | 100 k | Single sign-on | Yes | Edit | All other AAPG members |
Editor | 1 M | Wiki user account | Yes | Edit | Anyone who goes through the editor application process |
Reader | 1 B | None | No | Read | All other readers |
Automatic promotion
The software can take into account the following criteria:
- How old the user's account is (number of days since they registered)
- Their total edit count
If we need more control, then we can consider using FallgedRevs, but it is a large extension.
Other open issues and questions
- Can users see or edit the User namespace?
- Can users email each other?
- Do we populate User pages with any content, perhaps from the member database? Or do we link to another place where there are member profiles?
- Can users email each other? This might be a nice feature for members.
- Are there superusers? Who polices this? What rights do they have?
- To what extent does the community self-manage?