{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/test-infra/issues/6903","repository_url":"https://api.github.com/repos/kubernetes/test-infra","labels_url":"https://api.github.com/repos/kubernetes/test-infra/issues/6903/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/test-infra/issues/6903/comments","events_url":"https://api.github.com/repos/kubernetes/test-infra/issues/6903/events","html_url":"https://github.com/kubernetes/test-infra/issues/6903","id":298673255,"number":6903,"title":"opting out of fetja-bot?","user":{"login":"bacongobbler","id":1360539,"avatar_url":"https://avatars2.githubusercontent.com/u/1360539?v=4","gravatar_id":"","url":"https://api.github.com/users/bacongobbler","html_url":"https://github.com/bacongobbler","followers_url":"https://api.github.com/users/bacongobbler/followers","following_url":"https://api.github.com/users/bacongobbler/following{/other_user}","gists_url":"https://api.github.com/users/bacongobbler/gists{/gist_id}","starred_url":"https://api.github.com/users/bacongobbler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bacongobbler/subscriptions","organizations_url":"https://api.github.com/users/bacongobbler/orgs","repos_url":"https://api.github.com/users/bacongobbler/repos","events_url":"https://api.github.com/users/bacongobbler/events{/privacy}","received_events_url":"https://api.github.com/users/bacongobbler/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-02-20T17:05:13Z","updated_at":"2018-02-20T20:16:11Z","closed_at":null,"author_association":"NONE","body":"Hey, over at kubernetes/helm we'd like to opt out of fetja-bot from marking issues as stale. Any way we can disable this bot for the project? Thanks!"},"comment":{"url":"https://api.github.com/repos/kubernetes/test-infra/issues/comments/367105179","html_url":"https://github.com/kubernetes/test-infra/issues/6903#issuecomment-367105179","issue_url":"https://api.github.com/repos/kubernetes/test-infra/issues/6903","id":367105179,"user":{"login":"bacongobbler","id":1360539,"avatar_url":"https://avatars2.githubusercontent.com/u/1360539?v=4","gravatar_id":"","url":"https://api.github.com/users/bacongobbler","html_url":"https://github.com/bacongobbler","followers_url":"https://api.github.com/users/bacongobbler/followers","following_url":"https://api.github.com/users/bacongobbler/following{/other_user}","gists_url":"https://api.github.com/users/bacongobbler/gists{/gist_id}","starred_url":"https://api.github.com/users/bacongobbler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bacongobbler/subscriptions","organizations_url":"https://api.github.com/users/bacongobbler/orgs","repos_url":"https://api.github.com/users/bacongobbler/repos","events_url":"https://api.github.com/users/bacongobbler/events{/privacy}","received_events_url":"https://api.github.com/users/bacongobbler/received_events","type":"User","site_admin":false},"created_at":"2018-02-20T20:16:11Z","updated_at":"2018-02-20T20:16:11Z","author_association":"NONE","body":"> in general there is a large backlog of stale issues that serve no purpose\r\n\r\n> ...and the vast majority of issues open for this long (where nobody interacts with them!) are not relevant any longer.\r\n\r\nWith all due respect - for Helm in particular - I strongly disagree that these stale issues serve no purpose. A [large amount of our older issues](https://github.com/kubernetes/helm/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc) are either proposals or feature requests, all of which are fantastic features for Helm. It's usually the case that nobody's had the time to implement them, or we're waiting for the Helm Dev Summit (starting tomorrow) to discuss whether we want to consider them for Helm 3. For the core maintainers, we now have to sift through hundreds of tickets just to ensure that these enhancement proposals won't be closed. That doesn't bode for a great experience as a core maintainer of the project.\r\n\r\n> it will take 90+30+30=150 days or half of a year (!!!!) to be closed if nobody ever interacts with them in that time\r\n\r\nIt's probably a bug, but we've discovered that the stale issue bot will continue its lifecycle even after a user has commented on a stale or rotten issue, as if that user never commented. An example can be found [in this ticket here](https://github.com/kubernetes/helm/issues/3005).\r\n\r\n> The small fraction of issues that are untouched for half of a year and still relevant can be marked as such with /lifecycle frozen and that is a small price to pay for the valuable feature of stale issue closing in general.\r\n\r\nPerhaps for kubernetes, sure. But for Helm, we have about 70 open feature requests and 84 open proposals, all of which have discussions lasting several months. This is a significant chunk of our ticket queue (>40% of currently open issues). For us, this isn't a small fraction of issues; it's a large majority of them. :)\r\n\r\nIn conclusion, fejta-bot has probably been the single-most controversial \"feature\" that has been turned on for the Helm project. There were no announcements, no visibility or no option to toggle the bot on or off, and if you gauge community feedback via reactions to fejta-bot's comments, you can clearly tell that the Helm community doesn't appreciate it either. I'm not wild about having someone not associated with the project (read: not part of the [core maintainer list](https://github.com/kubernetes/helm/blob/master/OWNERS)) turning \"features\" on and off for us. The model should be that projects opt in for best practices, not top-down enforcement that we have to fight to opt out of after the fact.\r\n\r\nI am kindly asking for us to have the option to opt out of features turned on by test-infra, including the stale issue bot. If there is a way I can make that happen, please let me know and I will be more than happy to donate my time to work on a fix."}}
{"actor":{"display_login":"bacongobbler"}}