Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Go through Turing's/REG's OS repos #11

Open
mhauru opened this issue Sep 15, 2023 · 1 comment
Open

Go through Turing's/REG's OS repos #11

mhauru opened this issue Sep 15, 2023 · 1 comment

Comments

@mhauru
Copy link
Collaborator

mhauru commented Sep 15, 2023

We could do a manual sweep through our repos and note/fix basic things, such as:

  • Archive dead repos
  • Note which ones have pending issues, collect this information, maybe go fix some of the issues or find someone else to do so
  • Check the status with regards to
    • Is there a license?
    • Does anyone appear to be using this repo?
    • Is the repo maintained to any degree?

The aim would be to get an overview of how well/badly we are doing on this front, to find low-hanging fruit to pick in terms of fixes and improvements, and to catch any cases where some Turing repo has been neglected but actually has users demanding maintenance.

This could be semiautomated by a tool like #9, but I might advocate for a manual sweep to get started, since that tool doesn't exist yet. Welll, now that I said that, I note that the Turing org has 452 public repos, which is more than I expected, so, hmmm...

@JimMadge
Copy link
Member

An interesting problem but tricky.

I'm not sure who has the authority to delete/archive repositories.

I do think it is a bit embarrassing to have so many dead repositories. Practically it also hides the good stuff in the noise.
To anyone in the know, I think it is obvious that the Turing is not able to actively maintain so many projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Planning
Development

No branches or pull requests

2 participants