This is an easy +1 to me since it doesn't disrupt existing workflows for
IRC users and provides others a better chance to participate if they are
either unfamiliar with IRC or do not have stable Internet connection to
use IRC well.
This would also be a nice thing to have set up when CommOps revisits
this ticket after Fedora Appreciation Week this year:
https://pagure.io/fedora-commops/issue/159
On 9/20/18 7:54 AM, Eduard Lucena wrote:
> Hi,
>
> I'm totally +1 to this. We set this up in Marketing and CommOps and has
> been really successful.
>
> Br,
> Eduard Lucena
>
> El jue., 20 de sep. de 2018 08:29, Aidan Kahrs <abkahrs@xxxxxxxxx
> <mailto:abkahrs@xxxxxxxxx>> escribió:
>
> Bex,
> If you do decide to set this up, I know that RITlug maintains a
> bridge bot that is widely used and may actually be in use by parts
> of Fedora already. Keep in mind that Telegram is not fully FOSS as
> IRC or Riot/Matrix are so if that is a concern Telegram may not be
> the right platform.
>
> As far as the bridge bot, it can be found on GitHub at
> https://www.github.com/RITlug/teleirc
>
> Hope this is useful.
>
> Aidan
> abkahrs@xxxxxxxxxxxxxxxxx <mailto:abkahrs@xxxxxxxxxxxxxxxxx>
>
>
> On Thu, Sep 20, 2018, 3:36 AM Brian (bex) Exelbierd
> <bexelbie@xxxxxxxxxx <mailto:bexelbie@xxxxxxxxxx>> wrote:
>
> Hi,
>
> I am regularly getting pulled into several Fedora Docs related
> conversations in Telegram. These typically are around Antora
> and tooling, but are occasionally around large areas like L10N
> and new doc components.
>
> NO decisions are being made in Telegram, these are more working
> conversations.
>
> I'd like us to consider setting up a Telegram <-> IRC bridge,
> like some other channels have done so I can easily redirect
> these conversations into the public eye and encourage greater
> participation.
>
> What do you all think?
>
> regards,
>
> bex
> --
> Brian (bex) Exelbierd | bexelbie@xxxxxxxxxx
> <mailto:bexelbie@xxxxxxxxxx> | bex@xxxxxxxxx <mailto:bex@xxxxxxxxx>
> Fedora Community Action & Impact Coordinator
> @bexelbie | http://www.winglemeyer.org
> _______________________________________________
> docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:docs@xxxxxxxxxxxxxxxxxxxxxxx>
> To unsubscribe send an email to
> docs-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:docs-leave@xxxxxxxxxxxxxxxxxxxxxxx>
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/docs@xxxxxxxxxxxxxxxxxxxxxxx
>
> _______________________________________________
> docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:docs@xxxxxxxxxxxxxxxxxxxxxxx>
> To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:docs-leave@xxxxxxxxxxxxxxxxxxxxxxx>
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/docs@xxxxxxxxxxxxxxxxxxxxxxx
>
>
> _______________________________________________
> docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/docs@xxxxxxxxxxxxxxxxxxxxxxx
>
--
Cheers,
Justin W. Flory
jflory7@xxxxxxxxx
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@xxxxxxxxxxxxxxxxxxxxxxx
