Workflow

1. The work starts with the Tech PM, he sets up the repo and its base structure, defines whatever base test is needed, and along with the PM they define the tasks/issues to be done.

2. Then the Repo Managers (RMs) take charge of the Repo and make sure every part of the repo is arranged as it should be. README.md is properly written, and the CONTRIBUTING.md file is in place. The Wiki is up and documents concerning the project have been properly documented. They also check alongside the PMs to make sure all the necessary tasks needed to complete the project have been listed on the issues page.

3. Next is the Coders, they start work on the defined tasks/issues by self assigning the tasks they want and giving the PMs a timeline to complete the choosen tasks. Once they are through, they put up a proper PR (as deifned above), and wait for the verdict.

4. The Code Review (CR) team jumps in and checks to see if the code is clean, DRYied and properly structured, they review the PR and give appropriate comments as to what is needed to make the code merge-able.

5. After CR is done, the Testing team (TT) will check if tests have been properly added, run tests on it and make sure the code is working as it should.

6. The PR team comes up after CR and TT have both given a thumbs up. They do the defined merge test and if all is good, they merge, else they comment, requesting the necessary changes.

7. All through this, the RMs are checking to make sure everything is where it should be, and the necessary documents are being updated and listed.

8. Once all tasks (endpoints and all) have been done, and the Code base is all that and a bag of chips, the Server Deployment (SD) team pushes the API live on the defined Cloud site and with the agreed URL.

9. Finally, the general channel checks to make sure all endpoints are working fine, and the API is good to go. And voila! States & Cities v2 is a-live and done.

Check the list of teams to see each of these above mentioned teams