Drupal 7 API is now slushed and frozen. Now is the time for Contrib modules to start upgrading to Drupal 7. The #D7CX movement wants to see as many contributed modules as possible be ready by the time Drupal 7.0 is released. Lets get our Boston maintained modules upgraded!. Even if you don't do module development, you an be helpful here by reviewing module issue queues, QA testing, and documentation writing. There is a job for everyone.
MIT is graciously hosting on November 8 from 10am until whenever. We will have power, wifi, whiteboards, projectors - the works. If you are at all interested in attending, please click the Sign up button for this event. We will broadcasting more information to those persons who are signed up. We will likely not be updating this page with the final location of this event.
Comments
Signed up and looking forward
Signed up and looking forward to hearing about the space where this will be. (The lousy cell reception was a big damper, so to speak, on the coordinating during the redesign sprint at the MediaLab.)
I'm in. Is there anything I
I'm in. Is there anything I should do in advance to be be ready to go on sprint day? This is my first sprint.
-Bryan
Good working environment
Make sure to click on the sign up button to get the exact location of the sprint. The main thing to prepare is a good working environment on you laptop. Make sure to have your favorite editor/IDE properly setup. Ideally you would have cvs, svn, bzr and git installed since some projects might be hosted outside drupal.org during the porting phase. That will save you sometime at the beginning of the sprint. If you have time, read the Contributor Guide for tips on developing for Drupal.
I suppose there'll be several groups working on different modules, and people will be able to get you up to speed on the specifics of their modules. I'll be working on the RDF modules for Drupal 7 and anyone is welcome to join us!
Agreed. The single most
Agreed. The single most difficult part of the last sprint I attended was that not everyone had a working local environment set up on their laptops. In spite of several people working nonstop to get everyone up and running, it wasn't until 2pm that afternoon that we were all ready to move forward as a group.
That being said, my impression is that everyone will be working in teams on various projects instead of one large group. One of the things I'll be doing is looking at the modules I hold near and dear (top modules that already have the #d7cx pledge excluded) and posting what I know in their respective issue queues.
I recommend that anyone who's attending this event read up on the D7CX initiative and devise your battle plans accordingly:
http://cyrve.com/d7cx2
http://cyrve.com/d7cx2
http://groups.drupal.org/node/24642
Before the sprint, please get a copy of Drupal 7 and Coder 7.x-1.0-beta1 up and running in your local environment.
http://ftp.drupal.org/files/projects/drupal-7.x-dev.tar.gz
http://ftp.drupal.org/files/projects/coder-7.x-1.0-beta1.tar.gz
Basically, if you're already a module maintainer on drupal.org, the D7CX initiative should already make sense. If you don't maintain any modules, your help is massively helpful when it comes to QA, documentation and helping create the energy at the event. Even just encouraging the maintainers of your favorite modules (encouraging, not harassing) is a way to help. The best way to find which themes and modules have already taken the d7cx pledge is by searching the project pages for d7cx.
Not going to be able to make it, but will make contributions
Unfortunately I am not going to be able to make it today, but I will work on converting Search Lucene API to D7. I also have a couple of core patches that fix some bugs in D7 regarding hook_requirements(), and it would be great if a couple of people could look at them as part of the code sprint. They are located at http://drupal.org/node/592182 and http://drupal.org/node/592800, and as a side note they effect current versions of D5 and D6 as well. See you all at the next meetup!
~Chris