Echo much of what Gavin said. Chat is a tough problem to solve, you don’t reach critical mass if there is a cost, and there are just so many.
Keybase.io and a private Jenkins team might be a good option? It’s e2e encrypted, X-platform clients, allows for public entry rooms in what is otherwise a private “team” https://keybase.io/willwh is my user if you want to follow or chat. The other nice thing is keybase is well integrated to github too :) Thanks, Will On Thu, Dec 26, 2019 at 17:41 'Gavin Mogan' via Jenkins Developers < [email protected]> wrote: > I would be very much against yet another slack i'd have to join. > Especially cause its a closed system, requiring invites to join. Its > certainly why i havn't bothered looking into the jenkins-ux sig. > > Gitter is nice because everything is public and googleable, you only need > a github account, which is the minimum you'd need to contribute to any of > the jenkins systems anyways. Though gitter is pretty abandoned, and I would > prefer IRC, especially with a public logging bot. > > Gavin > > > > On Thu, Dec 26, 2019 at 5:27 PM Marky Jackson <[email protected]> > wrote: > >> The holidays are upon us and it’s time to relax and look back on the year >> and at the roadmap for the future. >> With [gitter being down]( >> https://twitter.com/gitchat/status/1210326466870882306?s=21) I think the >> conversation should be had regarding moving off the archaic (gitter/irc) >> communications used for the community and into a more robust form of >> unified community bonding. >> I would love to see the recently nominated board move to standardize, not >> only our crumbling infrastructure but also the means by which we >> communicate. >> With the CDF integration in the works I would also love to hear more >> about how that looks. More so how this community adapts to that new world >> (and their use of slack as a communication medium). >> We had a lot of emails about the integration and board nominations (along >> with officers), I personally am eager to hear more about the plans and the >> way to make rubber meet the road from all newly elected officials and >> returning ones. >> Happy New Years all and thank you to all the contributors for all the >> hard work you put in to this project, I for one am immensely thankful. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/139A5221-5B88-4B8E-A96A-39D399587D0F%40gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/139A5221-5B88-4B8E-A96A-39D399587D0F%40gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutWqTvR%3DAYwGcHUW10fGNj-OjV4NX06Kcj9%2BZP4PY%2BMFA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutWqTvR%3DAYwGcHUW10fGNj-OjV4NX06Kcj9%2BZP4PY%2BMFA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- William Hetherington w - opschops.ca t - @wmwh -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALJU9pcNf0LsP7k1MSyOK6_7_wzis%3D4UCviKhRQ0jjK%2BXtQCVw%40mail.gmail.com.
