Closed (fixed)
Project:
Groups.drupal.org
Component:
Other
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
23 Mar 2012 at 22:30 UTC
Updated:
21 Aug 2014 at 21:00 UTC
Jump to comment: Most recent
I have talked with greggles about helping with g.d.o. administration, and I understand I will need SSH and Jenkins access to do that. My SSH key is here:
http://drupal.org/ssh-keys/user/109890/378/edit
I believe I would need access to both groups.staging.devdrupal.org for testing changes and groups.drupal.org for applying changes. Here's an example issue on which I would like to help:
Comments
Comment #1
gregglesConfirmed. Thanks, sreynen!
Comment #2
coltrane+1
sreynen is a trustworthy and more than capable person. I've worked with him on DrupalCamps and DrupalCon Denver and also seen his great work in the project issue queue.
Comment #3
drummI sent the LDAP request in.
Comment #4
drummYour LDAP account is created any you should be able to ssh to util, scratchvm (for staging), and stagingvm (for dev).
I don't know if you already have plans, but something good to start with is #1074224: Redesign groups homepage for authenticated users.. This already has a dev site on stagingvm. See full info on dev sites at http://drupal.org/node/1018084. If you are looking for something more mundane but still important, we can do a new dev site to test routine module upgrades.
To get you ready to ramp up with Jenkins, SSH to util.drupal.org and run
/usr/sbin/slappasswd > slappasswd.out, which is setting your LDAP password. Once you have done that, follow up here and we'll ask the OSL to activate it.Comment #5
sreynen commentedI have set my LDAP password on util.drupal.org.
Comment #6
drummI put that request in, OSL #20837.
Comment #7
drummYour access should be all set. Each Jenkins job has an ACL, so we'll probably find some that need you added, which is quickly doable. I think the best way to get trained up is to do a real deployment. We do have some documentation at http://drupal.org/node/1274650.