Skip to content
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

Open
jbergstroem opened this issue Oct 8, 2016 · 6 comments
Open

IRC logger #85

jbergstroem opened this issue Oct 8, 2016 · 6 comments

Comments

@jbergstroem
Copy link
Member

@jbergstroem jbergstroem commented Oct 8, 2016

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?

@williamkapke
Copy link
Member

@williamkapke williamkapke commented Oct 8, 2016

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...?

@phillipj
Copy link
Member

@phillipj phillipj commented Oct 8, 2016

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
#85, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLLEwOqdCQf9LJTqnGHHFrOusUOpIwuks5qx6-TgaJpZM4KRvbS
.

@piscisaureus
Copy link
Member

@piscisaureus piscisaureus commented Oct 8, 2016

The other channels are mostly stale - I would stop logging them if I cared enough.

@piscisaureus
Copy link
Member

@piscisaureus piscisaureus commented Oct 8, 2016

Sorry for the downtime :(

@phillipj
Copy link
Member

@phillipj phillipj commented Oct 18, 2016

@jbergstroem any objections against running this as a separate project / deployment? Guess we could re-use the server the bot is currently running on..

@jbergstroem
Copy link
Member Author

@jbergstroem jbergstroem commented Oct 18, 2016

@phillipj not at all -- it just seems to fit in this working group.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.