Thursday, 2023-03-09

ViGe#startmeeting Sailfish OS, open source, collaboration -- 9th March 202308:00
sailbotMeeting started Thu Mar  9 08:00:10 2023 UTC. The chair is ViGe. Information about MeetBot at
sailbotUseful Commands: #action #agreed #help #info #idea #link #topic.08:00
*** sailbot changes topic to " (Meeting topic: Sailfish OS, open source, collaboration -- 9th March 2023)"08:00
ViGe#info Meeting information and agenda can be found here:08:00
ViGeI am the meeting's chairperson today, and will be doing my best to keep time and order. Please respect the timings and bee-hive.08:00
ViGe#topic Brief introduction (5 min). Please prefix your name/handle with #info08:00
*** sailbot changes topic to "Brief introduction (5 min). Please prefix your name/handle with #info (Meeting topic: Sailfish OS, open source, collaboration -- 9th March 2023)"08:00
ViGe#info Ville Nummela, sailor@Jolla, also the chairperson today08:01
pherjung[m]#info pherjung, community08:01
rainemak#info Raine Mäkeläinen, sailor@Jolla08:01
ViGehi pherjung, nice to see you. I was wondering if anyone will show up as we didn't have any topics for today, except for the recurring ones08:02
rainemakhi pherjung[m] nice to see you as well08:02
pherjung[m]there is always something to talk about08:03
Thaodan#info Björn Bidar, sailor @ Jolla08:03
dcaliste#info dcaliste, community08:04
ViGeSo 3-2 for the sailors08:05
ViGeWe didn't have any questions sent in on the forum on time, so let's start with the bug reports:08:05
ViGe#topic Untracked bug reports (5 min -- asked by Community Bug Coordination Team)08:05
*** sailbot changes topic to "Untracked bug reports (5 min -- asked by Community Bug Coordination Team) (Meeting topic: Sailfish OS, open source, collaboration -- 9th March 2023)"08:05
ViGe#info Our regular Community Bug Coordination Team update - see the forum for the links to actual bug reports08:05
ViGe#info <Jolla> As a result of the work of the bug team, we now have an additional:08:05
ViGe#info <Jolla> 10 high quality bug reports now recorded internally and tagged as "tracked" and08:06
ViGe#info <Jolla> 1 bug report closed.08:06
ViGe#info <Jolla> Thank you also to everyone who has reported issues.08:06
pherjung[m]There are still about +900 untracked bug reports and many are duplicate, already fixed or even wrong.08:08
ViGeplenty of work left. And there's always more bug reports coming in. But your work is really appreciated!08:09
pherjung[m]Since there is a 10-bug limit, I prefer to give priority to real bugs. But a lot of bugs could be closed easily08:09
ViGe#topic Open PR discussion (5 mins -- asked by jolla)08:10
*** sailbot changes topic to "Open PR discussion (5 mins -- asked by jolla) (Meeting topic: Sailfish OS, open source, collaboration -- 9th March 2023)"08:10
pherjung[m]For instance, this one
ViGe#info <jolla> Any open PRs to discuss?08:10
rainemakpherjung[m], that's a valid and known. I didn't had time yesterday to mark it as tracked.08:12
ViGepherjung[m]: I think that 10-bug limit really applies to "real bugs" only, as those are the ones that I have to do some work about.08:12
pherjung[m]pherjung[m]: This one is definitely a duplicate08:13
dcalistepherjung[m], would it be a large work from your side to give a complete list of duplicates or already fixed so they could be marked automatically ?08:13
rainemakpherjung[m], this was the previous one08:13
pherjung[m]dcaliste: I already do a triage which bug should be closed or is a duplicate of one08:14
pherjung[m]but as I'm not a dev, I may sometimes do some errors08:14
pherjung[m]I aim to ease the work of Jolla08:15
dcalisteSo ViGe, what is blocking to automatically close them ? If there are (some) errors, one can still reopen the faulty ones.08:15
ViGeEveryone can make mistakes. Reopening a bug report is easy.08:15
pherjung[m]because if a real bug is closed, it can be problematic08:15
rainemakpherjung[m], no worries there. Also it's not big deal to keep two or more issues open if you're not sure whether they are duplicates or not08:15
pherjung[m]I usually try to be sure and I took the habit to ask the other members if I'm not sure08:16
ViGedcaliste: We don't have any mechanism for automatically closing anything. It's still manual work even if we have a list.08:16
rainemakpherjung[m], what I find important is traceability between issues ie. cross link issues08:16
pherjung[m]ViGe: with some webscraping, everything is doable :)08:17
pherjung[m]but the API may offer this possibility08:17
dcalisteViGe, ah that explains the 10 bugs limit !08:17
ViGepherjung[m]: I'm quite sure it's possible through the API. Unfortunately the API is not exactly easy to get started with.08:19
ViGeLooks like no one had any PRs to discuss, let's move on to the general discussion, we can continue this bug report discussion under that topic :)08:19
ViGe#topic General discussion (20 min)08:19
*** sailbot changes topic to "General discussion (20 min) (Meeting topic: Sailfish OS, open source, collaboration -- 9th March 2023)"08:19
pherjung[m]I can take a look08:20
ViGepherjung[m]: Well, after you have managed to create the token, it's not that hard actually. The token creation is the hard part if you are trying to make a real app, but in this case it could be made on the browser which makes things easier.08:21
flypigBy the way, I found closing bugs can sometimes benefit from a bit of investigation. Some bug reporters rightly get upset if they think they're being ignored or overridden (e.g. bug closed without explanation).08:24
ViGehi flypig!08:24
pherjung[m]oh hi fylpig!08:24
flypigHello :)08:24
flypigSorry I was late, so didn't add my name at the start.08:24
pherjung[m]you're not the first one08:25
ViGeflypig: You definitely have a point there. So mass-closing with a script might not be the best solution really.08:25
pherjung[m]but, we could add a comment08:25
flypigWell, it could ruffle some feathers, but if you try, it might just work fine.08:25
dcalistehello flypig ! I agree, and in case of duplicate, the script may provide the link to the original, saying that's it's still possible to contradict if the author think so.08:25
flypigRight, if there's a comment that explains how to reverse the situation ('ping someone if you think this is a mistake...'), that's probably fine.08:26
pherjung[m]I'm not fan to automatically close duplicate bug reports08:26
pherjung[m]And honestly there aren't a lot08:27
flypigNice work with the newsletter by the way. The last one was great; really enjoyed reading about CLAT.08:29
flypigAnd the poll is fascinating too :)08:30
rainemakflypig, great to hear!08:33
ViGeflypig: you really set the bar quite high there. I have a feeling that even if there are more people involved now, there's no way we can reach the level that you set. But we are certainly trying!08:33
flypigThat's very generous of you, but to me it looks like it's benefiting from some new blood. It's great :)08:35
ViGeAlright, time to start wrapping up08:40
ViGe#topic Next meeting time and date (5 min)08:40
*** sailbot changes topic to "Next meeting time and date (5 min) (Meeting topic: Sailfish OS, open source, collaboration -- 9th March 2023)"08:40
ViGeProposing Thursday 30th March at 08:00am UTC.08:40
ViGeAgain a bit longer gap, to get us synced so that the meeting and newsletter are on alternating weeks.08:40
dcalisteWould be ok for me.08:41
flypigA good choice :)08:41
ThaodanSounds good to me too.08:42
rainemakSame here08:42
pherjung[m]Here too08:42
ViGeLooks like there are no objections :)08:43
ViGe#info Next meeting will be held on Thursday 30th March 2023 at 08:00am UTC: 2023-03-30T0800Z08:43
flypigAnniversary of the National Bank of Greece being founded in 1841.08:43
ViGeOk, that's all for today! Thanks everyone!08:44
sailbotMeeting ended Thu Mar  9 08:44:49 2023 UTC.08:44
sailbot Minutes:
sailbot Minutes (text):
sailbot Log:
*** sailbot changes topic to "Next meeting will be held on Thursday 9th March 2023 at 08:00 UTC"08:44
flypigThanks ViGe!08:45
rainemakThanks ViGe!08:47
ExTechOp#info Otto Mäkelä, community08:52
ExTechOp(sorry for being so late)08:52
pherjung[m]well, you're definitely are too late08:53
pherjung[m]the meeting is already ended :p08:53
ExTechOpI kinda guessed it :-/08:53
ExTechOpHowever, the /topic is still for the old meeting08:53
*** ChanServ changes topic to "Next meeting will be held on Thursday 30th March 2023 at 08:00am UTC. Topics can be made/read here:"08:54
ViGefixed that :)08:54

Generated by 2.17.1 by Marius Gedminas - find it at!