[Sugar-devel] Proposing a communication switch
quozl at laptop.org
Sun Feb 18 19:08:17 EST 2018
On Sun, Feb 18, 2018 at 09:21:11PM +0000, D. Joe wrote:
> On Mon, Feb 19, 2018 at 07:37:03AM +1100, James Cameron wrote:
> > Slack and Matrix are also popular.
And I forgot to mention Riot.im
> Since it is several links deep now, I'll surface this point I made in
> similar discussions elsewhere, for Sumit's benefit:
> My approach is that, if someone wants to try to make one of those bridges
> work, and is willing to put in the time and attention to do it, then I'm OK
> with it. That said "putting in the time and attention to do it" requires a
> level of commitment to making it work and keeping it working we'd probably
> rather see devoted to other things. But if that's what one wishes to do ...
Agreed. Also, putting time and attention to do it means to bring
along the rest of the community, and I don't yet see that happening.
Facts don't convince.
> This comes up often enough I have an essay draft sitting around about it
> all. For now, I'll just add this one new link I have to give some academic
> context to this discussion:
Agreed. Very interesting paper. For Sugar Labs, we have the
segregation of multiple GitHub repositories which has led to a call
for a developer "dashboard" aggregator, and also the "walled-garden"
effect of GitHub pull-requests and issues which are not archived at
sugarlabs.org. Design and development is segmented rather than
concentrated. Another chat medium is effectively a proposal to
Thread original poster might find an IRC client or persistent presence
tool more suited to their expectations; then document that tool for
others of like-mind.
More information about the Sugar-devel