Drupal.org redesign infrastructure team

http://d6-api.drupal.org/ is like http://api.drupal.org/, but is running on Drupal 6. Please take a look and comment or file issues for anything you find.

I have been trying to make this a basic Drupal 6 upgrade, but more was done:

• Some parser bugs were fixed.
• Basic unit testing was added, with a set of sample code for testing.
• All pages now use themeable templates.
• Minor redesigns have happened throughout.
• Function pages show how a function has changed between branches.

Here's a quick update on the Drupal.org redesign infrastructure. The first drupal.org site to be upgraded to Drupal 6 will be the Drupal association site. We are doing this for a couple of reasons. First, we want to a small project to test out our new collaboration infrastructure: VMs, Database, SVN, Access Control to allow more people to work on the upgrade. Second, upgrading association.drupal.org will allow us to upgrade to CiviCRM 2.1 and help with fund raising. The association will be dropping case tracker module so that we can upgrade to Drupal 6.

Hi,

This week sees the release of iteration 11.

http://drupal.markboultondesign.com/iteration11

This week we have made lots of some smaller changes throughout the whole prototype, items that were delayed from iteration 10. For this release, we've paid particular attention to several pages:

1. Marketplace

2. Download and Extend

3. Modules landing page

4. Themes landing page

5. Search_by theme

6. Home page

7. Dashboard

There has been a lot of great feedback on the iteration 10 post, thank you all for your valuable input.

This wiki page should reflect an up-to-date state of where drupal.org stands in its upgrade to Drupal 6. Initial data here is based on findings in http://groups.drupal.org/node/16246 and should be updated from time to time to reflect current reality.

SIGN UP TO HELP

Each section has "working on it:" sections, where you can mark yourself as someone who contributes to that section.

Hi,

This week sees the release of iteration 10 in the Drupal redesign prototype.

http://drupal.markboultondesign.com/iteration10

We're currently working with the Drupal Association to further define an advertising strategy for the redesigned d.o. Therefore, we've included a few more ads, but it probably isn't indicative of the final strategy.

Hi,

Iteration 8 is now available for you to browse and comment on. Last week the redesign took a pretty drastic change in direction so this week's release isn't as massive as we have worked to consolidate changes to the IA, reacting to feedback from the testing and to trends we have established in the community feedback.

Last week Leisa posted her thoughts on why we have moved in this direction and you can read her thoughts here:

http://www.disambiguity.com/drupalorg-redesign-iteration-7-for-your-revi...

Leisa will also be posting again shortly to further discuss our thoughts and reasons for recent changes as well as talking specifically about the modules section.

The link to the latest iteration is below:

http://drupal.markboultondesign.com/iteration8

So, we've had the 'About' section in the prototype for a while now, and we're turning our attention to the content. We're seeing this section as a place for evaluators of Drupal to make a decision. But also, as this is software, there are things like technical requirements that need to be included.

So we need your opinion and feedback.

What do you think needs to go in this section?
Are we on the right lines with the current prototype?
What do you think the navigation items should be?

Hi,

Following on from last week's call for feedback on iteration 5 of the prototype ... we have now progressed to iteration 6, whereby we have begun to integrate the visual design into the prototype, making the prototype feel more like a website now and less like wireframes.

We encourage you to browse through the prototype and feedback your thoughts and ideas in this thread. The link to the latest iteration is below (please note the slight change in URL - this is because of a new version of Blueprint, and additions to CSS etc.):

http://drupal.markboultondesign.com/visual/iteration6

While the drupal.org redesign is about so much more then drupal.org itself, we certainly need to clean up and improve on our act on the main drupal.org site before moving on to elsewhere IMHO. So I took a look at the modules enabled on the drupal.org website (via good old "system table where status = 1" queries), which I've attached as http://groups.drupal.org/files/DrupalOrgModules_0.pdf. Some notes:

• Drupal module was ported as site_network to Drupal 6, so drupal.org can keep offering that for backwards compatibility after and until the OpenID server is set up (waiting for that sounds like a never ending story)
• There are some interesting items on drupal.org, like dblog module enabled but without a file; also urlfilter contrib module enabled, while it is a built in drupal 5 feature.
• There are certainly items which we are not going to carry forward. The bluebeach theme is among these things, but feature module seems like a safe bet as well. It is a horrible way to present Drupal features, and should go away as soon as possible.
• Two of the drupal.org custom modules are not hosted under drupalorg module and are therefore not open source. This makes it harder to port them forward and get the community going on reviewing and helping with them. These are the ircnick module used to search by irc nickname and the update_status 1.x XML-RPC compatibility module.
• Quite a few of the modules have 6.x releases but not yet stable. In cases like image module, where even Acquia Drupal ships with them, it is a good question, whether we should believe they are stable or not. Independent verification always helps. Also, our criteria is more strict, we need to keep some existing features going forward, unless of course we can do something better.
• There are obviously 5.x modules not done for 6.x yet, but the list goes way over just the project module family. So there is lots of ground for work beyond upgrading project module.
• As far as project modules go, my last information is that dww/hunmonk/aclight look for new stable releases of the module suite for 5.x hopefully sooner then later (http://groups.drupal.org/node/10865 and http://groups.drupal.org/node/16069 for details), and then Drupal 6 patch committing will start.

I think there is plenty of work opportunity here to distribute. So let's get started!

Hi All,

The redesign has made great progress over recent weeks and we would really like to share this with you!

Below is a link to the latest iteration of the redesign prototype. Please take the time to look through the pages and feedback your thoughts and ideas in this thread.

http://drupal.markboultondesign.com/iteration5

We also welcome comments on the initial design and visuals, and as with previous weeks, all posts here will be read and fed back into the redesign process

Last night we enabled Pivots recommendations on Drupal.org. We've been working on Pivots for almost 18 months and I think it represents an exciting new type of Drupal.org service. Today pivots uses a custom indexer written in Java. That indexer reads the content on Drupal.org and then indexes it to the masterdb-other.drupal.org a database server outside our main Drupal.org database servers.

See: http://mrzhou.cms.si.umich.edu/diagram-pivots-recommendation-system-do

In an effort to be proactive on the Hosting Forums being shut down issue a small group of us are attempting to define some guidelines for moderating them should they be brought back online.

Please chime in if you have feedback to add to this topic. Bullets are quotes separated by contributor, followed by a consolidated 'Official Guidelines'.

Hi All,

This week we are calling on feedback on the first iteration of prototyping.

To view the prototypes in their current form please go to: http://drupal.markboultondesign.com

I took some time today to draw up my vision for the project pages..

Full size version.

It's a mix of my current work, some future plans, and some ideas I had for harnessing Drupal.org's data. More details over here.

So, what do you think?

A good place to start would be to update and inventory the Drupal.org infrastructure so everyone knows what we have and how our little virtual machine for the redesign development and staging comes into play.

In this issue from last year, http://drupal.org/node/155850#comment-626523, we updated the hardware diagrams.

A list of hardware is available to D.O. production infrastructure team members here: http://infrastructure.drupal.org/node/36
A backend network map is available to D.O. production infrastructure team members here: http://infrastructure.drupal.org/node/44