After conference sprint (CiviCon SF 2013)

There are no hard and fast requirements for attending a sprint, apart from a desire to work on improving CiviCRM in some way and the time to do it. We'll choose 2 or 3 areas to work on (based on participants' interest) and split into teams to tackle these areas. The idea is that we can work on improving CiviCRM and increasing your skills and knowledge at the same time.

Having skills in specific areas like coding, documentation, writing tests, etc. is great but not a requirement. A desire to further develop your skills and to help others through "peer learning" is required! Examples of work that we've done previously at sprints include:

• documenting new and upcoming features
• improving usability of current features getting your code improvements generalised and incorporated into CivICRM
• improving test coverage
• squashing bugs
• discussing, improving and finalising requirements for up and coming features

By the end of the sprint we'll have made some significant progress in a couple of areas in CiviCRM, and you'll have the tools to continue working on your projects outside of the sprint. You'll also have gotten to know people in the CiviCRM community a lot better, and there's always GREAT food at sprints.