docs: new code of conduct

This commit is contained in:
Aysegul Aydinlik 2025-11-27 15:35:47 +01:00
commit 26de27fda0

View file

@ -1,46 +1,54 @@
# Code of Conduct CSEP
> Last changed: 2025-11-14 04:20 PM
## Assignment description
- working on our teamwork skills
- coding with other people
- communication skill in a group setting
- Working on our teamwork skills "by helping eachother and working with eachother"
- Coding with other people "by working together in gitlab and in person"
- Communication skill in a group setting "working in a project with 6 people"
## Target or ambition level
- so we working towards a 10 but a 8 is fine
- the most important thing is that everyone does their best
- So we working towards a 10 but a 8 is fine
- The most important thing is that everyone does their best
## Planning
- friday - before the ta meeting checking eachother codes and making a planning for the week after
- label the to do lists in gitlab on friday (during planning time)
- check up on eachother thoughout the week
- **Submitter** - Rithvik
- We will at least meet in person 2 times a week with preference to thursday and friday
- We will meet 1 time a week online on monday
- We will have an organic planning with code because we will need to see week to week what we can do and what we can achieve
## Communication
- Discord for our online meeting and sharing info and asking questions
- GitLab to share our code
- Friday lab meetings for in person meetings
- Thursday and Friday lab meetings for in person meetings
### Collaboration outside of the mandatory meetings
- Friday during lab before ta meeting
- Discord
- Thursdays (to code together and help eachother)
- Friday during lab before ta meeting (to make the final changes before merging)
- Discord (for our quick questions about the small things)
- GitLab
## Help and assistance
- We have discord together, so if there is a question or issue it can be asked there and also during the friday meeting
- If someone is really struggling we make sure to help them in person based on the part they're working on client or server
## Work quality
- By having the other 5 members rate the code on gitlab
- By having the other 3 members rate the code on gitlab
- Making sure we use the same checkstyle document
- Making sure we also talk about what we want to see in the form of comments + style of code
## Decision-making
- Discuss it with arguments so consensus
- Using polls for our meet up location or decisions that are yes or no
- If someone want to change something they have to bring up the arguments for why the change is good
## Broken agreements
- Discuss it with them
- If they dont do anything (work, meetings) at all discuss with the ta
- If someone breaks the agreements we have agreed upon in this code of conduct we will first of all discuss it with them
- If someone isn't collaborating at all we will make this clear to the TA and hope they can help
- If that doesn't resolve it we will bring it up with the lecturer
- Never will we just exclude someone without taking the proper step
## Problem resolution
- We are all adults here so we can just talk it out by civil discussion
- If your gonna be late, communicate with the rest of the team
- Give a reason if you can't show up for a meeting
- Contact with the TA will be needed when someone doesn't react to any of our messages and doesnt show up at all
- Never escalate any problem if there is a big problem discuss it with the TA or lecturer depending on the severity of the problem