Drupal.org Improvements

Hello, we now have 10 staging sites available to help with the Drupal.org redesign. Drupal.org is a complex site with many moving pieces, and it is very difficult to create a staging environment that replicates the content, files, and Solr integration that are critical in replicating Drupal.org.

http://d6-api.drupal.org/ is ready to test again. Notable changes are:

• Commenting on documentation
• Faster autocomplete in the search box
• Search by URL, as in http://d6-api.drupal.org/theme
• OpenSearch plugins for your browser
• New file URLs (the old ones should redirect)
• The parser doesn't parse \@ and links http://example.com/

With the addition of comments, we need some webmasters, please volunteer at http://drupal.org/node/547534.

Please file issues at http://drupal.org/project/issues/api

api.drupal.org is a good test case for single sign on, it is a separate site and is getting a new feature that needs user logins, commenting.

chx made commenting work, http://drupal.org/node/101308, but I want to deploy this right. Comments about improving the documentation itself really should be improved documentation, it should be easy to file an issue to get the process started; http://drupal.org/node/500536 and http://drupal.org/node/512824 currently need work.

Damien is working on setting up three instances we can use for this project: redesign.drupal.org, staging-1.drupal.org and staging-2.drupal.org. If you want access to these instances, upload your SSH key on this thread.

Here are details that we'll need to discuss:

• What are our development needs?
• What do we do about managing the database?
• How will we handle configuration changes?
• How can we make the database available for developers using local environments?

So it sounds as though getting together for IRC or Skype meetings more often will be beneficial. What is your schedule like? When are your best days, and when are your worst days? What time period are you most available and less available?

What is your availability for the next month? Roughly how many hours a week are you available? What do you think your availability is for the rest of the summer?

And while we're at it, mention your speciality: designer, themer, developer, etc.

If you have any interest at all in this project, then respond! Knowing a rough head count will greatly help in planning!

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.

After reading dman's Open Letter I started to think about how module management on d.o can be improved. Not just to identify duplicated modules, but also regarding dependencies and incompatibilities.

With the absolutely fantastic growth in the number of contributed modules for Drupal it is quickly becoming more difficult to navigate through them, both to find a module that suites the needs and information about if it may create problems with modules already installed. Often this require quite a bit of research through various issue queues, forum threads and so on.