EDIT: We have moved on to the February steps. Thanks to everyone that stepped up to help out in January!
We had a good CoffeeTalk and were able to hash out some of our website features. Here is what I am proposing we focus on for the rest of January so we can start ramping up. There are all kinds of discussions and tasks here so if you want to learn about any of these or if you are knowledgable and want to help out PLEASE don't hesitate to step up. If you are want to get into one of these but aren't quite sure what/where/how feel free to contact me directly through my contact form or ping me on IRC (I'm often in #drupal and #drupal-dojo, nick is add1sun.)
As usual, feel free to add to this discussion, push back at me on points or propose new ideas. I'm just making it up as I go along. ;-)
1) Video issues are first priority:
We need to start producing solid videos so that we have content to keep people coming to the Dojo and hopefully get involved. I am basically in agreement with Matt's (mpare) assessment that we need to laser focus on quality produced videos for right now. I don't think that means no live lessons, but it would be good to produce some regular, quality vids for a little while and not depend on the varying winds of tech issues and quality from live lessons. Let's get ourselves organized and create 4 videos that can be released at regular intervals starting sometime in February. To that end we need to get the video tasks in the queue dealt with first. So please focus on these issues as a priority over the next two weeks so that in February we have a game plan:
Create Dojo video "standard"
Research video storage/delivery options
This not as much a priority at this time but a discussion we need to keep moving:
Screencast Instructor and Producer Incentive Program
2) Development environment:
Let's get code, issue tracking and dev workflow sorted and set up by the end of January. At this point it looks like we will be starting off with using Assembla for at least our SVN repo so we can get up and running. Folks with an interest are encouraged to hop into the SVN/tracking issue to hash that decision out more. Once that is settled and in place we will move the existing code into the new repo and set it up for dev work. We will also write up a best practices document for how to use SVN and the workflow we'll use for developing dd.com. Everyone that is interested in this process should speak up in the Dev environment issue so we can work together as a team. Note that the deadline for this is the end of January so we'll need to hunker down the next two weeks to get it done.
3) dd.com website moving forward:
So this Sunday we focused our feature list a bit and the results are listed in the issue queue. Everyone should review the issues we have and add any more that we missed this week. As of next Sunday, January 20 we'll begin writing an actual spec for the site. That means no more feature creep unless it truly is critical to the site. The spec will be written as a collaborative document so folks with experience here or interest keep your eyes open for when that process starts next week.
Comments
Update and easy starter tasks for learning
Here is an update so far. We need help and action from people in the group to keep this moving forward. If you want to learn, then now is the time to start helping and learning. You don't have to know how to do this stuff, you just need to be willing to help. No experience needed for any of these three tasks!
1) I've got an initial post up about a standard/guideline for videos that needs some work on it. Please give feedback and propose modifications and let's hammer that thing out. Target deadline: Jan 27
2) aclight, josh k and myself got SVN, viewvc and Project module set up over the weekend. We still need to finish a few connector bits and put the existing code in the new repository. We also need to get some documentation going so if you would like to know more about how we set this up and developing best practices for dev workflow, here is your shot to dive in and really help us out while learning. Target deadline: Feb 1
3) Feature creep is closed. :-) We need to get a spec written up. For starters would someone please start a simple document that lists and summarizes each of our features from the list we worked out in the issue queue? (Please create a text document and attach it to that issue in the queue and set the issue to 'code needs work'.) Then we can continue to fill it out with how we think the site will be structured. This should give us enough info to start up the fun process of wireframing our ideas. Anyone can get in on helping with this so don't hold back. Target deadline: Jan 27
Of course folks with experience and advice are more than welcome to jump in too! The very few people who are actually doing the work up to now are pretty stretched so we need as much help as we can get. Thanks!
Learn Drupal online at Drupalize.me
Some good inspiration
For those who aren't aware, there another Drupal redesign effort going on - obviously the scale is a bit different, but it would be good to observe, interact, or participate on this parallel project. In terms of the priorities above, how are things coming along? Are we at a point where we should try to recruit folks to various roles (project manager, lead developer, graphic designer, etc)? Some ideas on a potential process and roles can be found over here.
Gus Austin
PepperAlley Productions
Gus Austin