@rinigus, drop it as a topic in the meeting thread https://together.jolla.com/question/54157/sailfishos-open-source-collaboration-meeting-planning/
On Wed, Aug 23, 2017 at 9:56 AM, rinigus <rinigus....@gmail.com> wrote: > Hi, > > it would be great to get update on the state of QtLocation 5.6. As > suggested by Chris, *"veskuh would be the best person to describe our > intent going forward, and possible roadmap for updating"*. In particular, > for people working on map and navigation apps, would be good to know > > * 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? > > One of the questions posted earlier (Jul 7) on whether Jolla started > working on it was already replied by Chris (No). > > Best wishes, > > Rinigus > > > On Thu, Aug 3, 2017 at 8:39 AM, rinigus <rinigus....@gmail.com> wrote: > >> Morning, >> >> this is to bump the thread with the hope of getting a reply regarding >> QtLocation status and plans. >> >> Cheers, >> >> Rinigus >> >> On Thu, Jul 13, 2017 at 9:08 AM, rinigus <rinigus....@gmail.com> wrote: >> >>> 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 <chris.ad...@jolla.com> >>> 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 >>>> <http://redir.aspx?REF=zWm_Sf04kBkJblyUyNjvCqS4mOnF1wFPhx6A68AtZy0LC5Moh8nUCAFodHRwczovL2dpdC5tZXJwcm9qZWN0Lm9yZy9tZXItY29yZS9xdGxvY2F0aW9uL2FjdGl2aXR5> >>>> 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 >>>> <http://redir.aspx?REF=EUOWHvr5jEnv6pxp6JMfdOvXxr5kUYRUWfZnQJrvFZ4LC5Moh8nUCAFtYWlsdG86dXNlcnMuZ2l1bGlldHRhQGdtYWlsLmNvbQ..> >>>> > 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 <a...@piggz.co.uk >>>>> <http://redir.aspx?REF=Ty7ixpUauyWMAaPdQIs5VwKyAP15fbqxGVH7-4nRse0LC5Moh8nUCAFtYWlsdG86YWRhbUBwaWdnei5jby51aw..> >>>>> > 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 <otsal...@iki.fi >>>>>> <http://redir.aspx?REF=t28cqNItUuzUjyoP1dTK_fgFVhzqnX8cRi9ZMXZxvl0LC5Moh8nUCAFtYWlsdG86b3RzYWxvbWFAaWtpLmZp>> >>>>>> 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 >>>>>>> <http://redir.aspx?REF=j_RQOXU9GPO6D9nvJZUbzRDGnbylwIKxPwL8gkuBKWgLC5Moh8nUCAFodHRwczovL2dpdGh1Yi5jb20vcXQvcXRsb2NhdGlvbg..> >>>>>>> ). >>>>>>> >>>>>>> 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 >>>>>>> <http://redir.aspx?REF=CHz8pNz-HL_oBLrPditWfJlL33f48cvNpNuF_NFvQ-sLC5Moh8nUCAFodHRwczovL2dpdGh1Yi5jb20vcXQvcXRsb2NhdGlvbi9jb21taXQvNzFkYWJiNWRjMzMwYTQ3ZDkxZWU5MTdjYTYwYzg3MWE4OGU4YTQyYQ..> >>>>>>> >>>>>>> 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 <otsal...@iki.fi >>>>>>> <http://redir.aspx?REF=t28cqNItUuzUjyoP1dTK_fgFVhzqnX8cRi9ZMXZxvl0LC5Moh8nUCAFtYWlsdG86b3RzYWxvbWFAaWtpLmZp> >>>>>>> > >>>>>>> _______________________________________________ >>>>>>> SailfishOS.org Devel mailing list >>>>>>> To unsubscribe, please send a mail to devel-unsubscribe@lists.sailfi >>>>>>> shos.org >>>>>>> <http://redir.aspx?REF=O_CViBGcoNyp6DKjzWW_cpv1hoZ3JtwPzlvDFu3I7m0LC5Moh8nUCAFtYWlsdG86ZGV2ZWwtdW5zdWJzY3JpYmVAbGlzdHMuc2FpbGZpc2hvcy5vcmc.> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> SailfishOS.org Devel mailing list >>>>>> To unsubscribe, please send a mail to devel-unsubscribe@lists.sailfi >>>>>> shos.org >>>>>> <http://redir.aspx?REF=O_CViBGcoNyp6DKjzWW_cpv1hoZ3JtwPzlvDFu3I7m0LC5Moh8nUCAFtYWlsdG86ZGV2ZWwtdW5zdWJzY3JpYmVAbGlzdHMuc2FpbGZpc2hvcy5vcmc.> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> SailfishOS.org Devel mailing list >>>>> To unsubscribe, please send a mail to devel-unsubscribe@lists.sailfi >>>>> shos.org >>>>> <http://redir.aspx?REF=O_CViBGcoNyp6DKjzWW_cpv1hoZ3JtwPzlvDFu3I7m0LC5Moh8nUCAFtYWlsdG86ZGV2ZWwtdW5zdWJzY3JpYmVAbGlzdHMuc2FpbGZpc2hvcy5vcmc.> >>>>> >>>> >>>> >>>> _______________________________________________ >>>> SailfishOS.org Devel mailing list >>>> To unsubscribe, please send a mail to devel-unsubscribe@lists.sailfi >>>> shos.org >>>> >>> >>> >> > > _______________________________________________ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscribe@lists. > sailfishos.org >
_______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
