Developers at source{d} dedicate 10% of their development time to Open Source projects of their choice. This is accomplished with Open Source Days (OSD) every two weeks, on Mondays.
The result of OSD MUST be Open Source, whether it is code, prose, a dataset or a beer recipe. We generally use public GitHub repositories for this. They can be either in a personal account, a dedicated organization or the src-d organization.
OK. Actually, OSD is part of every source{d} developer's job. But the decision on what to do on OSD should be driven exclusively by your interests. While you can work on a source{d} project such as go-git, we also encourage you to work on something not related to your daily job.
- Share your plan. You should briefly explain what you are going to do and what do you expect to accomplish by the end of the day. Explanations about the project you're going to contribute are done in the
#osdslack channel, in the beginning of the day. - Do it. Execute your plan for the day and push it!
- Presentation. At the end of the day, everyone presents their work in the
#osdslack channel with the corresponding source code and description.