sledges | #startmeeting Sailfish OS, open source, collaboration -- 14th January 2021 | 08:00 |
---|---|---|
sailbot_ | Meeting started Thu Jan 14 08:00:06 2021 UTC. The chair is sledges. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
sailbot_ | Useful Commands: #action #agreed #help #info #idea #link #topic. | 08:00 |
sledges | #info Meeting information and agenda can be found here: | 08:00 |
sledges | #link https://forum.sailfishos.org/t/community-meeting-on-irc-14th-jan-2021/4030 | 08:00 |
sledges | I am the meeting's chairperson today, and will be doing my best to keep time and order. Please behave, and respect engine timing. | 08:00 |
sledges | #topic Brief introduction (5 min). Please prefix your name/handle with #info | 08:00 |
* sledges pokes sailbot_ with a stick | 08:01 | |
*** ChanServ sets mode: +o sailbot_ | 08:02 | |
sledges | #info Simonas Leleiva - privateer for Jolla | 08:02 |
ViGe | #info Ville Nummela - Sailor@Jolla | 08:02 |
karry | #info Lukas Karas - community member, developer | 08:03 |
abranson | #info Andrew Branson - Jolla | 08:03 |
fridl | #info fridlmue - Community | 08:03 |
sledges | #topic Silica control: ExpandingSection (10 min -- asked by fridlmue) | 08:06 |
*** sailbot_ changes topic to "Silica control: ExpandingSection (10 min -- asked by fridlmue) (Meeting topic: Sailfish OS, open source, collaboration -- 14th January 2021)" | 08:06 | |
sledges | #info <fridlmue> ExpandingSection is in the "ComponentGallery" but not in the Documentation. In the last meeting it was mentioned it would not be part of the API yet. | 08:06 |
sledges | #info <fridlmue> I use it in an App and would love to leave it like that as it is a nice control. But the Animation is nicer in the ComponentGallery than in my app and I don't find no documentation for that. | 08:06 |
sledges | #info <fridlmue> Is it planed to add it to the API and provide Documentation? Is my App now "illegally" in the Harbor? ;p (And how to influence the Animation to make it nicer?) | 08:06 |
sledges | #info <fridlmue> Long version: | 08:07 |
sledges | #link https://forum.sailfishos.org/t/expandingsection-in-silica-documentation/3994 | 08:07 |
sledges | #info <Jolla> ExpandingSection is not documented, but allowed component that is part of public API. The transition issues you are describing sound like a bug, could you link example code to the forum discussion so we can check? | 08:07 |
fridl | Sure, I can do that! I would assume wrong usage at the moment ;-) | 08:08 |
fridl | Can I help with providing documentation when fully understood the component? | 08:08 |
flypig | #info David Llewellyn-Jones - sailor@jolla&late | 08:09 |
jpetrell | documentation help is definitely appreciated :) | 08:10 |
flypig | The documentation source files aren't public, I think. | 08:11 |
jpetrell | not sure there is any | 08:11 |
jpetrell | overall ExpandingSection has limited uses, inside platform we have only used it to implement few dual SIM settings | 08:12 |
ViGe | Yup, we should think about the processes who the community members could help us with the documentation | 08:12 |
ViGe | This doesn't apply only to ExpandingSection but our documentation in general | 08:12 |
fridl | jpetrell: If documented for sure it would be used more often ;-) | 08:12 |
flypig | I guess it's best to receive any documentation in qdoc format. | 08:13 |
jpetrell | often when user opens a particular page you want to show all the information in full, and allow scrolling through all the content without requiring taps in between to open sections | 08:13 |
jpetrell | but sure expanding sections has its uses, if you have repetitive content under many sections | 08:13 |
jpetrell | the expanding animation can be a bit obtrusive with sections resizing and headers moving to left and right simultaneously | 08:14 |
fridl | Ok, I think from my side we are done here. Summary: 1) We can use it 2) No official docs, help welcome (no defined way at the moment) 3) animations can be tricky with this component | 08:17 |
fridl | 4) I can ask for help with the specific issue on the forums. | 08:18 |
fridl | thanks | 08:18 |
flypig | Nice summary :) | 08:18 |
sledges | #info No official docs, help welcome (no defined way at the moment, format most probably qdoc) | 08:19 |
sledges | jpetrell: are you ok with following that forum thread for bug reports etc, or should we stick to these meetings for info exchange? | 08:20 |
sledges | ah, you already mentioned "could you link example code to the forum discussion so we can check" | 08:22 |
sledges | if any aspects in the forum thread still get unanswered, please raise them in these meetings | 08:22 |
sledges | let's move on | 08:22 |
sledges | #topic OpenSSL 1.0 deprecation (10 min -- asked by Thaodan) | 08:22 |
fridl | Ok, I'll do! | 08:22 |
*** sailbot_ changes topic to "OpenSSL 1.0 deprecation (10 min -- asked by Thaodan) (Meeting topic: Sailfish OS, open source, collaboration -- 14th January 2021)" | 08:22 | |
sledges | #info <Thaodan> What are the plans for the deprecation of OpenSSL 1.0 and moving forward with later OpenSSL versions. | 08:23 |
sledges | #info <Jolla> In the upcoming Sailfish OS version we have updated OpenSSL to the latest stable version 1.1.1. | 08:23 |
sledges | #link https://git.sailfishos.org/mer-core/openssl/merge_requests?scope=all&utf8=%E2%9C%93&state=merged | 08:23 |
sledges | in fact Thaodan was the one who updated as you can see:) | 08:25 |
sledges | he probably wanted to raise this topic because community kept asking:) | 08:25 |
ViGe | He wanted to raise the topic as a heads up so that the community members are aware of what's happening :) | 08:26 |
fridl | sledges: So we know, keeping asking helps ;-P | 08:26 |
flypig | What will happen to apps in harbour that are now incompatible? | 08:27 |
ViGe | flypig: They will keep on working | 08:27 |
ViGe | at least for the time being | 08:27 |
ViGe | the validator will display a warning if you try to use openssl 1.0 in new packages | 08:28 |
flypig | I thought it wasn't backwards binary (or source) compatible. | 08:28 |
ApBBB | the way i read the question the answer seems to be what Vige answered. | 08:29 |
flypig | "They will keep on working": that's good :) | 08:29 |
ApBBB | ie for how long they will continue to work etc | 08:29 |
ViGe | ApBBB: It has not been decided when we will remove the old libraries, but it will happen eventually | 08:30 |
sledges | #info Harbour apps using 1.0 will continue working for the time being | 08:32 |
sledges | naturally, the 1.1.1 libraries to harbour rules are also (being) added | 08:34 |
sledges | let's move on from this topic (and 1.0 eventually:) | 08:35 |
sledges | #topic General Discussion (30 min) | 08:35 |
*** sailbot_ changes topic to "General Discussion (30 min) (Meeting topic: Sailfish OS, open source, collaboration -- 14th January 2021)" | 08:35 | |
sledges | Here's hoping that everyone had a good holiday break given the world's state!.. | 08:35 |
ApBBB | its no fun when you have to stay in :/ | 08:36 |
ApBBB | BTW are we getting a 3.5 release or the next release is 4.0? | 08:36 |
sledges | snow fun? ;) | 08:36 |
flypig | Groan! | 08:36 |
sledges | flypig: that was a legitimate question though :P | 08:37 |
ApBBB | i have to get to the mountains to find snow around my part of the world. and i cant. (lockdown etc) | 08:37 |
sledges | we're still allowed to go outside for recreation | 08:37 |
flypig | The snow in Finland looks wonderful! | 08:37 |
ApBBB | sledges traveling is not allowed between prefectures so i cant reach it. and the ski resorts are closed. :/ | 08:38 |
ApBBB | have you had any discussions about new apis??? after the poll etc? | 08:39 |
sledges | no snow here either (would have to travel thousand miles to reach one), so have to work with what we've got :( "no snow jogging" etc. But the frosty "Beast from the East" is approaching they say | 08:40 |
sledges | ViGe: how did that poll go? ^^ | 08:40 |
birdzhang[m]1 | What's Jolla's unique App Support tech for Linux? I know you can't tell me, but i still want ask :) | 08:41 |
ViGe | sledges: It went really well, we got 76 answers! | 08:41 |
ApBBB | birdzhang[m]1 i don't think there is anything special. after all its just linux | 08:42 |
ApBBB | Vige any discussions about the apis? | 08:42 |
ViGe | ApBBB: If you mean Jolla internal discussions, those happen all the time :) | 08:43 |
ApBBB | ok. | 08:43 |
birdzhang[m]1 | ApBBB: I don't thinks so, maybe it means GUI apps | 08:43 |
ApBBB | Vige now we need the actual apis :P | 08:44 |
sledges | #info API poll went really well with 76 answers | 08:46 |
sledges | #link https://forum.sailfishos.org/t/what-apis-are-missing-from-harbour/4017 | 08:46 |
sledges | #link https://forum.sailfishos.org/t/api-priority-poll-take-ii/4159 | 08:46 |
ViGe | ApBBB: Yeah, that's the hard part... but we'll get there! | 08:46 |
ApBBB | what pleases me is that the location one that is high on the list is just a switch. and i hope that you will turn it on. | 08:47 |
ApBBB | on the subject of push notifications. wasn;t there an effort back in the early days of sfos for something like that?? | 08:48 |
flypig | I think some of the results were a little surprising (to me, at least). Push notifications being one of them. | 08:48 |
ApBBB | by the community i think but cant remember much. | 08:48 |
flypig | Sledges, you may need to amend your info line above. There are 78 answers now ;) | 08:50 |
sledges | is nice we could update qtlocation and qtpositioning recently as they are not governed by licence change | 08:50 |
sledges | flypig: logs have timestamps ;) | 08:50 |
ViGe | ApBBB: Well, QtPositioning upgrade is already coming in the next release. I'm afraid QtLocation might have to wait a bit longer. But it's definitely on our todo list. | 08:50 |
sledges | ViGe: i hope we're talking about the same thing:) https://git.sailfishos.org/mer-core/qtlocation/merge_requests/18 | 08:51 |
ViGe | flypig: push notifications was surprising to me as well, as I don't recall anyone being vocal about it! | 08:51 |
abranson | Push notif wouldn't be as popular if background services were allowed | 08:51 |
karry | with QtLocation, is there any decision for plugin implementation? If I undertand it correctly, it is just api specification that may have various implementations... | 08:51 |
flypig | abranson, that's a good point. Hadn't thought of that. | 08:52 |
abranson | if you take away that need, they're only used for spamming ;) | 08:52 |
ViGe | sledges: even if QtLocation was upgraded, it's not allowed in Harbour (yet) :/ | 08:52 |
ApBBB | vige my mistake. position is the easy one. not the location one. as you explained in the forum | 08:52 |
sledges | ViGe: ok, upgrade vs api, got it | 08:52 |
rinigus | karry: I presume qtlocation "update" is on the level of qt 5.6 | 08:55 |
rinigus | not sure if it includes update in plugins | 08:56 |
rinigus | (but I haven't looked into these old specs) | 08:56 |
ApBBB | i hope that for 4.0 we will see a QT update | 08:56 |
ApBBB | if it cant be updated (for lisencing reasons or whatever) it might even make more sense to move to another toolkit :P | 08:57 |
fridl | ApBBB today brings up the elephants in the room, haha | 08:58 |
ViGe | rinigus: the qtlocation and qtpositioning were upgraded to 5.4. | 08:58 |
rinigus | ... just looked up on when it was released - 10 Dec 2014 :) . | 08:59 |
ApBBB | fridl sfos needs to move forward | 09:01 |
ApBBB | so many things are held behind by the old Qt | 09:01 |
sledges | and on that bombshell it's time to end (the topic) | 09:04 |
sledges | #topic Next meeting time and date (5 min) | 09:04 |
*** sailbot_ changes topic to "Next meeting time and date (5 min) (Meeting topic: Sailfish OS, open source, collaboration -- 14th January 2021)" | 09:04 | |
sledges | Proposing 11th February at 8am UTC | 09:04 |
sledges | 4 weeks from now, you might guess why ;) | 09:04 |
dr_gogeta86 | why ? | 09:06 |
dr_gogeta86 | despite dropping 4.x | 09:06 |
sledges | -ETOOBUSY | 09:06 |
sledges | dr_gogeta86: "despite dropping 4.x" that's pure speculation | 09:08 |
dr_gogeta86 | I will wait so | 09:08 |
sledges | btw, expect one more "last l10n round extension" soon (within days), be curious, and you'll know what release is what version:) | 09:09 |
sledges | #info Next meeting will be held on Thursday 11th February 2021 at 8:00am UTC: 2021-02-11T08Z | 09:09 |
sledges | since no objections | 09:09 |
sledges | thanks all! | 09:09 |
sledges | #endmeeting | 09:09 |
sailbot_ | Meeting ended Thu Jan 14 09:09:48 2021 UTC. | 09:09 |
sailbot_ | Minutes: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2021/sailfishos-meeting.2021-01-14-08.00.html | 09:09 |
sailbot_ | Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2021/sailfishos-meeting.2021-01-14-08.00.txt | 09:09 |
sailbot_ | Log: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2021/sailfishos-meeting.2021-01-14-08.00.log.html | 09:09 |
*** sailbot_ changes topic to "Next meeting will be held on Thursday 14th of January 2021 at 8:00am UTC. Topics can be read here: https://forum.sailfishos.org/t/community-meeting-on-irc-14th-jan-2021/4030" | 09:09 | |
dr_gogeta86 | sledges, i hope to contribute again in traslation | 09:09 |
sledges | jolly good, Italians need you:) | 09:10 |
sledges | ti aspettiamo | 09:10 |
karry | Thank you for the meeting and all the informations. I am going to use ExpandingSection :-P bye | 09:10 |
fridl | karry: Tell me, if you found out how to use probably ;-) | 09:11 |
fridl | *properly | 09:11 |
dr_gogeta86 | sledges, seen fravaccaro quit and cleanup all the evidence | 09:14 |
sledges | allora torno a fare i reviews personalmente:) | 09:17 |
*** ChanServ changes topic to "Next meeting will be held on Thursday 11th of February 2021 at 8:00am UTC. Topics can be read here: https://forum.sailfishos.org/t/community-meeting-on-irc-11th-feb-2021/4306" | 09:21 | |
*** vgtw_ is now known as vgtw | 20:33 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!