My job involves improving our community processes for Drupal core, and naturally this ends up back on Drupal.org a lot of the time. It'd be helpful for me to have a d.o dev site to do things like:

  • Propose small improvements to d.o. (E.g., we're currently discussing changing the kinds of issues that are counted in core issues thresholds, and the change will require an update to the Contributor Links dashboard block.)
  • Write queries that can be run against the d.o database to get metadata on contribution, issue management, etc. (Dries occasionally asks for various metrics for presentations or to inform community discussions.) In the past, I've written queries using the d.o testing profile and then worked with webchick to get them right, but she is on leave currently.
  • Etc.

Thanks for your consideration!

Comments

YesCT’s picture

YesCT CreditAttribution: YesCT commented

Me too.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented
Status: Needs review » Postponed (maintainer needs more info)

YesCT – Please upload an SSH key at https://drupal.org/user/258568/ssh-keys

xjm – your SSH access should be all set.

For random (non-destructive) queries, feel free to hop into whatever recent dev site exists. The comment file's timestamp is when the dev site was made. Drupal.org D6 dev sites sorted by creation time is

ls -ltc /var/www/dev/*-drupal.*/comment

(The server was rebuilt as part of https://drupal.org/news/130529SecurityUpdate, so everything from before that thinks it was created around then. tvn-drupal.redesign.devdrupal.org is the most recent.)

Small improvements can generally be made on any recent dev site. Everyone on that server has access to all dev sites. You can check the comment file next to htdocs for each site to see what's going on.

Larger improvements like #2013222: Add "Issue tasks" to project issues and correlate tasks with handbook documentation could use a separate dev site, which I started. This is the first Drupal.org D7 dev site buildout we've done since the server rebuild, so I'm watching it. (Smaller sites are tested and working.)

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

The dev site build did complete successfully. I'll put notes in #2013222: Add "Issue tasks" to project issues and correlate tasks with handbook documentation. In general, I like to keep dev sites per-task instead of per-person.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm commented

Thanks @drumm! That should work fine.

YesCT’s picture

YesCT CreditAttribution: YesCT commented
Status: Postponed (maintainer needs more info) » Active

key uploaded.

tvn’s picture

tvn CreditAttribution: tvn commented
Status: Active » Fixed

Added your key YesCT.
Here are some docs and tips on how to work on our dev server: https://drupal.org/node/1018084

If you are going to work on some small improvements on someone else's dev site, it's better to let that person know, so that you don't interfere with each other. You can usually figure out who requested the dev site from its comment file.

YesCT’s picture

YesCT CreditAttribution: YesCT commented

thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Component: Operating system » Servers