Repositories overview and actions #1
Conversation
sheplu
force-pushed
the
clean-organization
branch
from
082c0fd
to
57365e2
Compare
|
if / when we are all good with the decisions in this PR (after change and discussion if needed) I will archive/delete all repositories @expressjs/express-tc |
|
While I think this is a good first step, there are so many things we need to align on across all the repos. I am unsure a markdown table will be enough will it? |
The point of this PR is just to do a first step of cleaning, not all actions. But this would allow us to agree on which repos we are removing (empty ones), which one we are archiving (not used, with code not deployed), and which one we keep. It is just for us to agree on this list, and then after that we will consolidate a list of repositories we will have to work on. |
|
Ok awesome. Sounds good as long as we are going to do something a bit more "high fidelity" for all that other stuff to make it easier to read. |
|
I think for a more global approach for all packages we should
|
|
We could use a GH project board for that. They are fairly easy to setup if we wanted. I think across the orgs doesn't quite work right unless they are in an enterprise account but we could just setup one for each org and link to those in here? |
|
this would also work, I never really tried that feature :) |
| | [qs-strict](https://github.com/pillarjs/qs-strict) | 0 (1) | 9 years old | archive | | ||
| | [request](https://github.com/pillarjs/request) | N/A | where? | archive | | ||
| | [resolve-path](https://github.com/pillarjs/resolve-path) | 0.8 | 6 years old | update and keep OR archive | | ||
| | [router](https://github.com/pillarjs/router) | 0.6 | - | update and keep OR archive | |
There was a problem hiding this comment.
This is the core router in express 5 so should be keep (unless we're refactoring code back into express).
There was a problem hiding this comment.
Oh yeah for sure! This is absolutely keep. The main work is on the 2.0 branch. I was planning on (as I volunteered to be the project captain) to get that merged and make it more clear what is going on in there. I just have not yet had a chance to do that.
| | [timeout](https://github.com/expressjs/timeout) | 0.22 | 7 years old | update and keep OR archive | | ||
| | [urlrouter](https://github.com/expressjs/urlrouter) | 0 (142) | 10 years old | archive | | ||
| | [vhost](https://github.com/expressjs/vhost) | 0.12 | 8 years old | update and keep OR archive | | ||
| | [vhostess](https://github.com/expressjs/vhostess) | 0 (22) | 10 years old | archive | |
There was a problem hiding this comment.
We're missing 2 repos here:
There was a problem hiding this comment.
they are already archived so not part of the list
| | [ssl-redirect](https://github.com/pillarjs/ssl-redirect) | 0 (43) | 9 years old | archive | | ||
| | [templation](https://github.com/pillarjs/templation) | 0 (27) | 9 years old | | | ||
| | [understanding-csrf](https://github.com/pillarjs/understanding-csrf) | N/A | reuse the doc | archive | | ||
| | [view](https://github.com/pillarjs/views) | N/A | - | remove | |
There was a problem hiding this comment.
We're missing 1 repo here:
There was a problem hiding this comment.
they are already archived so not part of the list
Here is the list of all repositories that are currently marked as "active" in the three organizations (Express, Pillarjs, JShttp).
Some / a good numbers of them are empty or count for almost no downloads.
This PR is to validate and agree between TC members which repositories can be archived or deleted completely (only if the repository was empty)
Some repositories are representing a small amont of download per week but still suffisant to discuss if we want to maintain them or deprecate them.
After all repositories are deleted or archived, it will be necessary to deprecate the packages on npmjs.org