I am going to try instituting a new requirement moving forward. When any team member writes a piece of code, I have a few expectations before that piece of code can be considered complete. This is to help make sure that our final product is valuable to others, and also to make sure that the division of labor is fair. Here are the expectations:
The code needs to be included in a repository commit
The code must be commented. The author will take 10 minutes during a regular meeting time to explain the code to everyone. Teach the team what you know/discovered!
A Wiki page explaining the code's purpose, function, and organization must be written before the author moves on to a new project.
In addition, I think that team communication is important, and it isn't getting the attention it deserves. This is why I created the HipChat page, but there are ways you can tell your classmates what you are working on right here on Github-- Branches and Pull Requests.
The basics are: When you are about to do something, create a "branch" for the repository that describes the changes you are about to make. When you are done, you create a "pull request" to allow others to look at your changes before merging your "branch" of the code into the main repository. We will discuss this in class tomorrow, but the basics are simple.
Your classmates should know what you are working on, and you should know what they are working on. You need to work together!
@macjones743 @megantuttle @wangzeyi @dallisg711
I am going to try instituting a new requirement moving forward. When any team member writes a piece of code, I have a few expectations before that piece of code can be considered complete. This is to help make sure that our final product is valuable to others, and also to make sure that the division of labor is fair. Here are the expectations:
In addition, I think that team communication is important, and it isn't getting the attention it deserves. This is why I created the HipChat page, but there are ways you can tell your classmates what you are working on right here on Github-- Branches and Pull Requests.
Here is a tutorial on Pull requests: https://yangsu.github.io/pull-request-tutorial/
The basics are: When you are about to do something, create a "branch" for the repository that describes the changes you are about to make. When you are done, you create a "pull request" to allow others to look at your changes before merging your "branch" of the code into the main repository. We will discuss this in class tomorrow, but the basics are simple.