Should the requirements rest in the Wiki or in the Repository?

[ilgazer]

The requirements will be one of the most referenced and altered documents in this project. We will be making alterations on it in each meeting, and also different subgroups will be elaborating on different parts throughout this process. I believe that using the main repo will be helpful in these ways:

1. We can track changes over time with the git history and different commits.
2. We can separate out the requirements into different documents, as we create more elaborate requirements for each part of the system.
3. We can use issues and pull requests to track the progress of different tasks.
4. We can use different branches and pull requests to deconflict the work of different people. As an example, one person might be working on categorising our requirements into functional and non-functional requirements while someone else is typing up the new requirements decided on in the last meeting with the customer. Currently, there isn't a good way to merge the work of these two groups.
5. We will gain more experience with git, which we can use in 451 in the next semster.