Last updated by ok_lyndsey on Mon, 2017-01-23 13:06
Small local sprints everywhere (well, not everywhere, but anywhere) will be held during the weekend of January 30 and 31 2016. Listed alphabetically by continent, country, locality.
This is a wiki page. Please edit.
Places with Local Sprints
Africa (ordered by country, then city)
Asia (ordered by country, then city)
Europe (ordered by country, then city)
- Ghent, Jan 31 details
- Sofia Jan 31 Details
- Milan, Jan 30 Wellnet Details
- Luxembourg, Jan 30, Technoport - Belval (Esch-sur-Alzette) Details
- Timisoara Jan 30/31 Details
- Bratislava Jan 30 iKOS Slovakia Details
- Zurich Jan 30-31 Amazee Labs Details
Latin America (ordered by country, then city)
Canada & US (ordered by country, then state/province, then city)
- California, Santa Cruz - Jan 30 - Details
- District of Columbia, Washington - Jan 30 - Details
- Illinois, Evanston - Jan 31 - Details
- Illinois, St Charles - Jan 30-31 - Details
- Indiana, Laporte - Jan 30 - Details
- Massachusetts, Boston - Jan 30-31 - Details
- Minnesota, Twin Cities - Jan 30 - Details
- New Jersey, Princeton - approx. Jan 29-Feb 2 - Centered around DrupalCampNJ.
- New York, New York - Saturday, January 28th 10am-5pm: Details
- Oregon, Portland - Jan 30 - Details
- Texas, Austin - Jan 30-31 - Details
- Wisconsin, Milwaukee - Jan 30 - Details
- Washington, Bellingham - Jan 30 & 31 - Details
- Washington, Seattle - Jan 30 - Details
- use "Drupal Global Sprint Weekend 2016" 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 Global Sprint Weekend 2016."
- 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 #SprintWeekend hash tag on twitter
- use the tag "SprintWeekend2016" on d.o issues (no # in this tag name!)
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 groups and work on Drupal core issues. Bring your laptop. For new folks: you can get a head start also by making an account on Drupal.org, getting some contribution tools, and developers can install git before coming and git clone Drupal 8 core.
Resources to help plan your sprint
- d.o doc: What is a sprint?
- d.o mentoring doc: Resources for sprint planners: How to plan a sprint
- 2016 podcast: Dropcast Episode 14: You can host a Global Sprint Weekend sprint with YesCT and mediacurrent folks
- blog: Planning your own local Global Sprint Weekend January 25 and 26 2014 Sprint
- 2013 DrupalCon Portland session: video on sprint planning and mentoring by xjm, ZenDoodles, add1sun, YesCT
- 2013 podcast: There is no crying in sprints from DrupalEasy
- 2014 podcast: 084 Global Sprint Weekend 2014 with Cathy Theys - Modules Unraveled Podcast with webflo.
- 2014 podcast: Global Sprint Days from Lullabot
- irc planning meetings, ask any questions about planning or participating during the regular office hours: in #drupal Tuesday 02:00 UTC and Wednesday 16:00 UTC
Resources for participating in a sprint
(needs updating for 2016, but this is a start)
- Drupal 8 change notifications
- Resources for contributed module developers: upgrading your modules to Drupal 8. Look at git logs and 8.x issues from modules that have already started a 8.x branch. As you port, first commit a 7.x version as initial 8.x, and make frequent public commits (and issues in your issue queue!). In those commit messages: 1) say what you did, *and* 2) add "per ...." and site the change record, or link to an example in another module that led you to think that was what needed to be done. The "per" is really useful. See also the Pants example module.
- Use irc, and post a comment when about to work on an issue.
- Drupalize.me free Community videos
Issues and Topics to Sprint On
Initiative leads and module maintainers should create and link to planning pages.