this isn't necessarily something docs team needs to do, but webchick was talking about something like this
http://img.skitch.com/20100220-xenw54sj34r61hrxp7j75exk27.png
that can be used for various types of tasks, so they can easily be handed out or direct people to them....
(more later, gotta sleep!)
Comments
Comment #1
webchickHi. :)
Yes, so a couple times now I've been doing this sort of ad-hoc sprint format where we just tell a bunch of people to show up, and based on who does and what they're interested in, break them off into little teams around the room: for example, "Document all the D6 => D7 API changes" and "Write SimpleTests" and "Roll in handbook comments" and what have you. But what happens is I'm running around like a crazy person helping one team at a time to get oriented in what their task entails, and in the meantime everyone else is checking email, etc. Also I can't possibly be at every local user group in every town in every country, as much as I'd like to be. ;)
So my idea was to create a template for a one-page "cheat-sheet" that could explain to folks what skills are required to help with the task, what the end goal is and why it's important to work on it, step-by-step instructions for how to do X thing, and then a list of resources for more info. (Possibly other stuff; totally open to ideas.)
For various "teams" who have sort of ongoing tasks that just kind of always need help (you can never have too much test coverage, for example), they would fill out one of said template forms, and then people holding local sprints could print off the sheets that they either felt comfortable leading others in, or the group wanted to learn more about, and leave them on the tables. This way the designated "cat herder" could spend their time answering specific questions rather than re-iterating the basics for each of these tasks over and over. These could also double as great "How to get involved in X" pages in the handbook.
Anyway, it's totally just a concept, but it might be a way for us to be more productive at sprints in general (like the upcoming ones at Drupalcon SF), and also to lower the barrier of entry to those who want to throw a similar event in their own area (they're TONS of fun!)
Comment #2
bekasu commentedSee if the changes to this: http://drupal.org/node/424194, are helpful.
Since I've never been a cat-herder, someone should jump in here and add more to the last paragraph.
Also, please check that the files download and open. I don't have word on my machine, so I can only check the openoffice.
Comment #3
arianek commentedhey bekasu -
i just tightened up the language on the handbook page to make it a bit stronger, but this looks like a good start. the task sheet template is really basic, but i think that's ok to start with, and hopefully if this is useful, people will upload completed versions with more info that can be re-used!
i'm wondering if we shouldn't find another spot or two in the handbook to link to this from as well, i don't know that i'd ever find it where it is!
Comment #4
bekasu commentedarianek ---
I agree completely.
I think the disconnect is the title 'documentation sprints'. The forms I added to the page are generic enough for any type of sprint.
Like here; http://drupal.org/node/247982
or here: http://drupal.org/node/247987
also wouldn't hurt to provide info to drupal.groups but i don't know which ones. But perhaps rather than hijack this thread, we should open up a new issue.
bekasu
Comment #5
arianek commentedhmmm... well we really do need the sorts of people who run sprints, and specialists in the areas to fill out the template and repost... i think that's part of this same issue. i'm not entirely sure how to bring this to their attention..... maybe a g.d.o post cross posted to... ?
Comment #6
bekasu commentedwould really be nice if we had an 'interactive' form profile -- you select the type of sprint, the form prefills the usual skills needed, gives you a place to put in who, what, where, when, how .. then saves it for you so you can print or link to it.
sadly, we are stuck in a static world for a bit longer isn't it?
bekasu
Comment #7
arianek commentedyeah, you're totally right, that would be ideal... hmm... i wonder if it wouldn't just be best to create some templates as book pages and try to get some sprint leader types to just write in the details, then the book pages can just be printed. (???)
Comment #8
bekasu commentedI like that idea.
Might be a good idea to review whats happening at drupalcon in sf and see if we ping some of the 'likely suspects' for help... of course, so we can help them help themselves in the future.
;)
Comment #9
Crell commentedSubscribing.
Comment #10
figaro commentedThe idea really calls for a digital format and a printable version posted at the Drupalcon, similar to the design @#0. Except that I would not call it a "cheat sheet" for reasons which should be very obvious.
Comment #11
jhodgdonCheck out http://drupal.org/new-contributors -- took bekasu's sprint templates and made it into a whole section. :)
Meanwhile, I think this issue has been addressed.