You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
The text was updated successfully, but these errors were encountered:
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.
We could do a manual sweep through our repos and note/fix basic things, such as:
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...
The text was updated successfully, but these errors were encountered: