Hey Docs Teamsters!
Not sure if any of you have been following my posts about trying a more agile/sprint-based method for the online docs work that needs to be done - I wrote a bunch about it here: http://groups.drupal.org/node/134909 (And there's a link to my blog post about it there as well).
I've selected some issues that are very high priority that I think we ought to focus on for the month of April. I'm hoping that having a smaller set of tasks to concentrate on will help us band together and get them done!
Full list: http://drupal.org/project/issues/search/documentation?issue_tags=Sprint%...
Main issues of focus (size/difficulty) - who's planning to work on them:
- Review and update D7 core module handbook pages (medium/novice-moderate) - ?
- Installing contributed modules (medium/moderate) - jn2
- D6 CCK to D7 core field migration docs (large/advanced) - bayousoft
- Review changes to Upgrade process page (small/moderate) - ?
- Review and test the upgrade guide for Drupal 7 (medium/novice-moderate - almost done) - ?
So what I'm wondering is who might be looking for something focused to work on, and expecting to have some time to dedicate to docs for the month of April. And then second, if you do, whether there's a particular issue you'd be interested in working on.
It'd be great if there's enough interest to test out whether this idea of having specific issues to focus on month to month helps get things done more effectively. I think that some of the formal D8 initiatives will be trying this sort of method out as well, so this could be a nice demonstration of how to make this method work.
Please post below if you're up for it!
Comments
Is this mostly going to be a
Is this mostly going to be a sprint of what is tagged as 'April 2011' in the issues queue, or do you mean something more general, like get a group of people to once over the entire Theming Guide.
Month by month
Hi David -
The more formal month-long sprint will be on the issues tagged as April 2011. This doesn't preclude people already working on things to keep working on them though!
The focus will change each month, if this goes well, so that we can spend a month at a time working on an area that needs extra attention. This first one will be completing the D6 > D7 upgrade and D7 core module docs.
I'll be presenting about how
I'll be presenting about how to get involved in Docs at the Portland Drupal Users' Group Wednesday, April 13. The call to action will be to dive into the issues tagged for the sprint (if it's not too late), but we won't be coming to the party until half way through.
I almost think (assuming we
I almost think (assuming we actually get enough people to get this rolling at the start of the month), it might be better to get people up to speed on how this works, and invite them to jump in on the next one for May. Just because on-boarding people mid-sprint will be a bit difficult.
In the meantime, there are lots of other issues to work on! And maybe you could even peruse the queue for an area of focus for May - git? Theming docs? Beginner docs/cookbook?
Sounds good
I'll review the process as you suggest, and talk with folks about a May theme, then.
I'd like to help
I would like to help. All I need is a little direction getting started and then I should be fine. This sounds like a good idea to me. bite size chunks
or
Should I just jump in and start doing it? :)
Great! Maybe you can have a
Great! Maybe you can have a quick review of the issues that I'd earmarked and see if you find one of them particularly of interest? I'd like to get at least 2 people on each one, that'll work best for being able to review things back and forth.
Sounds good
Reading the (style guide) today before going further, either of the upgrade or core module pages will work, wherever the priority is highest I am game
Do you mean the CCK > Field
Do you mean the CCK > Field upgrade? Definitely more challenging, if you're up for it I think that would be a great place to help!
CCK > Fields Upgrade
In reading through the existing D6 > D7 upgrade guide I notice several mentions concerning CCK > Fields. Is the objective here to simply confirm/correct what is there now? or something else? thx
It's quite possible that
It's quite possible that someone has added info and not updated the issue! We'd be looking for instructions on how to migrate custom content types/data in CCK into core (fields) - there should be a D7 CCK (or CCK migrate module) that you have to install in D7 and then it allows you to do a full migration of what was built with CCK in D6.
If you want to start out by reviewing what's there and reporting back on the issue, that'd be great, maybe that one's close to finished and just needing testing (if we're lucky!)
OK
Well, there's a lot of negative comments about issues with the instructions and I didn't go all the way down the comments even yet so there appears to be some work left but there is definitely something already started. I'll go through everything and report back.
awesome! thanks!!
awesome! thanks!!
Next step
Correct me if I am wrong but this is the existing documentation for CCK > Fields: from http://drupal.org/node/570162
Do we want to: a) first follow the process at a basic level (with just CCK enabled) and confirm that it works b) follow the same process with other popular CCK contrib modules (i.e. imagefield) enabled
How far down the rabbit hole do we go with this? :)
Great! Can you post this to
Great! Can you post this to the according issue? (We should track anything about the actual work there.)
I think that a) yes! we should definitely test what's there. and b) yes! we ought to see how the other CCK contrib modules are supposed to be upgraded and document that as well - think like a person who is coming to find this info, the more detailed the walkthrough is the better (of course, within reason). ;)
The chunk that you pasted here is good, but definitely needs more detail (especially about the specifics of various other CCK add on modules), possibly even its own child page from http://drupal.org/node/570162.
Child page etc
That chunk is copied straight from that page, seems to be the entirety of the official cck > fields documentation right now.
Do you or someone else have to create the page? Do I write offline and forward it to you for approval?
If you want, you can post the
If you want, you can post the content right into the issue for reviews, before making a page. But otherwise, you should have a "create child page link" that you can use to create it. Then you can just post on the issue and say that it needs review (and change the status to "needs review").
I'll help
I've been following your posts about the April Sprint and want to help. I'm interested in http://drupal.org/node/895514, working on http://drupal.org/node/895232.
Fantastic!!!
Fantastic!!!
Update
I've added a comment to this issue queue and will update there. Captcha keeps at me here.
That's quite alright, better
That's quite alright, better to update on the issues anyway!
CAPTCHA
FYI
I tried to submit a link in my post above and got caught in and endless You didn't complete the CAPTCHA properly loop.
I hate captcha!
Eric Meyers uses simpler means to achieve the same: 2+2 =
Jeremy Donson
Database and Systems Engineer
New York City
Updated list of issues (top of page)
So, since we have no infra to do agile sprint tracking right now, I've added a list at the top of the page of the issues, size/difficulty level, and who wants to work on them.
I'll keep this up to date, so people can tell who they're teamed up with and find them on IRC or the issue queue (or even email if you want to do that).
Thanks to all who are volunteering their time!
Agile Sprint Infra
Is there a discussion going on anywhere about adding an infra for sprint tracking, Agile or otherwise?
Not sure if there's anything
Not sure if there's anything specifically agile oriented, but if there is, it's probably be here: http://groups.drupal.org/prairie-initiative
Targeting Linux
It appears to be common practice to target Linux in the documentation (ie. examples http://drupal.org/node/570162). Is that correct?
Sort of. ;) I think a lot of
Sort of. ;) I think a lot of the docs target Linux/unix, but we're trying to support Windows more too. So if you're able to cover both, that's great, otherwise do what you know and then update the issue saying what's still needed.
Office hours/mini-sprint?
Hey April sprinters (and potential sprinters) -
Thinking of ways to help this experimenting with sprinting...
I'm wondering, would anyone would be interested in some sort of mini-IRC sprints or office hours in the next couple weeks? I've been doing my darndest to get caught back up on reading/responding to issues (thanks so much to those who have been helping with that - Carolyn, jhodgdon, eliza411, and silverwing, you are life savers!), but I am wagering that there are people waiting on reviews, or to have questions answered etc.
So yes, just wanted to put that on the table and see what kind of interest there is. If you're interested, please give me a rough idea of ideal times (ie. how many hours off PST you are), and whether during work hours/evening/weekend would be best. It'd probably be ideal to do one or two 1-2hr timeslots where anyone who wants all gets on IRC and works together.
Let me know what you think!
Count me in
I can be available for 1 hour sprints almost anytime. 2 hours would require a little more planning but doable.
Disclaimer: Typically, I find out about critical pitch meetings an hour beforehand. It happens.
I am Chicago/Central time zone (but way down south in Lafayette, LA :) 2 hours ahead of you.
Tuesday (Apr 12) noon PST?
How's a one hour session, noon PST (3pm EST) on Tuesday sound? If even a couple people are up for that I'll post a proper "event" for the group.
_
That sounds great, I can do that. Thanks, Ariane!
Git Conflict
That conflicts with the Git demonstration on April 12, assuming you mean next Tuesday. I wanted to see that, but I also want to help with the sprint. Will you schedule another? Or maybe I can catch the beginning of the Git demonstration, and join the docs group halfway through.
I am available
I am available.
1pm PST?
Oh heck, we don't want to deprive anyone of git training! perhaps 1pm PST instead?
Great!
I'll be there.
I can do that ...
... and thanks for the GIT link. I didn't know about it and wasn't even a member of the group. thx
Booked!
http://groups.drupal.org/node/141359 be there or be documentationless! ;)