2.1 Git Repos and branch reference
Repo | URL | Branch | Description | Staging Server |
|---|---|---|---|---|
Safe Places Front End | Latest production code | |||
Latest development code | ||||
Safe Places Back End | Latest production code | |||
Latest development code |
|
2.2 Code Submission Etiquette
Devs should associate work with a git issue
If issue exists, tech lead may assign it to a dev
If issues does not exist, dev create create issue and self-assign
Tech lead + PMs will categorize issues against Jira stories
2.3 Community Roles
Role | Responsibilities | Requirement | Privileges | Defined by |
|---|---|---|---|---|
Member | Active contributor | Has multi contributions Sponsored by 2 reviewers | Have issues and PRs assigned to them Participate in SIGs through GitHub teams | Safe Places GitHub org member |
Reviewer | Review PRs and proposals | History of review and authorship in an area | Review code for quality and correctness on some part of the project | OWNERS file reviewer entry |
Approver | Approve PRs and proposals | Highly experienced and active reviewer and contributor to an area | Both review and approve code contributions | OWNERS file approver entry |
Maintainer | Manage and control project permissions and health | Highly experienced contributor active in multiple areas and roles | GitHub path-check/repos write access | Maintainers team in GitHub org |
0 Comments