Drupal.org redesign plan for the Drupal Association

The Drupal redesign needs several infrastructure managers to help manage testing sites for redesign themers and redesign developers. A Virtual Machine will be provided to the infrastructure managers. You will be given access to recent copies of scrubbed database copies of Drupal.org.

Duties will include:
1) Approving SVN Accounts for themers and developers to the private theme and drupal.org code repositories.
2) Creating new drupal.org instances for themers to work on.
3) Pushing theme and code changes from SVN

To learn more, see: http://groups.drupal.org/node/23645

We need to discuss how we want the d.o redesign project to move forward. One- to 5-day sprints every few months is not a sustainable solution. Maintaining momentum and continuity is nearly impossible.

Initial thoughts:

• Take a cue from the Aegir project and introduce a proper schedule
  • Require weekly time commitments and weekly meetings
  • Initial thoughts: 4 hours per week for at least three out of every four weeks (meaning you can skip one week from every four to catch up on client work)

Will the g.d.o design be changing with the d.o redesign?

I'm wondering b/c I'd like to customize the g.d.o group i admin - add pages, blocks, et cetera.. and am wondering if that will be lost effort if g.d.o is changing soon?

thanks in advance,

Stein

I've been helping with documentation pages and found that some pages appear to be editable, but in fact are off limits.

This seems to be related to Full HTML pages or Auto-generated pages. The pages themselves look like any other page - which is what causes the confusion.

Would the redesign infrastructure team please discuss possible solutions to this that involve a visual queue?

After my hand gets slapped for dinking with a page, I then go beg forgiveness OR
After I try to edit a page I realize I have to go grovel in another issue queue to get someone else to do my dirty work.

Could we add a task to clean up existing contribution branches by removing invalid ones
(e.g. DRUPAL-6--1-0 or DRUPAL-4-7--2-0 , and many more).

This assumes we actually have an automated way to generate a list of valid branches - not currently easily done in cvs.

This node is what sparked the issue http://drupal.org/node/97084

thanks,
bekasu

On Friday June 12th, we will be having the Drupal.org redesign sprint. All Drupal designers and developers who would like to learn how to how to contribute to theming drupal.org and implementing the redesign are welcome to attend, but must sign-up in advance.

20 Ames St., Cambridge, MA white-tiled building - Sprint is in Conference Room 135: Go to lower level of Media Lab, look for double glass doors "001"; go through doors, up metal staircase; 135 is at the top on right.

Hallo

jeden Donnerstag abend treffen sich Leute online, um gemeinsam an Übersetzungen von Modulen in Deutsche zu arbeiten.

Dazu wird der Editor gobby, die voice-chat-Software mumble und IRC #drupal.de auf Server: irc.freenode.net .

Detais zu den Programmen und der Konfiguration findest Du unter http://www.drupalcenter.de/drupalchannel.

Ich freue mich über jede/n .

Bis dann
Thomas Zahreddin

PS: Sorry für das crossposten, gerne verteile ich die Einladung auf einem anderen Weg, wenn ich damit alle deutschsprachigen Drupal-User erreichen kann :-)

I'm not sure whom to ask nor where to look for the answer to this question.

I've been working on the doc team and trying to help as best I can.

One thing that I'm concerned about are the terms Projects and Modules which seem to be used interchangeably.

Example: http://drupal.org/project has a link on it to Modules http://drupal.org/project/modules

Yet when you click on the http://drupal.org/project/modules link, you get a page titled 'modules' and the first line says you can get a list of
PROJECTS in alphabetical order.