5 ms·

To be fair, Kubernetes has 2137 issues open right now :)

peterwwillis 8y ago
I don't think there's any defense to this. If you look through the open issues you find stale issues, feature requests with no planned work, already resolved issues left open, "we'll get to it in a couple of releases", etc. Nobody is managing the queue. I know it's a big corporate product, but this is a sign of bad project management, imho. At the very least they could offer to let a community member go through and clean it up if they won't do it themselves.
- ecnahc515 8y ago
  They have a bot which cleans up inactive stuff, marking it as stale, eventually closing issues stale with no activity. Anything worth keeping open is re-opened or a maintainer will tell the bot to un-mark it as stale.
  - peterwwillis 8y ago
    It takes four months to close an issue with the bot. But before it closes, someone comments or removes the tag. There are 195 issues marked stale going back two years.
- parasubvert 8y ago
  It's only bad project management if you believe every issue from every rando on the Internet should be given equal attention. An open issue tracker is a poor metric for project health. IOW, it's popular open source, the Github issue tracker is going to have a lot of noise. What would a community member do that the stale bot isn't doing? What open source project comparable to Kubernetes' scope and interest has an open tracker that exemplifies what you seek?
bpicolo 8y ago
That's a useful thing to note. Kubernetes has a huge surface area, and you will definitely run into issues using it. That complexity is not the right choice for every org
altmind 8y ago
To be fair, issue in kubernetes github are closed after 90+30d of inactivity, so even more "closed" issues were never actually resolved. Check this, +4600 issues that were never addressed, just ignored https://github.com/kubernetes/kubernetes/issues?page=5&q=label%3Alifecycle%2Frotten&utf8=%E2%9C%93 https://github.com/kubernetes/kubernetes/issues?page=5&q=lab...

I don't think there's any defense to this. If you look through the open issues you find stale issues, feature requests with no planned work, already resolved issues left open, "we'll get to it in a couple of releases", etc. Nobody is managing the queue. I know it's a big corporate product, but this is a sign of bad project management, imho. At the very least they could offer to let a community member go through and clean it up if they won't do it themselves.

ecnahc515 8y ago
They have a bot which cleans up inactive stuff, marking it as stale, eventually closing issues stale with no activity. Anything worth keeping open is re-opened or a maintainer will tell the bot to un-mark it as stale.
- peterwwillis 8y ago
  It takes four months to close an issue with the bot. But before it closes, someone comments or removes the tag. There are 195 issues marked stale going back two years.
parasubvert 8y ago
It's only bad project management if you believe every issue from every rando on the Internet should be given equal attention. An open issue tracker is a poor metric for project health. IOW, it's popular open source, the Github issue tracker is going to have a lot of noise. What would a community member do that the stale bot isn't doing? What open source project comparable to Kubernetes' scope and interest has an open tracker that exemplifies what you seek?

bpicolo 8y ago

That's a useful thing to note. Kubernetes has a huge surface area, and you will definitely run into issues using it. That complexity is not the right choice for every org

altmind 8y ago

To be fair, issue in kubernetes github are closed after 90+30d of inactivity, so even more "closed" issues were never actually resolved. Check this, +4600 issues that were never addressed, just ignored https://github.com/kubernetes/kubernetes/issues?page=5&q=label%3Alifecycle%2Frotten&utf8=%E2%9C%93 https://github.com/kubernetes/kubernetes/issues?page=5&q=lab...