Planning for Cambridge Sprint

[KirstieJane]

Let's start making a list of things we need to figure out for the Cambridge Sprint.

• Date

  • Mid-may?

• Time

  • All day? Saturday? Day into evening so some people can come from industry??
  • Suggestion: 2pm to 9pm on a weekday with the following 3 modules:
    • 2pm to 4pm - Intro to GitHub and how to contribute to open source projects. Ideal for people who aren't confident in their understanding of how they can contribute to the project. This session will get everyone set up with a GitHub account and by the end everyone will have submitted their first pull request. We'll have to do a bunch of planning to make sure there are some sensible good-first-bugs to implement in this time frame.
    • 4:30pm to 6:30pm - Brainstorming ideas and project planning. This two hour session will be mostly around pitching ideas about how to develop the app and how to implement them. Everyone will work in groups to propose an issue that they can work on, and then pitch it to the group. There will then be a round of editing and commenting on the suggestions (on github) and a final pitch to the room. The team members do not need to be able to implement these ideas themselves, rather they will be trying to be as clear as possible for whichever experts come along! However, if they are able to implement the ideas then that would be fantastic!
    • 7pm to 9pm - Implementing the suggestions. In the final two hours, we'll be joined by developers from industry who will be able to help implement the ideas that have been proposed in the previous session. Everyone is welcome to stay and learn from the developers.

• Location

  • University centre? Makespace?
    Makespace is better for food - we'd probably have to order through the university otherwise. Only drawback is the need to have a member there for the whole time.
  • Needs wifi access (including for people outside the university)
  • Needs plugs and desks for laptops

• Advertising

  • Open Con Cam
  • Cambridge neuroscience
  • Cambridge Codebar
  • Cambridge Women and Technology meetup group
  • Cambridge Software Craftsmanship meetup group

  I've written a draft email but it's WAY too long. Any help editing it would be great!

What else should we consider?

[KirstieJane]

Some thoughts from @KirstieJane's conversation with @arlissc:

(To be formatted when it isn't time for a dog walk)

?? Remote participation? Can people join in by gitter chat room etc? Live stream?

Food 👍 Coffee ☕

Email

Eventbrite planning

Make a poster - based off

Check in
Signage to find the room etc
Map on website

Swag

Tweets

Reminder emails - More details as you get closer

Parking
Security

Toilets

Schedule - emphasise what pre-requisites are required

Second section: Pitches. GitHub - issues. Would it be better to edit in the etherpad? Faster?

Pitches: White board? Marker? Slides? Projector?

Wrap up plan: Toronto left hour at the end for demos.

If you can only make it to one - Please come to the 4:30 to 6:30 session.

Make sure there's time to meet people. Community building.

Sprint - short burst of energy - short burst of effort.