The following are guidelines for organizing guide the research and development activities related to the SKOPE project. They are meant to These guidelines make it easy for anyone in the project to know what is going on and to given . They give everyone the opportunity to comment on planned opportunity to comment on and participate in planned and ongoing activities and to contribute to planning, development, and testing.
...
Code in shared Git repositories
- Any and all All software developed as part of the SKOPE project is expected to be made available to the entire SKOPE team (and to the public whenever possible) via team via pushes to shared Git repositories , ideally in GitHub.
- Any code developed specifically for SKOPE is expected to can be found in Git repositories in the openskope GitHub organization.
- Code that also pertains directly to funded projects other than SKOPE may be stored in repositories associated with other GitHub organizations (or other Git hosting service). For example, the YesWorkflow code base is in the yesworkflow-org GitHub organization.
- Summary: Code unavailable to the SKOPE team via shared Git repositories doesn't exist.
...
Planned and ongoing development activities in JIRA
All JIRA items described meaningfully for all SKOPE team members
...
- All significant development activities sponsored by SKOPE are represented by one or more JIRA issues.
- Each issue is phrased in terms that allow anyone who regularly attends our biweekly project meetings to understand why the issue is significant to the project.
- Issues in progress are made part of the current sprint.