These are chat archives for cherrypy/cherrypy

1st
Jun 2017
Sviatoslav Sydorenko
@webknjaz
Jun 01 2017 07:59
@mbarkhau I think moving all of the collected information into GitHub issue is safer way to keep track and avoid losing opinions. So feel free to go ahead and create a ticket :)
@jaraco I've found this bot, which is watching stale issues https://github.com/apps/probot-stale
Do you think we could use its help in cherrypy organization?
Jason R. Coombs
@jaraco
Jun 01 2017 13:54
@mbarkhau: Filing a ticket, especially one that captures the requirement and any research toward it, will increase the likelihood that someone else will be able to pick up where you left off, so if you can spare the time, please do.
jaraco @jaraco had typed that message but not hit enter before getting distracted.
Jason R. Coombs
@jaraco
Jun 01 2017 13:57
@webknjaz I think that could help. One of the problems with something like CherryPy is there are so many open tickets that it’s a huge backlog. It looks like the bot would do everything I’d like. I’d probably not use wontfix as the label, but have a distinct label (like backlog or stale) for tickets closed by the bot. That would be very helpful, and it would create a fair incentive for the poster to advance the conversation or let it slide.
I approve.
Sviatoslav Sydorenko
@webknjaz
Jun 01 2017 15:51
@jaraco would you please enable in for the organization? I don't have sufficient privileges myself. It will only start working after config file pushed into master.
Jason R. Coombs
@jaraco
Jun 01 2017 15:57
@webknjaz : Done
For all cherrypy projects.
(for the record)
@webknjaz: I’ve just changed your role in the org from Member to Owner. Enjoy, but use responsibly.
Sviatoslav Sydorenko
@webknjaz
Jun 01 2017 17:28
sure, thanks