Not sure if this is the right spot to request. I understand that the ability to promote projects has been split from ridiculous super powers no mortal should have. Despite that, i'll apply for project-promotion power anyway ;-)
I am fully attuned to the fact that the Git migration has made the approval process much less critical for people to be contributing and collaborating, but people seeking to maintain a full project need to know their offer is being taken seriously. If they aren't showing evidence of being serious yet themselves, i'll have no problem saying try again later.
What i intend to do is link from the Peer Review group to the project applications queue and ask reviewers to look at the project expectations and coding-standards pages. (I'd appreciate someone giving me the contents of the old CVS Application Guidelines - http://drupal.org/node/59 - because if i remember correctly it was a pretty awesome code review process.) Not every review will be sufficient, i'm sure, but applicants will start to get more immediate feedback.
I will not promote any project to a full project that has not been reviewed by someone other than me, but i won't necessarily let any objection from additional reviewers put a hold on it either.
Thank you.
benjamin, agaric
Comments
Comment #1
arianek commentedsubs
Comment #2
catch+1 from me, this is a horrible bottleneck and Ben is great.
Comment #3
michelle+1 from me. Glad to see others taking up the cause. :)
Michelle
Comment #4
MGParisi commentedOpen it up
Anything else will kill drupal.
Licensee - Check
Readme - Check
Version - check
Promote page - check
Ill do that for the 500 current projects waiting approval
http://groups.drupal.org/node/139754
Comment #5
arianek commentedps. by "subs" i also meant +1 total vote of confidence in benjamin being a great person for this.
Comment #6
catchThat's enough people. I don't have administer users permission on Drupal.org any more to flip the switch. Also I think this belongs in webmasters.
Comment #7
chx commentedComment #8
chx commentedI have granted the "Git administrator" role to Ben.
Comment #9
mlncn commentedActually if someone could tell me how to use this permission that'd be great ;-)
Comment #10
catchIt looks like this permission requires 'administer users' in order to be able to actually use it. Moving back to RTBC.
Comment #11
avpadernoThe permission to administer users is required, or the user will not see the tab to make a user a vetted user, which is under
user/<uid>/edit.It is still possible to access that tab, but the user should manually write the link.
Comment #12
killes@www.drop.org commentedmlncn is now a user admin too
Comment #13
michelleSound like this is fixed, then. :)
Michelle
Comment #14
zzolo commentedPlease note that the user administration privilege is not needed. You can simply type in the URL manually: http://drupal.org/user//edit/git
See: #1076332: "Git adminstrator" role does not have enough permissions to do their job
There is currently no documentation on being a Git Administrator. This should happen (hopefully I will have time for this).
Comment #15
mlncn commentedThank you all! I did figure out that shortcut. zzolo, do you know where the Git Administrator documentation should live? i can at least start it. Thanks.
Comment #16
zzolo commentedI would suggest somewhere under this page: http://drupal.org/node/636570
Comment #17
kbell commented+1 from me too!
This bottleneck is driving away so much potential energy in the community, and at the worst possible time - right after the D7 launch and DCChicago, when there is a lot of great new energy pumping into the Community from newly-engaged developers, and we're just throwing it away. BIG thank yous to Ben et al for not letting this issue die.
-Kelly (kbell)
Comment #18
gregglesHi Kelly,
The best way to move the process along is...to move the process along. I notice you've never commented in the projectapplications queue. Perhaps you'd like to read up on the process and then dive in