proj2rubric

|Notes|Assessment (Total : 87 )|Evidence|
|-----|---------|----------|
|Video1| 3| A video showing the functionality of the previous project is included in [README.md](https://github.com/kunalshah03/PackReview_Part2/blob/main/README.md) |
|Video2| 3| A vidoe of the updated and scaled app with the new functionalities is included in [README.md](https://github.com/kunalshah03/PackReview_Part2/blob/main/README.md) |
|Bonus: Xfold improvement| 3 | Highlighted in [README.md](https://github.com/kunalshah03/PackReview_Part2/blob/main/README.md)|
|Docs: what: point descriptions of each class/function (in isolation)| 3 | Mentioned in respective README.md inside the respective folders |
|Use of style checkers | 3 | Pylint used|
|Use of code formatters. | 3 | Pylint used|
|Use of syntax checkers. | 3 | Pylint used|
|Use of code coverage | 3 | Coverage badge is present in README|
|Other automated analysis tools| 3 |Used github actions|
|Workload is spread over the whole team (one team member is often Xtimes more productive than the others... but nevertheless, here is a track record that everyone is contributing a lot)| 3 | Everyone has committed and contributed equally. [Visible in Insights -> Contributors](https://github.com/kunalshah03/PackReview_Part2/graphs/contributors)|
|Number of commits| 3 | There were a lot of commits [Present in Insights -> Contributors](https://github.com/kunalshah03/PackReview_Part2/graphs/contributorss) |
|Number of commits: by different people| 3 | Everyone has committed in different areas. [Visible in Insights -> Contributors](https://github.com/kunalshah03/PackReview_Part2/graphs/contributors)|
|Issues reports: there are **many**| 3 | Issues were raised and resolved. [Visible in Issues](https://github.com/kunalshah03/PackReview_Part2/issues) |
|Issues are being closed| 3 | A lot of issues were opened, resolved and closed [Visible in Issues](https://github.com/kunalshah03/PackReview_Part2/issues?q=is%3Aissue+is%3Aclosed) |
|DOI badge: exists| 3 | Visible in [GitHub Repository](https://github.com/kunalshah03/PackReview_Part2) |
|Docs: doco generated, format not ugly | 3 | Documentation is present with all the blings! [GitHub Repository README.md](https://github.com/kunalshah03/PackReview_Part2) |
|Docs: how: for common use cases X,Y,Z mini-tutorials showing worked examples on how to do X,Y,Z| 0 |No such examples or tutorials found|
|Docs: why: docs tell a story, motivate the whole thing, deliver a punchline that makes you want to rush out and use the thing| 3 | Documentation includes the story, punchline and would motivate anyone to rush out and use the thing|
|Docs: short video, animated, hosted on your repo. That convinces people why they want to work on your code.|  3| Animation video present in [GitHub Repository README.md](https://github.com/kunalshah03/PackReview_Part2)|
|Use of version control tools| 3 | GitHub was used by the team|
|Test cases exist| 3 |Test cases are present in tests folder. [see here](https://github.com/kunalshah03/PackReview_Part2/tree/main/tests)|
|Test cases are routinely executed| 3 |Test cases are executed|
|The files CONTRIBUTING.md lists coding standards and lots of tips on how to extend the system without screwing things up| 3 | File is present and clear instructions are available|
|Issues are discussed before they are closed| 3 |Issues were discussed before closing|
|Chat channel: exists| 3 | Slack channel exists [See here](https://github.com/kunalshah03/PackReview_Part2/blob/main/Data/Screenshot%20(37).png)|
|Test cases: a large proportion of the issues related to handling failing cases.| 0 | No issues found|
|Evidence that the whole team is using the same tools: everyone can get to all tools and files| 3 | Everyone has contributed to different files|
|Evidence that the whole team is using the same tools (e.g. config files in the repo, updated by lots of different people)| 3 | |
|Evidence that the whole team is using the same tools (e.g. tutor can ask anyone to share screen, they demonstrate the system running on their computer)| 3 | |
|Evidence that the members of the team are working across multiple places in the code base| 3 | Team members have been found contributing in different area|
|Short release cycles | 3 | Regular commits and releases have been made|