-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IRC logger #85
Comments
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 +1 to put such a project under governance of the github-bot team. On Saturday, 8 October 2016, Johan Bergström [email protected]
|
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. |
After 8 years, and considering that we mostly don't use IRC anymore, I think this can be closed. |
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?
The text was updated successfully, but these errors were encountered: