From d43feafb8fbfddb9fd5ad03a4710740ffeea4763 Mon Sep 17 00:00:00 2001 From: Roshni Pattath Date: Sat, 6 Jun 2020 16:21:54 -0400 Subject: [PATCH 1/3] Triaging issues --- os-team-workflow.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 os-team-workflow.md diff --git a/os-team-workflow.md b/os-team-workflow.md new file mode 100644 index 0000000..246c2de --- /dev/null +++ b/os-team-workflow.md @@ -0,0 +1,12 @@ +

Opensource Project Workflow

+

Issue Workflow

+ +* Untriaged issues are checked for validity and triaged by project managers. +* During triage: + * Label is set to `Status: Available` if the issue is valid. + * Label is set to `Status: On Hold` if additional information or discussion id required regarding that issue. + * Issue is closed if it is not valid. + * At least one label from each of `Category` and `Type` should be set. + * Label `First Timers Only` can be set if the issue has simple fix. + * Label `Help Wanted` can be set if the issue has a higher priority to be fixed. + From 5205fb8d8c91b6d5821d89034025698ccc5943b2 Mon Sep 17 00:00:00 2001 From: Roshni Pattath Date: Sat, 6 Jun 2020 19:08:42 -0400 Subject: [PATCH 2/3] PR workflow --- os-team-workflow.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/os-team-workflow.md b/os-team-workflow.md index 246c2de..80d74ab 100644 --- a/os-team-workflow.md +++ b/os-team-workflow.md @@ -9,4 +9,24 @@ * At least one label from each of `Category` and `Type` should be set. * Label `First Timers Only` can be set if the issue has simple fix. * Label `Help Wanted` can be set if the issue has a higher priority to be fixed. +* Assigning issues: + * Contributor interested in working on a PR for the issue can comment on the issue. + * Issues with label `Status: First Timers Only ` can be assigned to contributors who have never made a contribution to any github project. + * 1 contributor should have only 1 assigned issue at any time. + +

Pull request workflow

+ +1. When creating a Pull request for an issue, make sure all the firls of the PR template is filled in. +2. Project managers triage the PR and label `Status: Needs Review`. +3. Request 2-3 project contributors from coding team for code review. Comment on the PR requesting code review to the @anitab-org/coding-team. +4. Once the PR has at least 2 approvals for code review, project managers can change the label to `Status: Needs Testing`. +5. Request at least 1-2 project contributors from the QA team for PR testing. Comment on the PR requesting code review to the @anitab-org/qa-team. +6. If the PR is high priority the label `Help Wanted`. +7. If there is a question or further discussion is needed for the PR add the label `Status: On Hold`. +8. If the testing is successful (the PR has approval fromat least 1 tester). A comment is added by the tester using the [template](https://github.com/anitab-org/mentorship-backend/blob/develop/docs/test-pr-guide.md#template-to-report-pr-testing-results). +9. The label is changed to `Status: Ready to Merge`. Contributors with Merge permissions make sure the test report looks good before merging. + +

Change request during code review or testing

+1. Changes needed are comment by the code reviewers and the label is changed to `Status: Changes Requested`. +2. After the changes are commited the PR repeat steps 3-8 of Pull request workflow. From e5f33e642e07445d6887fafe80dcd705900837e4 Mon Sep 17 00:00:00 2001 From: Roshni Pattath Date: Sat, 6 Jun 2020 19:09:23 -0400 Subject: [PATCH 3/3] new line missing --- os-team-workflow.md | 1 + 1 file changed, 1 insertion(+) diff --git a/os-team-workflow.md b/os-team-workflow.md index 80d74ab..15bc3a9 100644 --- a/os-team-workflow.md +++ b/os-team-workflow.md @@ -27,6 +27,7 @@ 9. The label is changed to `Status: Ready to Merge`. Contributors with Merge permissions make sure the test report looks good before merging.

Change request during code review or testing

+ 1. Changes needed are comment by the code reviewers and the label is changed to `Status: Changes Requested`. 2. After the changes are commited the PR repeat steps 3-8 of Pull request workflow.