Western MA Drupal Community Code Sprints

Events happening in the community are now at Drupal community events on www.drupal.org.
sanguis's picture

So I wanted to post this before I lost my post DrupalCon rush.
I know have been less involved with the WMA Drupal community but I wanted to share a thought that I had.
LAst week At drupal con the talks were great, and the BOF's were great. but where I really learned was on the code sprints that happend for core, documentation, and contrib modules.
People picked a task and just started submitting patches. In the room it was like an in house IRC channel people just yelling out for help, or patch review. if it worked it was committed right then and there to its respective project.
I have talked with 2 other WMA devs and they say they would be into a code spint gathering at some point. What do yall think, we pick a module on drupal.org with plenty of issues in the que and hit it hard for an hour or 2. (i.e. finishing up coder_upgrade for d7, it really is missing quite a lot of changes ATM)

Just a thought. I dont know if this would be an additional gathering beyond the meetups or and extension of it.

Comments

Absolutely! I'd love to do

JacobSingh's picture

Absolutely! I'd love to do this. (of course, won't be there till may). It would be particularly useful to grab a module queue which had doc issues too so non-coders could be involved there. But to pull this off well, it requires groundwork, identifying issues, prepping them, making sure the maintainer is down, etc.

Roles,

sanguis's picture

At the last meetup kelly made a suggestion that people could try on different hats while we do this. So if anyone wanted to try project management they could do the research of which, module to do.
They Could look at the issues and divvy them up as will as report back to d.o on how things are going.
A dev, who wanted to documents would be able to do try it, and get help.

Module sugestion

sanguis's picture

I am personally going to suggest that we stick with the coder module, because for every code patch that we submit, a corresponding piece of documentation will need to be made explaining how the function had changed and what not., so we could have teams of 2, per function change,
one person creating the patch and one person creating the documentation on how to upgrade the function.
Also what a module for people to lean coding standards on but the modules that sets coding standards.

Is coder the right choice? I

JacobSingh's picture

Is coder the right choice? I agree that it has a lot of value, needs work, etc.. but would the subject matter be a little too "meta" for the non developers in the group?

You may be right. Got another

sanguis's picture

You may be right.
Got another suggestion?

Any date and place on this yet

yurtboy's picture

I could do some documentation since my coding is never "sprint" speeds.
Plus I would like to get to know the doxygen format better.

Ubuntu has a paper cut site of all the small things that urk the user. Maybe we can just figure out this things and go fix them?

Or maybe find some popular modules or modules where the maintainer is asking for help and jump in?

twitter or Oauth

sanguis's picture

how about http://drupal.org/project/twitter
porting it to d7
or oaAuth
These would be huge for the community.

I can do mons and weds for the next couple months.

name your week people

Yeah, that looks like a

JacobSingh's picture

Yeah, that looks like a really good one.

Western Massachusetts

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: