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

archive this repo? #1

Open
gireeshpunathil opened this issue Jul 3, 2020 · 3 comments
Open

archive this repo? #1

gireeshpunathil opened this issue Jul 3, 2020 · 3 comments

Comments

@gireeshpunathil
Copy link

ref: expressjs/discussions#134

@jonathanong - you have been identified as the last / most active committer in this repo which is inactive for a while. This ping is to check with you to determine:

  • whether do you have any specific maintenance plans with this repo
  • are you fine for this repo to be archived
  • do you believe if there is another stake holder / affected party who should know

thanks!

@jonathanong
Copy link
Member

¯\_(ツ)_/¯ i guess so

@dougwilson
Copy link

Thanks @jonathanong ! I just looked at this is published to npm, so probably makes sense to archive vs delete. Though in a way, it does seem more general than the Express.js project itself (works with a few different things, is not an express-specific middleware, etc.). We could relocate it to the pillarjs org, though we'd want to clean that one up too. If this is just "dead", we should probably archive it + move it to the archive ("sloth") organization.

@UlisesGascon
Copy link
Member

I agree @dougwilson. Archive seems the best solution 👍

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

No branches or pull requests

4 participants