Drupal Global Sprint Weekend January 25, 2014 and January 26, 2014

You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

Small local sprints everywhere (well, not everywhere, but anywhere) were held during the weekend of January 25 and 26 2014. Listed alphabetically by continent, country, locality. Wrap-up blog and thoughts for the future

This is a wiki page. Please edit (especially to add links to a blog about how your local event turned out).


Thanks everyone! Please enter data about your local sprint into the spreadsheet.

Africa

  1. Tunis, Tunisia, January 25th and 26th

Asia

  1. Bangalore, India, January 25th
    Update: Drupal Global Sprint Weekend Report!! in comment on event.
  2. Hyderabad, India, January 25th and 26th
  3. Kolkata, India, January 25th and 26th
  4. Pune, India, January 25th and 26th
  5. Osaka, Japan, January 25th
  6. Makati, Philippines, January 25th and 26th

Europe

  1. Leuven/Ghent, Belgium, January 25th (Leuven) and 26th (Ghent)
  2. Berlin, Germany, January 25th and 26th
  3. Mannheim, Germany, January 25th and 26th
    Blog: erdfisch Global Sprint Weekend 2014 by Tobias Stöckler and
    Blog: Sportlich: Drupal Sprint Weekend 2014 bei UEBERBIT
  4. Schwerin, Germany, January 25th and 26th
  5. Budapest, Hungary, January 25th
    Blog: Sprint Weekend In Budapest and Illinois
  6. Groningen, Netherlands, 25th January
  7. Cluj-Napoca, Romania, January 25th
  8. Saint Petersburg, Russia, January 25th
    Blog: Отчет о CodeSprint #4 from konstantin.komelin
  9. Novi Sad, Serbia, 25th January
  10. Sevilla, Spain. January 25th and 26th
    Blog: Drupal Global Sprint Weekend en Sevilla from the Asociación Española de Drupal
    Blog: Drupal Global Sprint Weekend in our Sevilla offices by penyaskito
  11. Barcelona, Spain. January 25th
  12. Zurich, Switzerland, January 25th and 26th
    Blog: Drupal Global Sprint Weekend Chapter in Switzerland: A big success! from @amazeelabs
  13. Glasgow, UK, 25th January
  14. London, UK, 25th and 26th January
  15. Manchester, UK, January 25th
  16. Wroclaw, PL, January 25th
  17. Bucharest, Romania, January 25th

North America (ordered by country, then state)

  1. London, ON, Canada, January 25th and 26th
  2. Montréal, QC, Canada, January 25
  3. Toronto, ON, Canada, January 25th
  4. Vancouver, Canada, January 24th and 25th
  5. Los Angeles, CA, USA, January 25th
  6. Chicago, IL, USA, January 25th
  7. Oak Park, IL, USA, January 26th
    Blog: Global Drupal Sprint Weekend by alimac about the experience of aparticipant, with setup and drush info.
  8. Boston, MA, USA, January 25th
    Pre blog: Acquia puts resources behind work on new Drupal version News about the sprint at Aquia
  9. Twin Cities (Saint Paul, Minneapolis), MN, USA, January 25th and 26th
  10. New York, NY, USA, January 26th
  11. Portland, OR, USA, January 25th and 26th
  12. Austin, TX, USA, January 25th
  13. Bellingham, WA, USA, January 25th and 26th
  14. Milwaukee, WI, USA, January 26th
    Blog: How the Milwaukee Drupal community sprints! by dsnopek

South America (ordered by country, then state)

  1. Campinas, SP, Brazil, January 25th and 26th

To participate,

  • use "Drupal Sprint Weekend 2014" in the description of your sprint meetup, sprint camp session, mini-sprint, wind-sprint, or all-day sprint, like: "Drupal All-day Sprint in Anywhere Town, IL, USA is part of Drupal Sprint Weekend 2014."
  • add a link to your sprint on this page. The link can be to a website, meetup, event on groups.drupal.org, blog post or whatever is appropriate for your event.
  • link back to this listing of local sprints
  • add an "event" of type "sprint" on groups.drupal.org in a group for your area, to put your sprint on drupical.com and get exposure to people in your area
  • use the hash tag #SprintWeekend on twitter
  • use the tag "SprintWeekend2014" on d.o issues

For resources to help plan your sprint:

Resources for participating in a sprint:

A blurb to add to your session/event description (edit to fit your event):

Everyone is welcome; if you have built a site in Drupal, you can contribute. We will split into pairs and work on Drupal core issues. Bring your laptop. If possible, install git before coming and git clone Drupal 8 core. For new folks: you can get a head start also by making an account on Drupal.org and taking a look at the Drupal Ladder http://drupalladder.org/

The curious might want to see the locations from 2013.

Comments

Questions about planning for local event....

stpaultim's picture

I'm curious if anyone can elaborate on what kind (if any) of special resources will be available during the Global Sprint Weekend.

1) Should we plan on there being lots of issues available on the Core Mentoring site? Or do we really need to plan on identifying our own issues prior to the weekend.

2) I'm a little worried that finding easy issues will be harder than usual with so many people all working at once. Is there anything we can do to "claim" a couple of issues in advance so that we don't have to spend most of our time searching for issues on day of SPRINT? Or is there any other special advice you can offer?

3) Are there any special efforts being made to have plenty of mentors available online to help out if we have questions? Any special protocols for Global Sprint Weekend? Are you in need of additional IRC mentors for Global Sprint Weekend?

Tim Erickson
WorkLatte.com

I'm not an expert - this is just my opinion

dsnopek's picture

Pre-warning: I've never organized a sprint before. (But I'm organizing my first one for this global sprint weekend!) So, I'm not an expert - this is just my opinion.

1) I don't know what will be on the Core Mentoring site, but it'd be my advice to spend some time finding issues yourself. In the end, you're the one responsible for making your sprint a success!

2) Have you considered doing a contrib sprint rather than a core one? We're going to pick a couple contrib modules (with buy in from the maintainer) and work on their issues. Since we'll be the only group working on those particular modules, there won't be any competition. :-)

3) Leaving this one for the sprint experts.

Mentors (me included, past

YesCT's picture

Mentors (me included, past mentors, and maybe new mentors who are organizing their own local sprints) will be encouraged to clean out the drupalmentoring.org site of tasks that are no longer good novice introductory tasks (marking them no longer relevant). But... I would also encourage local organizers to make their own list (using a tag on drupalmentoring.org or a google doc). drupalmentoring.org is having some problems pulling in d.o issue meta data (related to json) after the d.o D7 upgrade, but it can still be useful. Local sprint organizers can contact me or other mentors and we can give them the mentor and facilitator roles on the drupalmentoring.org website.

Long term, we are hoping to improve d.o so we dont need drupalmentoring.org anymore. See d.o issues tagged "Core mentoring on d.o" for ways to help make d.o better and drupalmentoring obsolete. :)

On drupalmentoring.org the sprint tag field is useful for making lists of tasks for a particular sprint location. Clicking on the sprint tag from a task takes you to a list for example, http://drupalmentoring.org/sprint/somewhere Replace the word sprint with tasks to get the nice task list like: http://drupalmentoring.org/tasks/somewhere

There is no way to exactly "reserve" issues on d.o. But if you find issues that are a good fit for anyone (globally) you could tag them "SprintWeekend2014", and edit the issue summary to make sure that the remaining tasks/next steps are really clearly identified. And I suppose if you are tagging it there, you could mention you intent to use it at your local sprint. :) On one hand, we dont want to "bump up" too many issues in the main d.o queue ... which was one reason drupalmentoring.org has been useful in the past. On the other, updating remaining tasks (especially with details and links to contributor task documents), tagging (or untagging) Novice or other tags, is helpful for the issue in general, not just for Global Sprint Weekend.

So we do not have people unknowingly working simultaneously on issues, it is highly recommended that when someone begins a task on an issue, they make a comment saying what they are about to do. (And reload the page to see if others have commented.) This will help us avoid stepping on each other's toes during the sprint. Also, please join irc in #drupal and/or #drupal-contribute so we can coordinate.

Cathy Theys

Twin Cities event

stpaultim's picture

Just thought I'd share what we are doing in the Twin Cities - just in case anyone is interested. Would welcome any feedback or suggestions.

We've had two different shops offer space, so we're meeting on Saturday in one location in another location on Sunday. We've set a goal of engaging 30 participants over the two days. We have had 9 register so far (1 week in advance) and there are several confirmed participants that have yet to register.

We're using Eventbrite for registration:

http://www.eventbrite.com/e/twin-cities-drupal-global-sprint-weekend-tic...

And have set up a google doc for open source event planning....

http://bit.do/tcdrupal

If anyone has any additional ideas for us, let us know....

Tim Erickson
WorkLatte.com

Sprints

Group organizers

Group categories

Post type

Group events

Add to calendar

Group notifications

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

Hot content this week