projects

The following is a first stab in terms of establishing guidelines and a workflow for open drupal development. Ideally we can use this wiki (and discussion thread) to hash out a process for the Dojo 2.0. (issue here) and other collaborative projects. This process is geared more towards building a complete site from start to finish.

With the interest expressed by Dojo members and the wider Drupal community in this project, we're moving forward. This wiki page is open to anyone to update as the project progresses. Feel free to leave comments as well.

Project Outline
One of the things mentioned by Dries in his "State of the Drupal" talk at OSCMS (watch the video here) was how nice it would be if book.module would turn into a more generic outline functionality, rather than being semi-attached to a specific node type. We're going to take on this task.

Project Deadline
The Drupal 6.0 code-freeze is on June 1st, meaning we need to have all features done by then, as only bugfixes are allowed beyond that point.

Issue Queue
We will be organizing by using Drupal.org's issue queue. Here is a direct link for the book component.

UPDATE: I made a mistake and had comments turned off. Please comment on this! I want your feedback and discussion!

In just six weeks, this group has really taken off, and I have been extremely pleased and excited by the response from the community, and by people's willingness to jump in and help out.

I think we're doing a lot of valuable work. We've got an excellent core group and a process for having "lesson" events that seems to really provide value, especially given the excellent work that so many of you have done to create screencasts and written documentation after the fact. So thank you all once again for your participation.

The topic of the day is growing pains. There was much discussion of this in Sunday's CoffeeTalk discussion, which I was thrilled to see take on a life of its own without my participation.

There are several points I would like to cover, not least of which is what (if anything) to do with the domains drupaldojo.com, and .org, which Squidster took the initiative to acquire, and .net which is owned by Senpai. Read on for my thoughts on this, including a pretty graph!

We should carry on the discussion from today's online meeting to help nail down things that were discussed and bring those that could not make it up to speed. This is a VERY brief rundown of the highlights and I'm sure the recordings will be available soon for those that want to follow the whole thing. If I'm off-base on any of this (which could easily be the case) please correct/discuss in comments.

Two big topics that were covered were 1) the idea of a separate scratch site to experiment and work ideas out in and 2) how to work with d.o handbook and get improvements into it. Sepeck was kind enough to stop in and really hash out these ideas, give guidance and be involved in the discussion.

With 'Drupal' support for installation profiles eminent (full-on distributions to follow), I'm thinking it will provide a rich platform for collaboratively building (real sites), learning, and giving back to Drupal.

Based on some of the recent conversations on the irc and in this forum, I just wanted to throw out some random ideas. It's a wiki, so with your help, we can make it sound logical...

Objectives

There are some great ideas for future lessons brewing here, so I thought it might be smart to put them all in once place. Hence, the "Drupal Dojo Lesson Ideas wiki". Edit away, folks. :) Hint: There's an 'edit' tab at the top of this node.

If anybody wants to take on one of these lessons (as a teacher/guru) stick your name in there somewhere.

Projects and collaborative workshops