Repository navigation
GitHub Process
Process 1. The first to create our Github page was to fil out the ReadMe with the project's goal, main core features and add every member. Once the core features were well understood, we created issues containing the core features. The core features were labelled as Web-User Stories and the syntax followed the user stories guideline from the teacher's slides. The core features are as followed:
- Asking and Answering Questions
- Voting on the answers
- Accepting the best answer
Under each core features, there is a task list with every tasks or features related to the core feature. Each of them are assigned to a team member.
Milestones of the project were created. These milestones are sprint 1,2,3,4. These allow to keep track of when the issues and pull requests needs to be closed or merged. It also separates the estimation of effort from the estimation of duration.
Once the developpers finish coding their assigned task from the issue/core feature, they create a Pull Request containing the code. This will create a branche which should be named after what you are working on (example login_info). You assign other teammates to review your work. You select the milestone it should be merge for and a label. A label describes what type of work you are doing (example; enhancement, bug fix)
If two developpers are working on the same code and are helping eachother, they can create a compare branche.
Every time their is an issue of any sort, an issue is created with the corresponding characteristic. This way all the team members can help as it is a group project (scrum).
Every time the team meets a wiki page is created containing the meeting minutes.