archive this repo? - Githubissues

expressjs / vhostess

virtual host sub-domain mapping

25 stars 7 forks source link

archive this repo? #1

Open gireeshpunathil opened 4 years ago

gireeshpunathil commented 4 years ago

ref: https://github.com/expressjs/discussions/issues/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 commented 4 years ago

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

dougwilson commented 4 years ago

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 commented 4 years ago

I agree @dougwilson. Archive seems the best solution 👍