question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Investigate track health and status of the track

See original GitHub issue

I’ve used Sarah Sharp’s FOSS Heartbeat project to generate stats for each of the language track repositories, as well as the x-common repository.

The Exercism heartbeat data is published here: https://exercism.github.io/heartbeat/

When looking at the data, please disregard any activity from me (kytrinyx), as I would like to get the language tracks to a point where they are entirely maintained by the community.

Please take a look at the heartbeat data for this track, and answer the following questions:

  • To what degree is the track maintained?
  • Who (if anyone) is merging pull requests?
  • Who (if anyone) is reviewing pull requests?
  • Is there someone who is not merging pull requests, but who comments on issues and pull requests, has thoughtful feedback, and is generally helpful? If so, maybe we can invite them to be a maintainer on the track.

I’ve made up the following scale:

  • ORPHANED - Nobody (other than me) has merged anything in the past year.
  • ENDANGERED - Somewhere between ORPHANED and AT RISK.
  • AT RISK - Two people (other than me) are actively discussing issues and reviewing and merging pull requests.
  • MAINTAINED - Three or more people (other than me) are actively discussing issues and reviewing and merging pull requests.

It would also be useful to know if there a lot of activity on the track, or just the occasional issue or comment.

Please report the current status of the track, including your best guess on the above scale, back to the top-level issue in the discussions repository: https://github.com/exercism/discussions/issues/97

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
stkentcommented, Nov 21, 2016

Can confirm that maintainers have responded in a very timely manner and with very thorough responses to the aforementioned PRs 👍

0reactions
kytrinyxcommented, Nov 24, 2016

Thanks, all, for weighing in!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Investigate track health and status of the track #156 - GitHub
Please take a look at the heartbeat data for this track, and answer the following questions: To what degree is the track maintained?...
Read more >
Monitoring and tracking the disease | CDC
Collecting data from medical records (chart abstractions) can tell us more about COVID-19 patients and the course of their disease. These data ...
Read more >
How to check Microsoft 365 service health
View the health status of Microsoft 365 services before you call support to see if there is an active service interruption.
Read more >
Track a detection investigation - ExtraHop Documentation
Detection tracking enables you to assign users, set a status, and add notes to a detection card. You can also filter your view...
Read more >
Public Health Surveillance: A Tool for Targeting and ... - NCBI
timely and complete receipt, review, and investigation of disease case reports, including the prompt recognition and reporting to or consultation with health ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found