- Show respect for others as classmates, teammates, and professors/technical leads
- Allow peers to voice their opinions and consider all opinions
- Participate regularly in class sessions
- Keep interruptions to a minimum
- If you are confused or unable to keep up with the course content, ask a question during that same class session
- Remain logged on to Discord during class
- Respectfully bring up any disagreements with others and keep any extended disagreements outside of class/lab session when practical
- Remain in the building during lab session although you are welcome to go work in other areas of Alden
- Display academic honesty in your collaboration with others
- Be respectful.
- Send messages into the correct channel or thread.
- Only use appropriate language.
- Do not share the server link with others outside of the organizations.
Issue Tracker
-
Label with accurate and descriptive issue type (use available labels)
-
Assign yourself and teammates to corresponding issue
-
Briefly and accurately describe the issue at hand and the possible solution
-
Address issues quickly and don't let them sit longer than 1 week
-
Track them through the project board
Pull Requests
-
Assign yourself and 3 other teammates to the PR
-
The title of the pull request should match the issue that it is addressing (issue number)
-
Leave detailed comments before accepting or rejecting a pull request
-
Review assigned pull requests at least 2 days before assignment is due
-
Always add Dr. Jumadinova and/or a TL to the PR
-
A minimum of 2 reviewers must approve the PR before merging to the
main
ormaster
branch
Commit Messages
- Use format:
Action verb: description
Members of this class must show respect for all peers as learners and team members, allow peers to voice their opinions and questions, and read, understand, and follow all parts of this code of Conduct. Every team member needs to be actively and cooperatively involved with the projects at hand. This will ensure the flow of questions, ideas, and thoughts in a respectful manner. Our project at its root includes participation, candidness and insightful collaboration. Participating in project discussion means engaging in conversation, not just answering questions. The goal here is to show up and truly be all there. The majority of individuals in a team should agree on a given decision before the project is implemented. It should be made with supporting evidence that shows that the decision is productive. When unsure about making a decision it is a good idea to defer to a technical leader or the professor. One should reach out to other teams whom the choice will influence. Teams will determine how long a decision will take to implement. Members of this class will resolve conflicts before they become severe by engaging in respectful conversations, with the course instructor having final say in how severe conflicts should be resolved.