Freenode IRC Admin #22
Comments
|
I've assigned @mrosseel, @ManfredKarrer and myself to this role, as we three in fact have op rights in #bisq and #bitsquare. @mrosseel is the only one actively managing this, though, and we should consider what we want to do going forward with these rights. It would be better to get the keys out of my and Manfred's hands, and into another new and active operator so we have at least two who are responsible. |
2017.12 reportLike @ManfredKarrer, I am only technically a Freenode Admin. It's really @mrosseel that's doing the work here, showing up every day, answering questions etc. @mrosseel, could you start providing monthly updates here from your side? It can be a simple one-liner if there's nothing to report. |
2017.12 reportNothing special to report, apart from the fact that the topic has been indicating the pending move from #bitsquare to #bisq for some time now, so it could be done any time now. Will be postponed till the bridge discussion is concluded. |
|
I think it's worth mentioning above, @mrosseel, something about the work you do moderating / answering questions in IRC as well. I don't track this closely, but when I do look at |
2018.01 reportNot many discussions on IRC, not much effort was needed to keep up this month. |
2018.01 reportThanks, @mrosseel. I have nothing to report, as I had no involvement with IRC this month. Going forward, I'll let you do these updates. I'm happy to keep my op status in Freenode, but will play a passive role from now on and won't do further reports here unless something changes. |
2018.02 reportNot a 'monthly report' per se, but I just noticed that the |
2019.03 - 2019.04 (Cycle 1) reportNothing to report Hosting 1 syncing node on a shared server with monitoring node. Because of the disabled syncing and not spending much time on IRC, no compensation will be requested for this period. |
Cycle 2&3 reportSince I don't spend a lot of time on IRC a new maintainer would be good for the IRC department Hosting 1 syncing node on a shared server with monitoring node. The #chat-bridge channel on slack was reenabled and resulted in better IRC response times by various contributors (special thanks to Homard) |
Cycle 4 reportHosting 1 syncing node on a shared server with monitoring node. The #chat-bridge channel is still helping us keeping an active presence on slack |
Cycle 5 reportHosting 1 syncing node on a shared server with monitoring node. The #chat-bridge channel is still used so good for PR |
Cycle 6&7 reportMoved the slack and irc bridge to Matrix, this has the advantage that it's always up (as long as the matrix servers are up) |
Cycle 8&9 reportThe #chat-bridge channel on slack is still being used, mirroring matrix/irc/slack. |
Cycle 10&11 reportNothing to report. |
Cycle 12 reportNothing to report. |
Cycle 13 reportNothing to report. |
Cycle 14 reportNothing to report. |
Cycle 15 reportNothing to report. |
Cycle 16 reportNothing to report. |
Cycle 17 reportNothing to report. |
Cycle 18 reportNothing to report. |
This role is responsible for administering the
#bisqand (legacy)#bitsquareFreenode IRC channels, as well as the#chat-bridgebot / channel in Slack. Owners of this role haveop(operator) status in Freenode IRC terminology.Docs: none, other than the above
Team: @bisq-network/irc-admins
Primary owner: @mrosseel
The text was updated successfully, but these errors were encountered: