目前的“退休”最佳做法是， github和npmjs.org上的项目？ [英] Current best practice for "retiring" a project on github and npmjs.org?

问题描述

我是github（和npm）上公共项目的维护者。当我创建该项目时，它比可用的替代方案更好地解决了我的特殊需求但是，社区已经赶上并超越了我的解决方案。我甚至不使用我创建的工具，我对维护它不感兴趣。我更新了自述文件以达到这种效果，但我仍然收到请求。我应该简单地把它拿下来吗？这被认为是粗鲁的，因为别人正在分化它并试图贡献？到目前为止，我没有让这些人接受作为其维护者的责任。

I'm the maintainer of a public project on github (and npm). When I created the project it solved my particular requirements better than available alternatives. However, the community has caught up and surpassed my solution. I don't even use the tool I created any more, and I'm not interested in maintaining it. I updated the README to this effect, but I'm still getting pull requests. Should I simply take it down? Is this considered rude given others are forking it and trying to contribute? So far I've had no luck getting these others to accept responsibility as its maintainer(s).

我不是在寻找任意的主观意见，而是一些证据这种共识 - 可能是以文件形式或来自公认的权威机构的方式。

I'm not looking for arbitrary subjective opinions, rather evidence of some kind of consensus -- perhaps in the form of documentation or a howto from a recognized authority. Thanks.

推荐答案

1. 编辑 README.md 并放置一张大闪亮的弃用通知，告诉这已不再受支持，请考虑使用XXX


2. 使用 npm deprecate 每次安装都会有一个弃用通知。

1. Edit README.md and place big shiny deprecation notice telling "this is no longer supported, please consider using XXX instead"
2. Use npm deprecate to place a deprecation notice on every install.

这被认为是粗鲁的，因为其他人正在努力并努力贡献？

Is this considered rude given others are forking it and trying to contribute?

是。

这篇关于目前的“退休”最佳做法是， github和npmjs.org上的项目？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！