Issue management: discuss caine again
When things have just started with io.js, I proposed to use a "gentle buttler" bot caine for the purposes of tagging and assigning the issues. It has been awhile since then (a bit more than 1 year), and I think it is a right time to discuss it again.
This doesn't mean that the bot should be used as it is, though. I just want to see a possibility of off-loading issue tagging and mentions of github groups to some automated system (which is sadly not provided by github itself).
What are your thoughts on this @nodejs/ctc
and @nodejs/collaborators
? What should be changed in caine in order to make it useful for us?
Thank you, Fedor.
P.S.
A bit of personal reasoning for this: I was watching the joyent/node
repo years ago, but the number of email notifications was just killing my productivity and trashing my inbox. So I decided to unwatch it, and pick the issues where people mention me, or rarely pick them manually from the issue tracker (assuming someone has tagged them with crypto
, tls
or anything else). Having automated system which will notify core devs about new issues that are relevant to their scope will definitely be much more useful to me, and hopefully to others too.