Re: [SailfishDevel] QtLocation | Qt 5.6

2017-07-12 Thread rinigus 
Hi Chris,

thank you very much for an update. Looking forward for veskuh's reply and,
hopefully, we can move forward with this API as well.

Cheers,

Rinigus

On Thu, Jul 13, 2017 at 3:40 AM, Chris Adams  wrote:

> Hi,
>
> I think veskuh will be the best to answer these questions.
>
> Currently, I don't think any work has gone toward upgrading QtLocation to
> version 5.6 yet, as we're busy with other projects.  Originally the
> decision to not take QtLocation 5.6 into use along with the rest of the Qt
> 5.6 libs was, I believe, because of the different licensing of QtLocation.
> I think veskuh would be the best person to describe our intent going
> forward, and possible roadmap for updating.
>
> Best regards,
> Chris.
>
>
> --
> *From:* Devel [devel-boun...@lists.sailfishos.org] on behalf of rinigus [
> rinigus@gmail.com]
> *Sent:* Friday, July 07, 2017 6:04 PM
> *To:* Sailfish OS Developers
> *Subject:* Re: [SailfishDevel] QtLocation | Qt 5.6
>
> Hi,
>
> it has been rather quiet regarding QtLocation 5.6 during the "first
> quarter of 2017" (see earlier emails in this thread). I would like to
> continue my work on navigation/mapping solutions for SFOS and the
> uncertainty regarding QtLocation is just slowing everything down and lead
> to major inefficiency in the development of this important aspect of SFOS.
>
> I would like to know what is the state of QtLocation and its future in
> SFOS. From the activity in https://git.merproject.org/
> mer-core/qtlocation/activity
> 
> I conclude that the developers working on it are @chriadam, @pvuorela,
> @xfade, Slava Monich, and @msmirnov. Maybe some of you can take time and
> reply. In particular:
>
> * Has any work started on upgrading QtLocation to 5.6?
>
> * Has Jolla decided whether they want to work on QtLocation/5.6?
>
> * If its decided that its impossible to include QtLocation due to
> licensing issues, can the community help to provide the QtLocation via our
> packages?
>
> * If you just haven't had time for working on QtLocation 5.6, how can we
> help and where should we start?
>
> It looks to me that QtLocation is the component that is pushed for map
> applications development. I presume that it would be wise to use it as well
> and not waste time to re-invent something similar. Or is there anything
> considerably better and we should work on that instead?
>
> Since it is developers channel, its an appropriate place to ask, I
> believe.
>
> Best wishes,
>
> Rinigus
>
> On Tue, Jan 10, 2017 at 10:49 PM, Tone Kastlunger <
> users.giulie...@gmail.com
> 
> > wrote:
>
>> I'd support this, not enough has been coming through at the meeting IMO
>> to have a clear yes/no answer.
>>
>> Best,
>> tortoisedoc
>>
>> On Mon, Jan 9, 2017 at 11:32 PM, Adam Pigg > 
>> > wrote:
>>
>>> I guess we need to wait for the internal review that was mentioned in
>>> the meeting, however it would be interesting to understand the issues jolla
>>> have with particular licenses for software included in sfos.
>>>
>>> On Mon, 9 Jan 2017 at 21:29 Osmo Salomaa >> >
>>> wrote:
>>>
 On 09.01.2017 13:01, rinigus wrote:
 > from reading the meeting transcript it seems that we still don't have
 > straight answer regarding QtLocation 5.6 ("checking at the moment").

 They were not wordy, but my interpretation is that nothing has changed
 regarding QtLocation being allowed in store apps once it's upgraded to a
 stable release, i.e. >= 5.6. "Aiming to have solution for it in the first
 quarter of 2017" doesn't sound too bad, I was worried we were at a dead 
 end.

 > However, I don't see the changes in the source code indicating
 exclusive
 > role of LGPLv3 among LGPL licenses. The LGPLv2.1 license is still
 there for
 > QtLocation module (see https://github.com/qt/qtlocation
 
 ).

 Indeed. There's a license change commit in the source 2016-01-20, but
 that's saying it would be from 5.7 onwards. And that commit is not in the
 5.6 branch.

 https://github.com/qt/qtlocation/commit/71dabb5dc330a47d91ee
 917ca60c871a88e8a42a
 

 Reading various other unclear sources, I

Re: [SailfishDevel] QtLocation | Qt 5.6

2017-07-12 Thread Chris Adams 
Hi,

I think veskuh will be the best to answer these questions.

Currently, I don't think any work has gone toward upgrading QtLocation to 
version 5.6 yet, as we're busy with other projects.  Originally the decision to 
not take QtLocation 5.6 into use along with the rest of the Qt 5.6 libs was, I 
believe, because of the different licensing of QtLocation.  I think veskuh 
would be the best person to describe our intent going forward, and possible 
roadmap for updating.

Best regards,
Chris.



From: Devel [devel-boun...@lists.sailfishos.org] on behalf of rinigus 
[rinigus@gmail.com]
Sent: Friday, July 07, 2017 6:04 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] QtLocation | Qt 5.6

Hi,

it has been rather quiet regarding QtLocation 5.6 during the "first quarter of 
2017" (see earlier emails in this thread). I would like to continue my work on 
navigation/mapping solutions for SFOS and the uncertainty regarding QtLocation 
is just slowing everything down and lead to major inefficiency in the 
development of this important aspect of SFOS.

I would like to know what is the state of QtLocation and its future in SFOS. 
From the activity in 
https://git.merproject.org/mer-core/qtlocation/activity
 I conclude that the developers working on it are @chriadam, @pvuorela, @xfade, 
Slava Monich, and @msmirnov. Maybe some of you can take time and reply. In 
particular:

* Has any work started on upgrading QtLocation to 5.6?

* Has Jolla decided whether they want to work on QtLocation/5.6?

* If its decided that its impossible to include QtLocation due to licensing 
issues, can the community help to provide the QtLocation via our packages?

* If you just haven't had time for working on QtLocation 5.6, how can we help 
and where should we start?

It looks to me that QtLocation is the component that is pushed for map 
applications development. I presume that it would be wise to use it as well and 
not waste time to re-invent something similar. Or is there anything 
considerably better and we should work on that instead?

Since it is developers channel, its an appropriate place to ask, I believe.

Best wishes,

Rinigus

On Tue, Jan 10, 2017 at 10:49 PM, Tone Kastlunger 
>
 wrote:
I'd support this, not enough has been coming through at the meeting IMO to have 
a clear yes/no answer.

Best,
tortoisedoc

On Mon, Jan 9, 2017 at 11:32 PM, Adam Pigg 
>
 wrote:
I guess we need to wait for the internal review that was mentioned in the 
meeting, however it would be interesting to understand the issues jolla have 
with particular licenses for software included in sfos.

On Mon, 9 Jan 2017 at 21:29 Osmo Salomaa 
>
 wrote:
On 09.01.2017 13:01, rinigus wrote:
> from reading the meeting transcript it seems that we still don't have
> straight answer regarding QtLocation 5.6 ("checking at the moment").

They were not wordy, but my interpretation is that nothing has changed 
regarding QtLocation being allowed in store apps once it's upgraded to a stable 
release, i.e. >= 5.6. "Aiming to have solution for it in the first quarter of 
2017" doesn't sound too bad, I was worried we were at a dead end.

> However, I don't see the changes in the source code indicating exclusive
> role of LGPLv3 among LGPL licenses. The LGPLv2.1 license is still there for
> QtLocation module (see 
> https://github.com/qt/qtlocation).

Indeed. There's a license change commit in the source 2016-01-20, but that's 
saying it would be from 5.7 onwards. And that commit is not in the 5.6 branch.

https://github.com/qt/qtlocation/commit/71dabb5dc330a47d91ee917ca60c871a88e8a42a

Reading various other unclear sources, I see 5.5, 5.6 and 5.7 all mentioned for 
the change -- maybe it was pushed back a few times? I have found no web page 
that would actually list the licenses under which Qt modules are available. Can 
anyone from Jolla comment? Do you have better information?

--
Osmo Salomaa 
>
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] [Minutes] Sailfish OS, open source, collaboration meeting on July 12th 2017

2017-07-12 Thread James Noori 

Hi all.

First of all, apologies for not sending a reminder for this meeting and 
not being present during the meeting either. I tend to be forgetful when 
I'm not home. Special thanks to Nokius for chairing the meeting and 
taking care of everything despite being at work!


Meeting minutes can be found in variety of formats below:

Minutes: 
http://merproject.org/meetings/mer-meeting/2017/mer-meeting.2017-07-12-08.18.html
Minutes (text): 
http://merproject.org/meetings/mer-meeting/2017/mer-meeting.2017-07-12-08.18.txt
Log: 
http://merproject.org/meetings/mer-meeting/2017/mer-meeting.2017-07-12-08.18.log.html


Next meeting will be held on 26th of July 2017 at 08:00 UTC.

Please add your topics to the planning page on TJC:
https://together.jolla.com/question/54157/sailfishos-open-source-collaboration-meeting-planning/

Thanks and best regards,
James Noori (Jaymzz),
Community Manager


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org