[almighty] Communication Channels

[Andrew Lee Rubinger]

On Thu, Sep 29, 2016 at 8:19 AM, Karanbir Singh <kbsingh at redhat.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
>
> On 28/09/16 19:04, Andrew Lee Rubinger wrote:
> > As we continue to move technical discussions to the public space, I
> > was hoping we could outline a plan for various mediums.
> >
> > Realtime Chat:  I know we've looked at Mattermost and RocketChat;
> > is there a timeline in place for when we might expect one of these
> > to be available for use?  In the meantime I'll advocate using
> > Freenode IRC's #almighty channel.
>
> I am guessing that IRC is optional at this point in time, if not - the
> other venues need to be shut down and content actually moved over
> exclusively - otherwise we've just split chatter.
>

Totally.  For instance yesterday we had an open development workblock
hosted on #alrmighty/Freenode.  Which is why I'm looking forward to
something that works for everyone and is open (with IRC hooks as
lowest-common-denominator for people coming from other RHT groups or the
community).


> w.r.t the chat system, I am aiming to have a solution in place by the
> end of October after having run through atleast a week or so of
> evaluation by the relevant teams.
>

That'd be wonderful; looking forward to it!


> > Forums/Threaded Discussions: Max has suggested Hyperkitty; Baiju
> > has noted https://www.discourse.org/.  Is anyone owning this area
> > to gather our requirements, survey the field, make recommendations,
> > and stand up an instance?  Mail alone has proven to be difficult,
> > I've found, once discussions take tangents.
>
> What sort of conversations are we expecting to have there on the lists
> or emails etc that cant otherwise be consolidated in github's own
> issues/PRs, complemented by the existing public mailing list and a
> chat room ?
>

Threaded ones.  Linear representations of these talks can direct a
discussion into tangents pretty easily.


> if its a case of disjointed user driven content, then can we just
> adopt a relevant hash/tag or something similar in stackoverflow ? ie.
> keep the content where the people who are likely to be contributing
> already have a footprint.
>

Not opposed, but I don't think that solves the "longform development
discussion" problem. :)

For now will use GitHub issues discussions for design/development talk and
see how well it holds up.

S,
ALR


>
> regards,
>
> - --
> Karanbir Singh, Project Lead, The CentOS Project, London, UK
> Red Hat Ext. 8274455 | DID: 0044 207 009 4455
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQEcBAEBAgAGBQJX7QbKAAoJEI3Oi2Mx7xbt1cUIANGS1HBoaGw+H7eniwoj3Jvn
> 7xZyzZevSdb+voUcwsNwNAFYSbnZ27AnwO7ZMHDU4Aq3BQQmj28DVTfeksHXWIuo
> ff1XWaxN48MlJ0Yyedf33YYiWnu4D6POLaD43ERvdh3nFGaCDw8Ntlwt+3FX3i9D
> WV1rYS10PGAalK6bbyT6SgVR1BF/QgulifWsL6+gczTEF8wfzJJGvRWWegW6aupz
> GEsAUadkl7cOKFnVvJ2laoaHI60azoVi8ceBqh/AI8fn6dZUIpEc77Ei8iYHQjrJ
> JgSErRjyJDw/KA7bnpwLcrcltgOVUYT+MxUExeZ9oOzidlSuuVMeq//y4nTo4qI=
> =ypia
> -----END PGP SIGNATURE-----
>



-- 
Red Hat Developer Programs Architecture
@ALRubinger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160930/98d3aa1d/attachment.htm>