After looking at http://drupal.org/node/334785 (Drupal.org Teams) and http://drupal.org/node/319783 (Permissions assigned to Drupal.org roles) it seems there's some confusion (in the docs) about clearly delineating the differences between the "site maintainer" and "webmaster" teams/roles. For example, "webmaster" isn't even listed on 319783.
"Infrastructure" seems clearly defined in 334785 (webmaster + shell, I'm assuming), but we could definitely use a lot of clarification in the docs. I'll work on updating those docs once I can see what permissions are assigned to what roles on d.o.
Now that I have been given extra infrastructure-ish permissions, I can see some of the /admin functionality on d.o. However, I don't have permission to see what roles I have, so I can only make some educated guesses. But I need confirmation on my guesses before I feel comfortable updating the docs:
- "site maintainers": (I think this is the role I was just assigned to) have the privileges to:
- Manage book outlines
- List and edit comments
- Edit and delete content
- Configure the feed aggregator
- Create and manage image galleries
- Configure “Post settings” such as teaser length, etc.
- Configure Taxonomy
- "user admin": (completely guessing on this one)
- assign roles to users
- block users
- "webmasters": have all Drupal privileges.
- "infrastructure": webmaster privileges plus shell access to the servers.
Can someone confirm my guesses are correct? Or point out where I'm wrong? Thanks!
Comments
Comment #1
vm commentedsite maintainers have user.module permissions as well.
ie: edit/delete/block user
Unless I'm in a role above site maintainer but I think not.
Comment #2
johnalbin@VeryMisunderstood: the list of permission I listed under "site maintainers" are the only permissions that I have under drupal.org/admin. That's why I assume I'm a site maintainer. You must be in an additional role. In addition to what I listed under "site maintainers", what additional links do you see on the /admin page?
I feel like a forensic analyst. :-)
From talking to several people in IRC over the past few months, its clear that many, many people don't even know what roles they belong to. Which further underscores why we need to clearly document this.
Comment #3
add1sun commentedRoles on Drupal.org
---------------------------
administrator = pretty much everything, notably they have "administer permissions" so they have complete control over the site. There are very few users with this role (like 2 dozen).
CVS administrator = control CVS accounts and such. Main perms are "administer CVS" and "administer projects". Very few users here too, maybe a dozen.
CVS user = allowed to add images for projects, basically perms to "create images". CVS account holders need this in order to use the image module with their project.(I don't know if having this role does anything more based on custom access checks or such.)
documentation maintainer = elevated rights for handbooks; mainly access to the Documentation team input format that allows the use of
<img>and<table>tags on handbook pages. They also have the "revert revisions" perm.user administrator = has the "administer users" perm which is mainly used to block spammers. Again, maybe 2 dozen of these.
site maintainer = also referred to as "webmasters." Long list of basic maintenance kinds of perms, notably it does NOT have the "administer users" perm, which is a separate role:
- has "administer nodes" perm, letting them manage all content on the site
- all perms for aggregator module (i.e. can manage Planet Drupal)
- all perms for book, comment, image_gallery, taxonomy and upload modules
Comment #4
michelleTo clarify #2.1 in the OP, user admins do not have access to roles. You need to be a full admin for that.
Michelle
Comment #5
David Naian commentedto @JohnAlbin
As the page you want to complete was initiated by me, You may get some information on a summarize page I worked for a while to get the job done.
You may take a look here: http://rumors.adaccs.at/node/64.
I did not continue because it was to difficult to get a clear overview about the different active teams due the general opinion is that they change to fast as we can followup
a documentation about.
Regards
Comment #6
avpadernoWe could at least start with listing all the possible permissions.
At the moment, I can complete the list of permissions, and show which permissions an authenticated user has.
Comment #7
Wolfflow commentedFollowing
Edit: for update link provided by @David Naian in 5# right link is: This - Drupal.org Core Teams
Comment #8
Wolfflow commentedI think this issue also refer to the design of drupal.org community general informations pages. Being out for a long time of actively contributing to documentation I think and guess that with the upcoming new Drupal.org redesign we will have a different or dedicated place for such time of general informations. So and therefore because this issue is more the 7 month old I am for mark it "by Design". Feel free to change if needed.