People have spoken on when they can do a sprint and Advantage Labs has so graciously reserved us the conference room in the IATP building, so the Documentation Sprint is on June 20, 2009 from 10:00AM to 5:00PM!
Logistics
- Place: 2104 Stevens Ave S, Minneapolis, MN 55404
- Day: June 20, 2009
- Time: 10AM to 5PM, feel free to come and go as you please. There is no reason you have to be there the whole time though it is encouraged.
- Who: Everyone! There is no skill level required. You just have to have a good attitude.
Goals
Our original discussion outlines some ideas. We don't necessarily need concrete goals, but some idea of larger tasks we want to accomplish would be great. Please comment on this post any ideas you have.
RSVP
It would be very helpful if people who can RSVP do, as we can start to gauge how many people and what kind of skill level we will have. This is an event type and there should be some sort of attend button on this page.
Support and Sponsorship
It would be really great if we can find someone or a company to sponsor lunch or maybe even drinks afterward. Let me know if you or some you know is able to.
Comments
Free Lunch provided by FiveFiveFour
Stephen at FiveFiveFour has generously offered to pay for lunch at the Documentation sprint! They will provide Galactic Pizza for up to ~20 people, so RSVP now so we know who's coming. Feel free to drop them a line and say thank you here or here. Thank you!
Also, we could always use some coffee and other drinks during the spring, or even some drinks afterward!
--
zzolo
zzolo.org
--
zzolo
Gorton Studios will also support
zzolo - thanks much for getting this rolling. I'll be participating in the sprint and we (Gorton Studios) would also be happy to help sponsor. So - as you're putting together plans for what's most needed (coffee, doughnuts, drinks afterward or whatever) just let me know what's missing and we'll bring it!
Drew Gorton
Gorton Studios
One thing that I think could
One thing that I think could be both fun to work on and extremely beneficial would be documentation for the new Fields API in Drupal 7.
At the moment, there isn't much end user facing documentation though there really should be. It would also be something fun for people that are interested in learning more about the new Fields API and getting a jump start on knowing how to use it when D7 comes out.
Docs issue queue link: http://drupal.org/node/419348
Current documentation: http://drupal.org/node/443536
Current API documentation: http://api.drupal.org/api/group/field/7
Perhaps there is an opportunity to work with someone who is more knowledgeable about the new API, get them to help write some outlines for documentation and then we can go through and fill the outlines in with real language/examples.
Great Idea
I think this is a great idea! The new Field in core is really exciting.
We are currently without any specific agenda or goals. Allie mentioned leading some Geo documentation.
As this is a really new topic, I think doing this would require your leadership to point those interested in the right direction, and also try to contact some folks that are knowledgeable in this area (I would suggest asking around #drupal and #drupal-docs in IRC).
--
zzolo
zzolo.org
--
zzolo
good!
Looks very interesting. Thanks for sharing..
Standard tasks for doc sprint
There are always the standard tasks -- not glorious, but they sure need doing all the time:
You might also consider reviewing Documentation patches that have already been filed in the Drupal /documentation queue; there are a number that are lingering (Search for "needs review" status -- http://drupal.org/project/issues/search/drupal?&status%5B%5D=8&component...)
Drupal programmer - http://poplarware.com
Drupal author - http://shop.oreilly.com/product/0636920034612.do
Drupal contributor - https://www.drupal.org/u/jhodgdon
Yay!!
Leave it to the people from Minnesota to be awesome! :D
Here's another spot that could use a bit of help:
http://drupal.org/project/issues/search/drupal?text=&assigned=&submitted=&participant=&status[]=1&status[]=13&status[]=8&status[]=14&issue_tags=Needs+Documentation
These are all core issues that are tagged "Needs documentation." For the most part, this should be changes that have been fixed in Drupal 7, but whose changes haven't yet been reflected in the 6.x => 7.x module updates page and/or the 6.x => 7.x theme updates page.
So the task here would be:
Feel free to ping the patch authors in IRC as well if you get stuck at all. Technically this is their responsibility but sometimes they get busy.
Count me in!
I'll be there to make bad puns, take pictures, help with re-writes and, generally speaking, help out wherever I can. I am also good for testing and pretending I am a naive user.
Doc Roadmap Posted
We're in luck - Add1sun (and others) have been working on documentation infrastructure. In addition to having webchick's thoughts above guide us, we ought to also review the doc roadmap just posted at http://drupal.org/node/488070.
Good Timing TC Drupal!
Drew Gorton
Gorton Studios
cvs access?
(I can't believe this is coming up in 6 days already!)
http://drupal.org/node/424194 (Documentation Sprints)
Some things we might need:
*CVS accounts
There will probably be at least 2 people with actual drupal cvs accounts who can actually contribute our documentation back to drupal, right?
I would be happy to help with the commits this if someone can please help me get cvs access.
*IRC -- depending on how many people come and their familiarity with drupal and IRC -- i think we should all get on the #drupal-docs IRC channel. I use IRC rarely but want to do it more - so I think at the beginning of the day we should check that everyone who wants to be on IRC has a client (like colloquy on macs, mIRC on windows or chatzilla firefox plugin) and can get in. I think it is much easier to get into the groove of talking on IRC when you are in a room with other people who are already using it. Also it isn't as scary. The drupal IRC channels still scare me. (I will organize this if the IRC regulars will help with technical questions)
*Agenda-y stuff:
We will probably just gather at 10, do some introductions and then self-organize into groups of people who want to work on certain projects -- and people who organize some documentation will present/explain a documentation project. These projects will probably be documentation for issues from an issue queue, fields, geo stuff.
Then we'll just document all day, adjust schedule as necessary & eat.
Right?
Update
Just an update on things.
CVS Access
We should not need too much of this. But I have one, Allie, and Jer do as well. For people that want one, this may be a good opportunity to do some work that requires one and then apply for one.
Documentation Team Access
Barry has this, and I am currently applying for one (again). Again, this is not necessary to work, but can help with specific tasks.
Agenda
I think chachasikes has the right idea. It will be a pretty organic process. Pairing up is always a good idea. I will try to put together some specific options before Saturday, just in case we need it.
--
zzolo
zzolo.org
--
zzolo
Oh - and this list of tasks:
http://drupal.org/project/issues/documentation
Drew Gorton
Gorton Studios
Initial sprint notes
Sprint started at about 10:15 a.m. with 14 Drupal documentation specialists in the room. 5 more Drupal documentation specialists joined the group by 11 a.m.
First topic was who had ever participated in a sprint before, one person had and another had looked in on one at DC Drupalcon. We had several people who had documentation access.
We discussed specific projects and a concensus developed around working through the documentation list of open issues plus some specific items people have been working on.
1) How to set up audio lists
2) Drupal 7 code
3) Plow through documentation queue
4) Train people on how to contribute documentation - this happened organically at each table.
Split out into 5 separate groups.
Kept a whiteboard list of issues we were working on and most folks hooked up on IRC.
Minor note on our titles
"Documentation specialists" is very fancy sounding. We were all just some people who were interested enough in Drupal to show up on a Saturday to do some good. All you people of the future - don't be scared into thinking you need to be a Documentation specialist before arriving. (All of us can proudly wear that title, now, though)
:)
Drew Gorton
Gorton Studios
What We Accomplished
We had a great turn out on Saturday for the Twin Cities Documentation Sprint. We broke up into groups and worked on various different documentation tasks.
Many thanks to Gorton Studies and FiveFiveFour for their generous donations of lunch, spirits, and coffee, as well as Advantage Labs for providing the space.
We marked the issues we worked on as tcdocsprint09. I'll try to list the specific things that we accomplished:
For those of you who were there, I know am I am missing some stuff. Please let me know what you did so I can update this post and put a post on my blog that will get aggregated to Drupal Planet. Also, if anyone took pictures, I would like to include those as well.
Thanks for the great work, everyone. I have a great time and think we should do this again sometime.
--
zzolo
zzolo.org
--
zzolo