preparing for a sprint, would be good to have a list of candidate issues

xjm suggested the candidate tag could be fine.

suggested tag is:
SprintWeekend2015Queue

I suggest when someone adds it they use some version of this statement in their comment:

Identifying this as a potential good issue for Sprint Weekend. See discussion at #2407325: preparing for a sprint, would be good to have a list of candidate issues. Adding sprint queue tag.

If this is worked on during the sprint, please add the tag SprintWeekend2015. Add a comment when you start work saying what you are about to do, so we can coordinate.

tagging issues is something people forget. we can ask them to install http://webflo.github.io/drupalsprint-bookmarklet/ ...or justafish might have made one to automatically do it.

@penyaskito I would go with no. we have 45 locations. that's a lot of tags.
If local places have a particular focus, like a module, or topic, hopefully they can use another way of filtering the advanced search so they dont need their own local tag.

also

https://gist.github.com/clemens-tolboom/7e15dac5bfb07a729f6e ( http://bl.ocks.org/clemens-tolboom )
We should think about updating and asking people to install it.
I seem to remember a request from ams was for a timer (a date comparison), so that after the sprint it didn't keep adding the tag.

0) log in to drupal.org
0.5) get into irc.freenode.net #drupal-contribute

When someone finds an issue they might want to workn on:

1) follow it
2) read the summary and info
3) read first few comments
4) read few most recent comments
5) pick a task that needs to be done (issue summary might have a list, or found one reading the comments). A task might be, review a change record, draft a change record, manually test, make a screenshot, update the issue summary, review a patch, review mockup or screenshot, verify bug stil exists in head, update a patch based on feedback from a review and post a new patch and interdiff, reroll an old patch to apply on head and post that new patch (no interdiff for rerolls), add automated tests and post interdiff and new tests only patch and patch combining the fix and tests, ....
6) before begin to do the task,
6a) reload the issue page (lok for any new comments)
6b) if no-one has posted a new comment saying they are doing the same task you picked, then you post a comment saying which task you are about to do. Add the SprintWeekend2015 tag.
6c) paste a link to the issue into irc, and say what task you are about to begin doing
7) later... ask questions in irc and in new comments on the issue
8) later... post half done or half working result, ask more questions
9) before leaving the Sprint (for lunch, dinner, or to go home) post your work, ask questions, suggest next steps, update the issue summary, make sure the issue status is appropriate. Say you are done for now, for the night... whatever.
9b) if you go to post your work, and someone already has done what you did, that can be frustrating and disappointing. But, you are in an excellent position to post feedback or questions about what they did.
10) when you return from a break, reload the page and look for new comments.

Note, there are often many tasks to do, so work with others on the same issue, but communicate as to who will do which task.

If you are stuck, pick a second issue to also work on at ththe same time... but don't work on too many moving each only forward a little. Instead, focus on 1 or 2, doing many of the tasks, until you cannot do anymore. Try and get issue rtbc, or as close to rtbc as you can.

If you finish a task and identify a next step on the same issue, ask around (in your room, or in irc) if someone is looking for something to do, if the task you identify is good match for them, help them do the task.

Thinking about drupalcon LA , I think instead of a separate queue tag, we can just ask sprint organizers (maintainers, initiative managers, other people taking an organizing role) to pre tag some issues with the regular sprint tag we use.

This would

• prepopulate the tag, so it is at the top of tag autocomplete results (which was is now fixed to sort by most used yay! #2362065: Sort autocomplete of issue tags descending by usage count *in the issue metadata form* and #2398379: Sort autocomplete of issue tags descending by usage count *on advanced search page*)
• represent the work that happens in advance of a sprint, by the organizers as part of the "work" done at a sprint
• safe some confusion of switching tags, or a "wrong" tag being added

We should also decide on a tag, if we stick with the recent pattern at cons, it would be
LosAngeles2015
(no spaces, no hash # symbol)

This is not just for mentoring. And the origin of having a tag for sprints (at DrupalCon) was afaik, a request from @Dries because he wanted to have a way of finding out what was worked on at a sprint to be able to tell how effective the investment in having a sprint was. And so he asked that we try and get every issue touched during the con sprint to have the tag. We have discussed other ways of trying to gather data about what issues get worked on at a sprint, like db queries, but each has it's downside.

Personally, as a way of organizing which issues should be worked on, I would prefer that component/topic/initiative organizers just use the sprint tag to ... tag their items that should be current priorities, ... but that is it's own can of worms.

I suggest for Barcelona: Barcelona2015