こんにちわ！
僕はgithubが大好きなユーザーです。いつも使わせて貰ってます。
質問です。
人気があるリポジトリの中に幾つかメンテナンスされず、pull requestが溜まってしまい沢山forkされてしまっているリポジトリがあります。
これは勿体ないと感じています。
私が提案する解決案として、作者がもうメンテナンスしないと宣言可能にするのと、次のメインの開発者を指定出来るというのはどうかと考えました。
是非先の問題が解決されるのを願っています。
![[削除済みユーザ]](https://secure.gravatar.com/avatar/695023b4efd563721d13716b1457bc73.png?d=identicon&mode=crop&r=PG&s=42)
評価
72
翻訳 / 英語
- 2012/11/29 21:41:50に投稿されました
Hello!
I am a user who loves github. I always use it.
I have a question.
There are some repositories among the popular ones that no longer do maintenance, but have collected many pull requests and been forked many times.
I feel like that is a waste.
I would like to propose this solution: if you make it so that it is possible for the developer to declare they are no longer maintaining the repository, it will be possible to appoint the next main developer.
By all means, I am hoping that the problem mentioned above will be solved.
camelmasaさんはこの翻訳を気に入りました
I am a user who loves github. I always use it.
I have a question.
There are some repositories among the popular ones that no longer do maintenance, but have collected many pull requests and been forked many times.
I feel like that is a waste.
I would like to propose this solution: if you make it so that it is possible for the developer to declare they are no longer maintaining the repository, it will be possible to appoint the next main developer.
By all means, I am hoping that the problem mentioned above will be solved.
評価
58
翻訳 / 英語
- 2012/11/30 07:38:24に投稿されました
Hello!
I am an user who really likes GitHub. I use it often.
On that note, I have a question. Among the popular repositories, there are many repositories which have been forked, but never have maintenance performed on them and have a build-up of pull requests. This seems like such a waste to me.
I would like to propose a resolution to this. What if, when a creator decides that maintenance may no longer be possible, a secondary main developer can be designated?
I truly hope that there can be some resolution to this problem.
camelmasaさんはこの翻訳を気に入りました
I am an user who really likes GitHub. I use it often.
On that note, I have a question. Among the popular repositories, there are many repositories which have been forked, but never have maintenance performed on them and have a build-up of pull requests. This seems like such a waste to me.
I would like to propose a resolution to this. What if, when a creator decides that maintenance may no longer be possible, a secondary main developer can be designated?
I truly hope that there can be some resolution to this problem.
*There are some repositories among the popular ones that are no longer maintained, but have collected many pull requests and been forked many times.