Sunday, Feb. 21st, 9am - 12:30pm PST
Where: Venueless (note: you'll need a PyCascades ticket to access Venueless). If you have any questions, or are unable to access Venueless you can watch this brief video, then request help in the PyCascades Slack (join now).
About the Sprints
Sprints offer an excellent opportunity to get contributors and developers together and to squash several bugs in a relatively short time.
The mentored sprints at PyCascades focus on providing less experienced developers with a supportive environment in which they can learn, collaborate, expand their network, and celebrate their victories at the end of it.
Furthermore, it serves as an excellent opportunity for some open source projects to get some practical advice around inclusion and how to serve a global and diverse pool of contributors. And perhaps establish longer-term mentor-mentee or contributor relationships.
Q: I am new to Python or have never contributed to an open source project, is this an event for me?
A: Definitely! We will have mentors and helpers at hand to support you through your open source contributions. We will also be providing an introduction to Open Source Contributions for those new contributors around the 9am PT start time.
Q: Do I have to contribute code?
A: Coding is not the only way in which you can contribute to an Open Source project, there are many ways in which you can help. For example, you can help writing or improving documentation, helping design a new logo, improving a project's website or help triage open issues or review other's contributions.
Q: What will I need on the day?
A: You will need access to PyCascades Venueless and Slack channel. We have also prepared some handy guides for you to get the basics of your development environment up and running: https://mentored-sprint-for-diverse-beginners.readthedocs.io/01_contributor_resources.html
Q: I would like to mentor or help on the day. Do I have to be a project maintainer?
A: Not necessarily, you can mentor others if you've got some open source experience. We are also always looking for helpers on the git desk to help with those pesky git issues such as merge conflicts and the occasional scary rebasing.
Q: Do you have a Code of Conduct?
A: Yes, the PyCascades Code of Conduct applies to the sprints.
If you have any other questions that are not covered in the FAQs please feel free to reach out to Tania Allard and Eric Holscher by @-mentioning them on the PyCascades Slack or e-mailing them at email@example.com and firstname.lastname@example.org.