add dashboard to website on who is doing what/how much

[maxheld83]

it'd be nice if we could at some point have a visualisation on the class website, how much individual participants are contributing to the repo, and in what form.
Might give everyone an idea of where there stand.

Obviously, this shouldn't shame people or stress them out, so this needs careful design.

Also, this would be a pretty big job. More like graded-10

[maxheld83]

couple of links:

• Talking to the GitHub API from R:
  • https://github.com/r-lib/gh
• Building dashboards
  • shiny: https://shiny.rstudio.com/
  • flexdashboards: https://rmarkdown.rstudio.com/flexdashboard/ (those are static do not require a runtime)
  • shinydashboard: https://rstudio.github.io/shinydashboard/ (those require a shiny runtime)
• Github-based dashboards:
  • https://github.com/unconf-toolbox/unconfissues
  • https://emilyriederer.github.io/projmgr/index.html

[maxheld83]

one more thing to consider is how often this is supposed to be updated:

if we update once per git event (i.e. push), then that's easy, we can use the runtime on the CI/CD server (here: github actions, visible from the actions tab) to rerun whatever github api calls we want on every commit.

if however, we want to rerun the whole thing on every issue event, it get's a bit more complicated, because we might have to run a shiny runtime the entire time and poll GH from time to time.
We can do that, but shiny runtimes are pretty heavy/expensive.
We can use our FAU account to run it on at http://shinyapps.io.

Theoretically, we could also leverage github actions to do this work, by triggering on every issue event (github actions can trigger on a bunch of GH API events: https://developer.github.com/actions/managing-workflows/workflow-configuration-options/).
This would be pretty cool, though it would have a significant lag, because we'd need to run the whole rmarkdown::render_site() on every commit event.
It's also possible we'd overwhelm GitHub actions / or get a horrendeous queue.

[PaddyGlass]

Thank you (this is a test)

[maxheld83]

probably not working on this any more.
Just for completeness sake @PaddyGlass @Crisphi could you open placeholder issues here on fossos to track what projects you're working on? Perhaps with a link to the repo where you're doing the actual work.

[maxheld83]

ah sorry, never mind @PaddyGlass @Crisphi already done in #179 and #178