Re: [libreoffice-projects] On the communication channels we use

2017-09-25 Thread Ilmari Lauhakangas
On 25.09.2017 12:57, Florian Effenberger wrote: Hello, Ilmari Lauhakangas wrote on 2017-08-16 at 12:12: I have continued working with Kiwi IRC's lead developer. I brought up the topic of KDE and showed him their Etherpad, which listed all sorts of requirements and nice-to-haves for a

Re: [libreoffice-projects] On the communication channels we use

2017-09-25 Thread Florian Effenberger
Hello, Ilmari Lauhakangas wrote on 2017-08-16 at 12:12: I have continued working with Kiwi IRC's lead developer. I brought up the topic of KDE and showed him their Etherpad, which listed all sorts of requirements and nice-to-haves for a messaging solution. In response, he said he is willing

Re: [libreoffice-projects] On the communication channels we use

2017-08-16 Thread Ilmari Lauhakangas
I have continued working with Kiwi IRC's lead developer. I brought up the topic of KDE and showed him their Etherpad, which listed all sorts of requirements and nice-to-haves for a messaging solution. In response, he said he is willing to work with KDE and LibreOffice to build a platform that

Re: [libreoffice-projects] On the communication channels we use

2017-08-14 Thread Florian Effenberger
Hi, Heiko Tietze wrote on 2017-08-11 at 19:45: Could the missing desktop app become a showstopper? that reminds me of one question I didn't answer yet: Why Telegram. ;-) Indeed, the possibility to use it on mobile, in browser and as dedicated desktop application was one of the main reasons,

Re: [libreoffice-projects] On the communication channels we use

2017-08-13 Thread Heiko Tietze
KDE fellows found a Qt5-app for Matrix https://github.com/mujx/nheko/ (we need a cross-platform tool for average users without the hassle to compile; or rather a simple mobile app) On 11.08.2017 20:10, Ilmari Lauhakangas wrote: > I guess you mean "missing desktop app with an attractive GUI"? :)

Re: [libreoffice-projects] On the communication channels we use

2017-08-11 Thread Ilmari Lauhakangas
I guess you mean "missing desktop app with an attractive GUI"? :) Regarding features in general, chat history batch is a draft in the IRC v3 spec: http://ircv3.net/specs/extensions/batch/chathistory-3.3.html A metadata spec is being written and it would include avatars. It is also worth

Re: [libreoffice-projects] On the communication channels we use

2017-08-11 Thread Heiko Tietze
Could the missing desktop app become a showstopper? Telegram is available as standalone app and Telepathy can also handle this protocol (not sure about Pidgin). Thomas collected a couple of requirements in the KDE chat what a messenger should be able to do. I would rate some points differently,

Re: [libreoffice-projects] On the communication channels we use

2017-08-11 Thread Ilmari Lauhakangas
On 11.08.2017 17:05, Ilmari Lauhakangas wrote: On 11.08.2017 16:53, Florian Effenberger wrote: doesn't look too bad to me indeed. ;-) Do you know if it is available localized? I think if we want to extend IRC to casual users, some localization would be helpful, and for me Kiwi IRC loaded in

Re: [libreoffice-projects] On the communication channels we use

2017-08-11 Thread Ilmari Lauhakangas
On 11.08.2017 16:53, Florian Effenberger wrote: Hi, Ilmari Lauhakangas wrote on 2017-08-09 at 14:42: Kiwi IRC rewrite will go stable in a couple of weeks. I intend to change our links to point to it. It is much nicer than the dated qwebirc interface. For now, you can try the new version like

Re: [libreoffice-projects] On the communication channels we use

2017-08-11 Thread Florian Effenberger
Hi, Ilmari Lauhakangas wrote on 2017-08-09 at 14:42: Kiwi IRC rewrite will go stable in a couple of weeks. I intend to change our links to point to it. It is much nicer than the dated qwebirc interface. For now, you can try the new version like so (add and remove channels at will):

Re: [libreoffice-projects] On the communication channels we use

2017-08-09 Thread Ilmari Lauhakangas
On 09.08.2017 14:17, Mike Saunders wrote: Hi, On 08/08/2017 12:44, Florian Effenberger wrote: I'm all open for making access easier, have a better web IRC Do you think it's worth hosting our own web IRC front-ends? Currently we point people to Freenode's webchat, eg

Re: [libreoffice-projects] On the communication channels we use

2017-08-09 Thread Mike Saunders
Hi, On 08/08/2017 12:44, Florian Effenberger wrote: > > I'm all open for making access easier, have a better web IRC Do you think it's worth hosting our own web IRC front-ends? Currently we point people to Freenode's webchat, eg https://webchat.freenode.net/?channels=#tdf-infra But if we host

Re: [libreoffice-projects] On the communication channels we use

2017-08-08 Thread Florian Effenberger
Hello, ilmari.lauhakan...@libreoffice.org wrote on 2017-07-31 at 14:25: I have concerns regarding the communication channels we use for working on LibreOffice. First, it seems we are sliding into a situation where thanks for sharing your concerns. I indeed do take these very seriously, and

Re: [libreoffice-projects] On the communication channels we use

2017-08-01 Thread Xisco Fauli
Hello, I just want to make clear that the decision of creating the Telegram group for QA was discussed in the QA meeting on 2017-04-25 [1] Besides, both channels are bridged now, which IMHO, allow everyone to choose what fits her/him better. Regards [1]

Re: [libreoffice-projects] On the communication channels we use

2017-08-01 Thread Ilmari Lauhakangas
On 31.07.2017 23:58, Toki wrote: On 07/31/2017 12:25 PM, ilmari.lauhakangas wrote: the closed-source chat platform Telegram becomes an official channel for team coordination. Source code is at https://github.com/telegramdesktop/tdesktop Where it states «The source code is published under

Re: [libreoffice-projects] On the communication channels we use

2017-07-31 Thread Toki
On 07/31/2017 12:25 PM, ilmari.lauhakangas wrote: > the closed-source chat platform Telegram becomes an official channel for team > coordination. Source code is at https://github.com/telegramdesktop/tdesktop Where it states «The source code is published under GPLv3 with OpenSSL exception, the