[kde-community] possible foss alternative to telegram/slack

2016-05-17 Thread Marco Martin
Hi all, Right now many groups are using Telegram as their primary communication medium due to some limitations in IRC (mainly due to the ease of pasting images inline the channel and the lack of fancy mobile clients for IRC), there may be other valid reasons i'm not aware of today i randomly stu

Re: [kde-community] possible foss alternative to telegram/slack

2016-05-17 Thread Teo Mrnjavac
On martedì 17 maggio 2016 10:55:52 CEST Marco Martin wrote: > Hi all, > Right now many groups are using Telegram as their primary communication > medium due to some limitations in IRC (mainly due to the ease of pasting > images inline the channel and the lack of fancy mobile clients for IRC), > the

Re: [kde-community] possible foss alternative to telegram/slack

2016-05-17 Thread Luca Beltrame
Il giorno Tue, 17 May 2016 11:24:59 +0200 Teo Mrnjavac ha scritto: > A huge +1. It has Jenkins integration, and from what I gather > Bugzilla integration might be doable as well. I'd love it if we had a I tested Mattermost myself a bit, it looks slick indeed, but I couldn't test more than that a

Re: [kde-community] possible foss alternative to telegram/slack

2016-05-17 Thread Ken Vermette
I'm interested too, if for no other reason than self-hosting an instance means we aren't tied to the fate of a 3rd-party. Several people who were not on board with issues on the Telegram openness would probably be willing to use this as well. One thing I'd like to mention is that we should firmly

Re: [kde-community] possible foss alternative to telegram/slack

2016-05-17 Thread Nicolás Alvarez
2016-05-17 5:55 GMT-03:00 Marco Martin : > Hi all, > Right now many groups are using Telegram as their primary communication medium > due to some limitations in IRC (mainly due to the ease of pasting images > inline the channel and the lack of fancy mobile clients for IRC), there may be > other val

Re: [kde-community] possible foss alternative to telegram/slack

2016-05-17 Thread Thomas Pfeiffer
On Dienstag, 17. Mai 2016 12:33:25 CEST Nicolás Alvarez wrote: > 2016-05-17 5:55 GMT-03:00 Marco Martin : > > Hi all, > > Right now many groups are using Telegram as their primary communication > > medium due to some limitations in IRC (mainly due to the ease of pasting > > images inline the channe

Re: [kde-community] possible foss alternative to telegram/slack

2016-05-17 Thread Thomas Pfeiffer
On Dienstag, 17. Mai 2016 11:05:56 CEST Ken Vermette wrote: > I'm interested too, if for no other reason than self-hosting an instance > means we aren't tied to the fate of a 3rd-party. Several people who were > not on board with issues on the Telegram openness would probably be willing > to use th

Re: [kde-community] KDE Mission - let's do this!

2016-05-17 Thread Alexander Neundorf
On Monday 16 May 2016 23:37:17 Thomas Pfeiffer wrote: > On Montag, 16. Mai 2016 22:59:59 CEST you wrote: > > Hi Thomas, > > > > On Tuesday 10 May 2016 22:48:01 Alexander Neundorf wrote: > > > On Tuesday, May 10, 2016 17:18:39 Thomas Pfeiffer wrote: > > ... > > > > > > Both positions are perfectly

Re: [kde-community] possible foss alternative to telegram/slack

2016-05-17 Thread Luca Beltrame
Il giorno Tue, 17 May 2016 20:18:37 +0200 Thomas Pfeiffer ha scritto: > Good point! I think we should use it internally extensively before > switching any public communication over to it. More food for thought: another alternative may be Matrix[1] a FOSS, federated service a la Jabber. Unfortuna