Merge with Drupal.org redesign theme implementers group

Events happening in the community are now at Drupal community events on www.drupal.org.
drumm's picture

3+ groups for the redesign is confusing and people have a hard time locating information. Infrastructure issues should be handled in the Drupal.org issue queue anyway.

  1. Make sure all posts in this group are cross-posted.
  2. Remove this group.
  3. Rename Drupal.org redesign theme implementers to Drupal.org redesign implementors.

Any objections?

Comments

We need more infrastructure team members

Amazon's picture

The Drupal.org infrastructure is closely guarded. But we need more infrastructure help, particularly to match the increased demand for infrastructure in the re-design. This group aims to recruit and train more infrastructure team members.

We've added central authentication to http://infrastructure.drupal.org. But we don't have a process for sharing sanitized dumps of drupal.org, the ability to create staging databases without making a request from the infrastructure production team, nor do we have the ability to bring up web environments for staging efforts. While this has been done in the past, on a case by case basis, we need to make staging infrastructure more available.

Until we have more staging and development infrastructure contributors this group needs to exist.

Kieran

Drupal community adventure guide, Acquia Inc.
Drupal events, Drupal.org redesign

I went ahead and changed the

drumm's picture

I went ahead and changed the orange box to focus this group.

We're at the Drupal.org redesign sprint

christefano's picture

We're at the Drupal.org redesign sprint at MIT and would like to close this group (Drupal.org Redesign Infrastructure Team) for good. Placing a sticky post at on the group home page may not be enough to prevent unwanted posts from being posted here. What's the procedure for moving posts or subscriptions to the implementers group?

I don't want to close this group

Amazon's picture

This group still hasn't served it's purpose. That was to have infrastructure folks available to help with the redesign. We still don't have a single person dedicated to providing infrastructure support for the redesign.

For example, dosprint.org went off-line and we didn't have anyone to ask to bring it back so that the sprinters had live sites this morning. We need people other than the Drupal.org production team to provide this kind of assistance.

Kieran

Drupal community adventure guide, Acquia Inc.
Drupal events, Drupal.org redesign

Drupal.org Improvements

Group categories

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: