ubc-mds / video_game_sales_dashboard Goto Github PK

Let's meet and discuss Thursday 7pm!

Reflect on what you think your dashboard does well what its limitations are, and what are good future improvements and additions. This section should not be more than 500 words and the reflection-milestone2.md document should live in your GitHub.com repo in the doc folder.

• Add a Dockerfile and a docker-compose.yml files to allow the users run your app locally.

• Write clear instructions at the end of the README.md on how to run the app locally.

Reactivity - How do you generate a reactive plot? Can you indicate (1) the basic way to create a reactive plot, (2) how to create a plot reactive to more than one input and, (3) how to create more than one reactive output (for example, having a plot and text to print on the screen)?

Mahmood - Section 1: Motivation and Purpose
Alex - Section 2: Description of the data
Amelia - Section 3: Research questions and usage scenarios

• You can create your own favicon based in an image or dowloading one. You should place it as favicon.ico in a folder called assert in the root of the project.

• Add a title

app.title = "my title"

Once you have finished the work for this milestone you must create a release on GitHub.com before the submission deadline.

• Please read the GitHub documentation on how to create a release via the online interface. Name your release with the respective milestone name.

• We will grade all files in the repo at the state they were in when you created the release. This means that you can continue to make changes in the repo without worrying about messing up your grading for the previous milestone.

You should paste in Gradescope the link to the GitHub repo

• Remember to add in Gradescope all the members of the group

Paste in Gradescope the link to the team work contract and the link to the GitHub repo
Add in Gradescope all the members of the group

• To finalize the dashboard

Instructions in the repo:
https://github.com/UBC-MDS/DSCI532-peer-review

You will give peer feedback to the group one number higher than you. So if you are group 5, you give feedback to group 6. If you are the last group (30), you will feedback group 1. You should be able to find your feedback groups’ repo in the MDS organization on github.com. If they did not include their group number in the repo name, you can let me know and I can help you find it.

To give valuable feedback to another group, you will pretend to be their target audience. To do this effectively, you will need to read section 1 (motivation) and 3 (usage scenario) of their proposal and also skim their README.

All the groups will have to paste issue in the groups repo, where you write your feedback. Name the issue “Peer feedback”, so that it is easy to find. When you give feedback, try to both include what you like about the dashboard and want the group to keep as well as what you think can be improved. You don’t need to make this overly long, aim for around three things you like about the dashboard, and around three things that you think could be improved. The group will respond to your feedback and try to implement some of it in milestone 4. It is fine to comment on style, colors etc, but aim to have at least one point about a bigger picture issue, these are often the most helpful feedback.

Need 5 improvements. Please put related PRs here.