Software Engineering Project (IS F341)
We have followed Scrum framework thorughout this project. All the scrum project reports are available in the scrum/ directory.
Complete project was divided into 3 sprints of 3 weeks each. Each sprint had 6 daily scrums, 1 sprint planning, 1 sprint retrospective meets.
- Frontend (ReactJS): Frontend Link
- Backend (NodeJS + Express): Backend Link
- Ujjwal Raizada
(Scrum Master) - Satyam Mani
(Product Owner) - Daksh Yashlaha
(Developer) - Prakhar Goenka
(Developer) - Pranjal Gupta
(Developer)
- ReactJS
- ExpressJS
- Atlas MongoDB
- Bootstrap 4
We love contributions. That out of the way, an average contribution would involve the following:
- Fork this repository in your account.
- Clone it on your local machine.
- Add a new remote using
git remote add upstream https://github.com/ujjwalrox/student-utility-portal.git. - Create a new feature branch with
git checkout -b my-feature. - Make your changes.
- Commit your changes.
- Rebase your commits with
upstream/master:
git checkout mastergit fetch upstream mastergit reset --hard FETCH_HEADgit checkout my-featuregit rebase master
- Resolve any merge conflicts, and then push the branch with
git push origin my-feature. - Create a Pull Request detailing the changes you made and wait for review/merge.
It might seem a little complicated at a glance, but the fundamental concept is simple: we want to ensure that your changes are always made on top of the latest changes to the project and thus, we can easily merge your code.
The commit message:
- is written in the imperative (e.g., "Fix ...", "Add ...")
- is kept short, while concisely explaining what the commit does.
- is clear about what part of the code is affected -- often by prefixing with the name of the subsystem and a colon, like "server: ..." or "docs: ...".
- is a complete sentence, ending with a period.