Help Us Design a New Git(Hub) Organizational Dashboard

[This article was first published on rOpenSci - open tools for open science, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

We have developed a prototype dashboard which aims to help organizations maintain complex systems of inter-dependent software components. Our initial prototype organizational dashboard provides insights into code contributors, their repositories, and maintenance status and needs. The prototype dashboard shows data for the three related GitHub organizations, reconhub, epiverse, and epiverse-trace, all of which develop and host open-source software for understanding and analysing epidemics. We aim to develop the current prototype as a template for adoption and adaptation by other open-source organizations.

Main prototype dashboard page. There are four cards, the top left one shows the total number of packages and below that it lists the organizations ordered from largest to smallest by the number of packages they have. The top right card shows the number of package that needs urgent maintenance. It lists those packages with a link. The bottom left card shows total numbers of commits for all repositories, including a graphical representation. The bottom right car show total activity on GitHub, also including a graphical representation.

Organizational overview sections from main prototype dashboard page.

Network connections between packages.

Interactive network diagram connecting packages in the organization.

The primary aim of the dashboard is to help all people involved with, or interested in, either those epidemic-related organizations or rOpenSci, through providing an organization-wide overview of the state of code repositories and the community activity which sustains them.

Help design and develop our dashboard!

We are seeking help in the further design and development of our prototype organizational dashboard, both for the organizations featured there, and more generally for a planned rOpenSci-wide dashboard. You can help us by providing suggestions for any ways you think the prototype organizational dashboard could be improved. If you’re a contributor to, or maintainer of, an R package, we’d particularly like to hear about any ways the dashboard could be made more useful for you. Please make comments either in this blog post, or via or discussions in the associated GitHub repository. Want to give private feedback? No worries, email me directly.

A few notes

  1. The dashboard is built on a huge wealth of data, so presume any data you can think of from full git logs and GitHub APIs are already there and could be used.
  2. Those data include time series of most things measured, even though many are only presented as snapshots of the latest time period.
  3. Given those 2 points, the biggest challenge is reducing these data to some minimally meaningful amount.

Thank you!

Thank you! Interested in contributing in other ways to rOpenSci? Please have a look at our contributing guide.

To leave a comment for the author, please follow the link and comment on their blog: rOpenSci - open tools for open science.

R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)