8000 Who Can Do What? · Issue #20 · YaleSTC/yalestc.github.io · GitHub

More Web Proxy on the site http://driver.im/

Who Can Do What? #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

caseywatts opened this issue Nov 17, 2014 · 0 comments

Contributor

caseywatts commented

For the Security Design Review we have to post somewhere a description of who can do what.

Code Editing Workflow

Student Developers can

edit code on their own feature branches
submit pull requests

Team Leads can:

merge in pull requests of proposed changes by team members
tag releases
deploy changes to the development server, roll back a failed deployment
request production server deployment from Unix Systems / Infrastructure
request help from Unix Systems / Infrastructure

Managers can

grant read/edit access to our public/private repositories
do anything student developers and team leads can do

Unix Systems / Infrastructure can:

retrieve a database dump for debugging purposes, providing it to student developers
use the rails console to execute ruby commands provided by Team Leads, often to fix bugs
deploy changes to the production server, approved by Team Leads. Roll back a failed deployment.

Pull Request Review Policy

code changes are normally reviewed by at least 3 people (often 2 developers pair programming, and the team lead as the third person)
(pull from our wiki more details? or the email I sent last semester?)

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

0