Progress update: Telegram <=> IRC <=> Slack bridge downtime

[Justin W. Flory]

Hi all,

We are working to restore the Telegram and Slack bridges to IRC after an
unexpected outage last week. We expect service to be restored no later
than Sunday, Dec. 7th.

Some issues were not anticipated in RITlug's infrastructure and data was
lost. Previous configurations were not backed up. At the same time, some
bugs in the bridge software interfered with reliable up-time. We expect
fixes upstream soon¹.

On the infrastructure side, I am setting up basic automation for the
bridge software. This should make continued use more sustainable. The
work is now happening on GitHub². The delay in restoration of service is
because of this additional work for more sustainable work (also in the
weeks approaching final exams).

We apologize for the downtime of the bridges. Service will be restored
no later than Dec. 7th. You can follow progress in any of the links
mentioned prior.

Feel free to reach out to me or reply on the list if you have questions
or concerns.


¹ -- https://github.com/RITlug/teleirc/milestone/4
² -- https://github.com/FOSSRIT/infrastructure

-- 
Cheers,
Justin W. Flory
jflory7(a)gmail.com

[Justin W. Flory]

The Telegram <=> IRC bridges are restored and are expected to remain
stable. Please file a new infrastructure ticket¹ if you notice problems.

For more detailed information, read the Teleirc v1.2.2 changelog² and
see the upgrade commit in the infrastructure repository³ to see what
changed.

The Slack bridge is not yet restored.


¹ -- https://github.com/FOSSRIT/infrastructure/issues/new
² -- https://github.com/RITlug/teleirc/releases/tag/v1.2.2
³ --
https://github.com/FOSSRIT/infrastructure/commit/0083a0dd6d0c8aa037fbfcdb...


On 11/30/18 10:49 PM, Justin W. Flory wrote:
>  Hi all,
>  
>  We are working to restore the Telegram and Slack bridges to IRC after an
>  unexpected outage last week. We expect service to be restored no later
>  than Sunday, Dec. 7th.
>  
>  Some issues were not anticipated in RITlug's infrastructure and data was
>  lost. Previous configurations were not backed up. At the same time, some
>  bugs in the bridge software interfered with reliable up-time. We expect
>  fixes upstream soon¹.
>  
>  On the infrastructure side, I am setting up basic automation for the
>  bridge software. This should make continued use more sustainable. The
>  work is now happening on GitHub². The delay in restoration of service is
>  because of this additional work for more sustainable work (also in the
>  weeks approaching final exams).
>  
>  We apologize for the downtime of the bridges. Service will be restored
>  no later than Dec. 7th. You can follow progress in any of the links
>  mentioned prior.
>  
>  Feel free to reach out to me or reply on the list if you have questions
>  or concerns.
>  
>  
>  ¹ -- https://github.com/RITlug/teleirc/milestone/4
>  ² -- https://github.com/FOSSRIT/infrastructure
>   
-- 
Cheers,
Justin W. Flory
jflory7(a)gmail.com

[Mike Nolan]

Thanks Flory! Happy to have out telegram/irc communities once again
reunited.

 - Nolski

On Sun, Dec 2, 2018 at 7:51 PM Justin W. Flory <jflory7(a)gmail.com&gt; wrote:

>  The Telegram <=> IRC bridges are restored and are expected to
> remain
>  stable. Please file a new infrastructure ticket¹ if you notice problems.
>
>  For more detailed information, read the Teleirc v1.2.2 changelog² and
>  see the upgrade commit in the infrastructure repository³ to see what
>  changed.
>
>  The Slack bridge is not yet restored.
>
>
>  ¹ -- https://github.com/FOSSRIT/infrastructure/issues/new
>  ² -- https://github.com/RITlug/teleirc/releases/tag/v1.2.2
>  ³ --
>
>
> https://github.com/FOSSRIT/infrastructure/commit/0083a0dd6d0c8aa037fbfcdb...
>
>
>  On 11/30/18 10:49 PM, Justin W. Flory wrote:
>  > Hi all,
>  >
>  > We are working to restore the Telegram and Slack bridges to IRC after an
>  > unexpected outage last week. We expect service to be restored no later
>  > than Sunday, Dec. 7th.
>  >
>  > Some issues were not anticipated in RITlug's infrastructure and data was
>  > lost. Previous configurations were not backed up. At the same time, some
>  > bugs in the bridge software interfered with reliable up-time. We expect
>  > fixes upstream soon¹.
>  >
>  > On the infrastructure side, I am setting up basic automation for the
>  > bridge software. This should make continued use more sustainable. The
>  > work is now happening on GitHub². The delay in restoration of service is
>  > because of this additional work for more sustainable work (also in the
>  > weeks approaching final exams).
>  >
>  > We apologize for the downtime of the bridges. Service will be restored
>  > no later than Dec. 7th. You can follow progress in any of the links
>  > mentioned prior.
>  >
>  > Feel free to reach out to me or reply on the list if you have questions
>  > or concerns.
>  >
>  >
>  > ¹ -- https://github.com/RITlug/teleirc/milestone/4
>  > ² -- https://github.com/FOSSRIT/infrastructure
>  >
>
>  --
>  Cheers,
>  Justin W. Flory
>  jflory7(a)gmail.com
>
>  _______________________________________________
>  FOSS @ Rochester Institute of Technology (RIT) mailing list --
>  fossrit(a)lists.fedorahosted.org
>  To unsubscribe send an email to fossrit-leave(a)lists.fedorahosted.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedorahosted.org/archives/list/[e-mail]
>

All RIT FOSS community bridges restored

[Justin W. Flory]

The Slack bridge was restored and is now online. As of now, all bridges
between IRC, Slack, and Telegram are online. Reliable service is
expected from this point. If anyone notices an issue, please file a new
infrastructure ticket¹.

For more detailed information about this outage, see the outage ticket².

Thanks for your patience! \o/


¹ -- https://github.com/FOSSRIT/infrastructure/issues/new
² -- https://github.com/FOSSRIT/tasks/issues/76#issuecomment-443977219


On 12/2/18 12:51 PM, Justin W. Flory wrote:
>  The Telegram <=> IRC bridges are restored and are expected to
> remain
>  stable. Please file a new infrastructure ticket¹ if you notice problems.
>  
>  For more detailed information, read the Teleirc v1.2.2 changelog² and
>  see the upgrade commit in the infrastructure repository³ to see what
>  changed.
>  
>  The Slack bridge is not yet restored.
>  
>  
>  ¹ -- https://github.com/FOSSRIT/infrastructure/issues/new
>  ² -- https://github.com/RITlug/teleirc/releases/tag/v1.2.2
>  ³ --
>
> https://github.com/FOSSRIT/infrastructure/commit/0083a0dd6d0c8aa037fbfcdb...
>  
>  
>  On 11/30/18 10:49 PM, Justin W. Flory wrote:
> > Hi all,
> >
> > We are working to restore the Telegram and Slack bridges to IRC after an
> > unexpected outage last week. We expect service to be restored no later
> > than Sunday, Dec. 7th.
> >
> > Some issues were not anticipated in RITlug's infrastructure and data was
> > lost. Previous configurations were not backed up. At the same time, some
> > bugs in the bridge software interfered with reliable up-time. We expect
> > fixes upstream soon¹.
> >
> > On the infrastructure side, I am setting up basic automation for the
> > bridge software. This should make continued use more sustainable. The
> > work is now happening on GitHub². The delay in restoration of service is
> > because of this additional work for more sustainable work (also in the
> > weeks approaching final exams).
> >
> > We apologize for the downtime of the bridges. Service will be restored
> > no later than Dec. 7th. You can follow progress in any of the links
> > mentioned prior.
> >
> > Feel free to reach out to me or reply on the list if you have questions
> > or concerns.
> >
> >
> > ¹ -- https://github.com/RITlug/teleirc/milestone/4
> > ² -- https://github.com/FOSSRIT/infrastructure
> >
>   
-- 
Cheers,
Justin W. Flory
jflory7(a)gmail.com