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 messaging solution. In 
response, he said he is willing to work with KDE and LibreOffice to 
build a platform that we can be happy with.


this is an important topic and I have not forgotten about it - just
the time upfront LibOCon keeps us quite busy. ;-)

That being said, are you at LibOCon, so we could talk there in person 
maybe?


Florian


Sure.

Some weeks ago there was this nice bit of news about Konversation: 
https://blogs.kde.org/2017/09/05/konversation-2x-2018-new-user-interface-matrix-support-mobile-version


I just discussed with the Kiwi IRC dev and I decided I will replace the 
qwebirc links in our wiki and site with the /nextclient/ link tomorrow. 
Full roll out of the next gen version to the /client/ URL is pending 
some translations and /nextclient/ will never stop working in any case. 
It is possible for us to the get a custom landing page and background 
image for the webchat. We can discuss this at the conf.


Best,
Ilmari

--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted



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 to work with KDE and LibreOffice to build a 
platform that we can be happy with.


this is an important topic and I have not forgotten about it - just the 
time upfront LibOCon keeps us quite busy. ;-)


That being said, are you at LibOCon, so we could talk there in person maybe?

Florian

--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted


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 we can be happy with.


I posted my proposal to KDE community list: 
https://mail.kde.org/pipermail/kde-community/2017q3/003857.html


For convenience, I will include below the text that the Kiwi dev wrote 
after reading KDE's requirement list:


Kiwi Next is the next generation of the Kiwi IRC client, specifically 
aiming to bring modern interfaces and ease of use from platforms such as 
Slack to IRC.


Many communities have established environments built up around IRC so 
any features or additions that Kiwi IRC brings will be 100% IRC 
compliant throughout and put to the IRCv3 working group so that other 
clients and servers may also make use of the functions.


The UI for Kiwi Next is getting tested on all major browsers including 
mobile, with translations being made available for 28 languages to make 
sure that anybody trying to be part of a community can do so.


Keeping people connected to IRC so that they may receive notifications 
on their desktop and/or mobile is a huge feature currently missing from 
IRC. This is currently being developed directly into Kiwi IRC so it is 
available out of the box with minimal fuss. Once connected and logged 
into your existing network services, a user can then simply resume their 
session with complete message history and searching. This is a feature 
that will be introduced on kiwiirc.com very soon but also entirely open 
source to be used anywhere. Works very similar to ZNC in that Kiwi acts 
as a normal IRC client which means any IRC client can make use of the 
same server.


A lot of the points mentioned are very much inline with the aims for 
Kiwi Next, most likely due to the same mindset: Slack + IRC merged 
together with some IRCv3 features thrown in.


Some quick overview points:
* 100% standards compliant
* Part of the IRCv3 working group to improve IRC itself
* Open source with an available hosted solution
* Use existing infrastructure and tools
* Multilingual and accessible
* Web based while still allowing desktop clients to be used
* Has already been tested with thousands of users in a single channel 
flood fest
* Built in media preview (images, videos, PDFs, anything that can be 
embedded)


Soon to be released:
* Team based channels that supports @everybody highlighting
* Switchable message views such as traditional IRC view and a more 
relaxed avatar + relaxed view
* Message reactions (Using IRCv3 standards so they work with other 
clients too)


In development at the moment:
* Built in BNC with desktop/mobile notifications
* Use Kiwi IRC and a desktop client on the same account at the same time 
(similar to ZNC)

* Message history + searching + exporting
* File sharing by uploading files through the UI, with optional file 
history


Not in development but can easily be added into Kiwi Next if required:
* Replying to a message with a reference/quote
* Editing messages
* Annotate images linked/shared through the client
* Stickers between Kiwi clients or between all IRC clients

--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted



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, beyond the fact that 
it's been used by many people. There are several truly free and open 
solutions out there, but sadly, very few users use them - and that's in 
line with what I wrote earlier on about "getting people where they are".


I tried some mobile IRC clients a while ago and was not really 
convinced: no push notification, high battery usage - IRC simply is a 
different tool than a messenger...


I'm not at all against hosting our own web IRC frontend, preferably 
localized - I just think it won't get us the mobile crowd...


Florian

--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted


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"? :)
> 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 mentioning here that replies are a draft: 
> http://ircv3.net/specs/client-tags/reply.html
> Editing and deleting of messages is being worked on: 
> https://github.com/ircv3/ircv3-specifications/pull/304
> 
> Ilmari
> 
> On 11.08.2017 20:45, Heiko Tietze wrote:
>> 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, so the avatar is a nice-to-have
>> and stickers a contradiction, and suggested to run a Kano survey like
>> I did for KGet in [2]. But the list is interesting anyway.
>>
>> [1] https://mail.kde.org/pipermail/kde-community/2017q3/003693.html
>> [2] https://user-prompt.com/using-the-kano-method-to-prioritize-requirements/
>>
>> On 11.08.2017 19:23, Ilmari Lauhakangas wrote:
>>> 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 English. No dealbreaker, but a nice to have of
> course.

 Yes, it supports localization, as evidenced by code changes such as:
 https://github.com/kiwiirc/kiwiirc/pull/56
 I don't think anyone has translated it yet.
 qwebirc never supported localization.

 Ilmari
>>>
>>> I was wrong, the translations are here: http://translations.kiwiirc.com/
>>>
>>> Ilmari
>>>
>>
>> -- 
>> Dr. Heiko Tietze
>> UX designer
>> Tel. +49 (0)179/1268509
> 

-- 
Dr. Heiko Tietze
UX designer
Tel. +49 (0)179/1268509


-- 
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted


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 mentioning here that replies are a draft: 
http://ircv3.net/specs/client-tags/reply.html
Editing and deleting of messages is being worked on: 
https://github.com/ircv3/ircv3-specifications/pull/304


Ilmari

On 11.08.2017 20:45, Heiko Tietze wrote:

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, so the avatar is a nice-to-have
and stickers a contradiction, and suggested to run a Kano survey like
I did for KGet in [2]. But the list is interesting anyway.

[1] https://mail.kde.org/pipermail/kde-community/2017q3/003693.html
[2] 
https://user-prompt.com/using-the-kano-method-to-prioritize-requirements/


On 11.08.2017 19:23, Ilmari Lauhakangas wrote:

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 English. No dealbreaker, but a nice to have of
course.


Yes, it supports localization, as evidenced by code changes such as:
https://github.com/kiwiirc/kiwiirc/pull/56
I don't think anyone has translated it yet.
qwebirc never supported localization.

Ilmari


I was wrong, the translations are here: 
http://translations.kiwiirc.com/


Ilmari



--
Dr. Heiko Tietze
UX designer
Tel. +49 (0)179/1268509


--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted



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, so the 
avatar is a nice-to-have and stickers a contradiction, and suggested to run a 
Kano survey like I did for KGet in [2]. But the list is interesting anyway.

[1] https://mail.kde.org/pipermail/kde-community/2017q3/003693.html
[2] https://user-prompt.com/using-the-kano-method-to-prioritize-requirements/

On 11.08.2017 19:23, Ilmari Lauhakangas wrote:
> 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 English. No dealbreaker, but a nice to have of
>>> course.
>>
>> Yes, it supports localization, as evidenced by code changes such as:
>> https://github.com/kiwiirc/kiwiirc/pull/56
>> I don't think anyone has translated it yet.
>> qwebirc never supported localization.
>>
>> Ilmari
> 
> I was wrong, the translations are here: http://translations.kiwiirc.com/
> 
> Ilmari
> 

-- 
Dr. Heiko Tietze
UX designer
Tel. +49 (0)179/1268509


-- 
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted


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 English. No dealbreaker, but a nice to have of
course.


Yes, it supports localization, as evidenced by code changes such as:
https://github.com/kiwiirc/kiwiirc/pull/56
I don't think anyone has translated it yet.
qwebirc never supported localization.

Ilmari


I was wrong, the translations are here: http://translations.kiwiirc.com/

Ilmari

--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted



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 so (add and remove channels 
at will):

https://kiwiirc.com/nextclient/#irc://irc.freenode.net/libreoffice-qa,libreoffice-design,libreoffice-dev,libreoffice-doc,tdf-infra


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 English. No dealbreaker, but a nice to have of
course.


Yes, it supports localization, as evidenced by code changes such as: 
https://github.com/kiwiirc/kiwiirc/pull/56

I don't think anyone has translated it yet.
qwebirc never supported localization.

Ilmari

--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted



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):
https://kiwiirc.com/nextclient/#irc://irc.freenode.net/libreoffice-qa,libreoffice-design,libreoffice-dev,libreoffice-doc,tdf-infra 


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 English. No dealbreaker, but a nice to have of course.


Incidentally, KDE is having a similar discussion: 
https://mail.kde.org/pipermail/kde-community/2017q3/003664.html 
(warning: massive thread, you might spend your whole day..)


Didn't manage to read this yet though :)

Florian

--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted


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

https://webchat.freenode.net/?channels=#tdf-infra

But if we host ourselves, we could add TDF/LO themeing, extra help, and
make the interface more welcoming for newbies to IRC.

Just a thought...

Mike


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):

https://kiwiirc.com/nextclient/#irc://irc.freenode.net/libreoffice-qa,libreoffice-design,libreoffice-dev,libreoffice-doc,tdf-infra

Hosting our own, we could set up persistent history. A history solution 
for Kiwi IRC is currently in development. Kiwi IRC also has a theme 
builder functionality for CSS-only changes: 
https://kiwiirc.com/nextclient-themebuilder


Incidentally, KDE is having a similar discussion: 
https://mail.kde.org/pipermail/kde-community/2017q3/003664.html 
(warning: massive thread, you might spend your whole day..)


Ilmari

--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted



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 ourselves, we could add TDF/LO themeing, extra help, and
make the interface more welcoming for newbies to IRC.

Just a thought...

Mike

-- 
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted


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 that topic was considered quite a lot before going that route.


My personal take on the situation is that the primary and official 
channels are those on TDF premises, i.e. primarily our mailing lists, 
wiki, pad and other resources to create and upload content. We have full 
control over these. My personal order of preference is e-mail (it's an 
asynchronous medium that everyone can use at the time and frequency they 
like), sometimes chat or phone, as the latter ones can help resolving 
topics easier than with lots of mails back and forth.


During the previous LibreOffice Conference, the organizers have setup a 
Telegram group for the attendees. It was considered mostly an experiment 
and planned to be shut down after the conference - the strong 
participation rate and acceptance of it made us rethink and keep it 
running. It was not a decision upfront, but turned out to be a good idea 
(IMHO) over time. So, it was initialized in first place by volunteer 
conference organizers, and has not been pushed by TDF's team, although 
of course they are quite visible.


I agree, though, that we can get better on communication that, indeed. 
There was a blog post at 
https://blog.documentfoundation.org/blog/2016/10/25/presenting-libreoffice-telegram-channel/ 
that also mentions bridging to IRC, but we could have added more details.


The main reason for using all sorts of networks is that we "want to get 
the people where they are". Especially for the younger generations, and 
also for some native language groups, messengers and social networks 
have turned out to be the most effective way. I recall at least one 
community ever since using Google Plus, and another one ever since using 
Facebook, considering mailing lists way too complicated and "old style". 
Being a free software enthusiast, and essentially living in my e-mail 
client, this doesn't make me totally happy; however, IMHO we would be 
wasting lots of opportunities if we expect people to show up on mailing 
lists and IRC, independent what their background is.


This is also the reason why the (few) truly free and open social tools 
do not help in this regard - they are only used by those already 
attracted by our project. If we want to reach out to new possible 
contributors, we need to show up where they are, if we like it or not. 
And looking at my contacts, very few of these use one of the truly free 
tools either; one contact here, another contact there, but nothing 
consistent sadly.


For me, the main rationale is to have as many content creation, 
discussions and votes on official channels as possible. I'd like to 
avoid a situation where decisions take place on some random network only 
a few subscribe to - the primary working place is the mailing list 
still, decision need to be properly communicated and shared and run on 
the official channels.


I'm all open for making access easier, have a better web IRC, and also 
re-investigate video conferencing systems (although I have to admit that 
testing with 10-20 people is quite time-consuming, so I'd prefer a 
real-life experience with such an amount, geographically distributed, on 
various bandwiths). Bridging is another option, and deciding which 
content to post where makes sense as well.


If you have proposals, please share them. We surely can get better, and 
I'm open for any proposals.


Hope that helps!
Florian

--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted


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]
http://nabble.documentfoundation.org/Libreoffice-qa-QA-Meeting-Minutes-2017-04-25-tc4213251.html


El 01/08/17 a les 10:46, Sophie ha escrit:
> Hi Jonathon, Ilmari, all,
>
> Le 31/07/2017 à 22:58, Toki a écrit :
>> 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 license is available here.»
>> The "here" links to
>> https://github.com/telegramdesktop/tdesktop/blob/dev/LICENSE, which
>> contains the text of the GNU GPL 3.0
>>
>> As such, I don't understand how it can be accused of being "closed source".
> Yes, you're right. However, the most important thing Ilmari is pointing
> is about the decision process that shouldn't be on IRC or Telegram or
> any other media but on mailing lists.
> I like that the community is able to use the tool it prefers to
> communicate, that opens the possibilities and makes our projects more
> reachable. ESC is not only using hangout, but also phones on Talkyoo,
> one language is leading its translation on Facebook, etc... whatever
> they are at ease with and brings people together.
> What we should be very careful with is to report on the lists, make the
> decision process available on the lists and keep an archive of the
> activities on the lists. That way each new comer has access to the
> information at the same level others have and there is a memory of what
> has been done.
>
> Cheers
> Sophie
>

-- 
Xisco Faulí
Libreoffice QA Team
IRC: x1sc0



-- 
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted


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 GPLv3 with OpenSSL
exception, the license is available here.»
The "here" links to
https://github.com/telegramdesktop/tdesktop/blob/dev/LICENSE, which
contains the text of the GNU GPL 3.0

As such, I don't understand how it can be accused of being "closed 
source".


https://en.wikipedia.org/wiki/Telegram_(messaging_service)

"Its client-side code is open-source software but contains binary blobs, 
and the source code for recent versions is not always immediately 
published, whereas its server-side code is closed-source and 
proprietary."


--
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted


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 license is available here.»
The "here" links to
https://github.com/telegramdesktop/tdesktop/blob/dev/LICENSE, which
contains the text of the GNU GPL 3.0

As such, I don't understand how it can be accused of being "closed source".

jonathon

-- 
To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted