Open jbergstroem opened 7 years ago
Yeah- I had a convo with @piscisaureus about this at collab summit. One thing to note is that slurp is collecting logs for many channels- ie non foundation channels. We'd need to decide if the foundation is ok with supporting the others...? Or only taking on some of them...?
I'm a big fan of small and focused projects, so I'd much rather have an IRC-bot separate from the github-bot.
+1 to put such a project under governance of the github-bot team.
On Saturday, 8 October 2016, Johan Bergström notifications@github.com wrote:
Just saw that http://logs.libuv.org/channels was down again (has been for 4 days). Last time it went down I suggested we could move it to the node.js infra so more people could help out keeping it going then quickly forgot about it once it was back up. This time I thought I'd bring it up here as a task that could be integrated into our bot?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nodejs/github-bot/issues/85, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLLEwOqdCQf9LJTqnGHHFrOusUOpIwuks5qx6-TgaJpZM4KRvbS .
The other channels are mostly stale - I would stop logging them if I cared enough.
Sorry for the downtime :(
@jbergstroem any objections against running this as a separate project / deployment? Guess we could re-use the server the bot is currently running on..
@phillipj not at all -- it just seems to fit in this working group.
Just saw that http://logs.libuv.org/channels was down again (has been for 4 days). Last time it went down I suggested we could move it to the node.js infra so more people could help out keeping it going then quickly forgot about it once it was back up. This time I thought I'd bring it up here as a task that could be integrated into our bot?