-
Notifications
You must be signed in to change notification settings - Fork 1
SFDO Community Sprints Topic Overview
Github defines Topics as labels that create subject-based connections between GitHub repositories and let you explore projects by type, technology, and more.
We are using Github Topics in the same way but you can see Topics as visual indicators of a projects' overall theme, status, contributor needs, and vertical.
Our open source community needs a way to quickly and efficiently explore repositories in order to find projects that are active, ready for contribution, and that interest them because they meet a particular vertical.
Github Topics can be used to help people find and contribute to your project before, during, and after a Sprint.
Salesforce.org Open Source Program Managers assign Topics to each project prior to a Sprint.
Open Source Program Managers assign Topics based on the information located in a Project's README.md file. To review the requirements of a README file click here.
Note: If you feel a Topic is inaccurate and/or needs updating for a given project feel free to email [email protected] along with a link to the repo and a rationale for your request.
Defines a high-level delivery goal for a given project.
- theme-packaged-app-or-component
- theme-technical-documentation
- theme-video
- theme-best-practice-article-or-blog
- theme-community-ecosystem
Defines the state of a given project.
- status-contributor-ready
- status-not-enough-information
- status-stalled
- status-complete
Defines the roles needed to support the project.
- need-developer
- need-doc-writer
- need-qa-tester
- need-user-stories
- need-project-leader
- need-thought-leader
- need-general-volunteers
Defines the vertical associated with the project.
- vertical-nonprofit
- vertical-education
- vertical-general
- open-source-commons-official
- Metecho
2020 Sprints
- virtual-sfdosprint-March-2020
2019 Sprints
- philly-sfdosprint-2019
- detroit-sfdosprint-2019
- amsterdam-sfdosprint-2019