<div dir="auto">As an alternative to meetbot - in the future - maybe we could consider logbot? <a href="https://mozilla.logbot.info/">https://mozilla.logbot.info/</a><div dir="auto"><br></div><div dir="auto">I have found it very helpful and feature full, with full text search online.</div><div dir="auto"><br></div><div dir="auto">We could invite it only for meetings, and/or we could start publicly logging public channels.</div><div dir="auto"><br></div><div dir="auto">-tom</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 11, 2019, 3:03 PM Antoine Beaupré <<a href="mailto:anarcat@torproject.org">anarcat@torproject.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello!<br>
<br>
I'm your new friendly sysadmin! I hope I'm doing good. I'm also not a<br>
bot and should be able to pass a turing test on a good day. ;)<br>
<br>
I've so far prioritized my work mostly towards sysadmin-specific stuff<br>
(like rebuilding parts of the broken monitoring system and generally get<br>
up to speed with everything), but I'm sensitive to priorities people<br>
from the Tor project express, obviously...<br>
<br>
One of those recurring issue I've heard (other than "OMG Trac is pain!"<br>
of course) is that "MeetBot is down!" The service is ran by the good<br>
folks at Debian, but has fallen somewhat in disarray in recent<br>
years. All the gory details are of course in Trac:<br>
<br>
<a href="https://trac.torproject.org/projects/tor/ticket/29680" rel="noreferrer noreferrer" target="_blank">https://trac.torproject.org/projects/tor/ticket/29680</a><br>
<br>
... but the short story is that I've considered setting up a replacement<br>
when the service was completely offline. Since then, the Debian folks<br>
brought the machine back up (you can see logs at<br>
<a href="http://meetbot.debian.net/" rel="noreferrer noreferrer" target="_blank">http://meetbot.debian.net/</a>) but the bot is still struggling to return. I<br>
am hoping they bring it back up themselves and restore the service. If<br>
that doesn't happen, I might squat a VM somewhere to restore some sort<br>
of service myself within TPO.<br>
<br>
But considering the number of things I'm juggling with right now, I'd be<br>
very happy with not adding a new service to the list on my first (well,<br>
second) week on the job. So I hope people don't mind the little extra<br>
wait while the good folks at Debian figure out what they want to do with<br>
the service in the long term.<br>
<br>
As weasel says, we don't want to reimplement all the services on the<br>
internet ourselves, do we? :) So if that problem can be fixed itself,<br>
I'll be more than happy than watch it heal.<br>
<br>
If not, we'll figure something out.<br>
<br>
Note that I've made sure the ArchiveBot (from ArchiveTeam) takes a look<br>
at the site so we have a copy as well in the Internet Archive.<br>
<br>
See you around!<br>
<br>
A.<br>
<br>
PS: the best place to report problems like this is still Trac. File a<br>
ticket in the "Internal Services/Tor Sysadmin Team" and I'll definitely<br>
look at it.<br>
<br>
-- <br>
Cyberspace. A consensual hallucination experienced daily by billions<br>
of legitimate operators, in every nation, by children being taught<br>
mathematical concepts...<br>
- William Gibson<br>
_______________________________________________<br>
tor-project mailing list<br>
<a href="mailto:tor-project@lists.torproject.org" target="_blank" rel="noreferrer">tor-project@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project" rel="noreferrer noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project</a><br>
</blockquote></div>