| *** ChanServ sets mode: +o sailbot | 08:00 | |
| flypig | Let's see if I can do a better job today. | 08:00 |
|---|---|---|
| flypig | #startmeeting Sailfish OS, open source, collaboration -- 3rd February 2022 | 08:00 |
| sailbot | Meeting started Thu Feb 3 08:00:53 2022 UTC. The chair is flypig. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
| sailbot | Useful Commands: #action #agreed #help #info #idea #link #topic. | 08:00 |
| *** sailbot changes topic to " (Meeting topic: Sailfish OS, open source, collaboration -- 3rd February 2022)" | 08:00 | |
| flypig | #info Meeting information and agenda can be found here: | 08:01 |
| flypig | #link https://forum.sailfishos.org/t/community-meeting-on-irc-3rd-february-2022/10002 | 08:01 |
| flypig | Hello all. | 08:01 |
| flypig | I am the meeting's chairperson today, and will be doing my best to keep time and order. Please respect the timings and keep your arms inside the vehicle. | 08:01 |
| flypig | #topic Brief introduction (5 min). Please prefix your name/handle with #info | 08:01 |
| *** sailbot changes topic to "Brief introduction (5 min). Please prefix your name/handle with #info (Meeting topic: Sailfish OS, open source, collaboration -- 3rd February 2022)" | 08:01 | |
| flypig | #info David Llewellyn-Jones - sailor@jolla and today's chair | 08:01 |
| abranson | #info Andrew Branson - sailor@Jolla | 08:02 |
| pherjung | #info pherjung community | 08:04 |
| sledges | #info Simonas Leleiva -- privateer for Jolla | 08:05 |
| ViGe | #info Ville Nummela - sailor@Jolla | 08:05 |
| jusa | #info Juho Hämäläinen - sailor@jolla | 08:05 |
| dcaliste | #info Damien Caliste, community | 08:06 |
| flypig | Thanks all for joining :) It's quite quiet today, I guess lots of people preparing for FOSDEM... | 08:07 |
| flypig | We didn't get any community questions today, so I made one question myself. | 08:08 |
| flypig | #topic Ideas for improving the community meetings (15 mins -- asked by flypig) | 08:08 |
| *** sailbot changes topic to "Ideas for improving the community meetings (15 mins -- asked by flypig) (Meeting topic: Sailfish OS, open source, collaboration -- 3rd February 2022)" | 08:08 | |
| flypig | #info <flypig> We're not planning any changes to the community meetings in the immediate future, but it's always good to get input. | 08:08 |
| flypig | #info <flypig> Let's have some open-ended discussion: what would you change to make the meetings work better for you? | 08:08 |
| flypig | #info <flypig> Feel free to continue the conversation as well on the forum. | 08:08 |
| flypig | #link https://forum.sailfishos.org/t/ideas-for-improving-the-community-meetings/10166 | 08:08 |
| flypig | #info <Jolla> No answer from Jolla, this is all about you. | 08:08 |
| pherjung | For instance, why is the telegram bridge read-only? | 08:08 |
| flypig | That's a good starting question, but I don't know the answer. Is that Thaodan's bridge? | 08:09 |
| pherjung | I'm not sure, but I think yes. At least, last time there was an issue, he resolved it | 08:10 |
| ViGe | I believe it is. It's not an official service (by Jolla), but just something he does on his free time. | 08:10 |
| Thaodan | flypig: Yes its run by me | 08:10 |
| Thaodan | #info Björn Bidar Sailor @ Jolla | 08:11 |
| flypig | Well, first off, thanks for running it. | 08:11 |
| flypig | Could it be made read/write, and if so, would that be a good thing? | 08:11 |
| Thaodan | it is just not in this channel | 08:12 |
| flypig | Was there a reason for that? | 08:12 |
| Thaodan | since the meeting bot has issues with the bridge being one user on the IRC side, I'm not sure if it can recognize telegram users | 08:13 |
| flypig | So, I guess it would lead to messy minutes? | 08:14 |
| ViGe | I doubt that really matters. All the important stuff is anyway #infoed by the meeting chair. | 08:14 |
| Thaodan | A normal user can do info or link to | 08:15 |
| ViGe | Sure, but that doesn't really happen | 08:15 |
| Thaodan | but I guess we can test. | 08:16 |
| dcaliste | Except during introduction time. | 08:16 |
| Thaodan | ^ exactly | 08:16 |
| abranson | I think we can remove spurious messages from the minutes too | 08:16 |
| flypig | We usually have people join in who don't add their details at the start anyway. | 08:16 |
| Thaodan | There's also a link to webirc for joining the meeting in the telegram channel description | 08:17 |
| Thaodan | I would just test it how good it works and then see | 08:18 |
| abranson | it's a good meeting to test that, with no community questions | 08:18 |
| pherjung | Just tried using the link and it doesn't work | 08:18 |
| flypig | We can do it now? | 08:18 |
| flypig | pherjung, doesn't work in what way? | 08:20 |
| Thaodan | No the telegram side is read only because its a channel not a group | 08:20 |
| Thaodan | Have to create a new group, add it to the bridge and test. | 08:20 |
| flypig | Okay, so it would require some significant changes. | 08:20 |
| flypig | In which case, could we trial a Telegram group for the next meeting? | 08:21 |
| Thaodan | Not that significant but editing the bridge config and create a new channel | 08:21 |
| Thaodan | sure | 08:21 |
| flypig | Any objections from anyone? | 08:21 |
| pherjung | I'm not sure if I understood correctly. On Telegram, there is this link (https://webchat.freenode.net/?channels=#sailfishos-meeting) and it doesn't work. Perhaps because it's freenode | 08:22 |
| Thaodan | We can also do a test meeting. | 08:22 |
| Thaodan | pherjung: Are you on the old channel? | 08:22 |
| Thaodan | New one has oft as link | 08:22 |
| Thaodan | "One-way connection, if you want to participate join on IRC at https://webchat.oftc.net/?channels=sailfishos-meeting" | 08:22 |
| Thaodan | Invite link: | 08:23 |
| Thaodan | https://t.me/joinchat/AAAAAFcbasJX67Fu-aGxxQ | 08:23 |
| ViGe-webchat | seems to work :) | 08:23 |
| pherjung | oh, nice to know :) | 08:23 |
| flypig | Thaodan, I'd be happy to do a test meeting with you. O/w we could run it at the next meeting, but without advertising the group. | 08:25 |
| flypig | We actually hit time on this topic. But we got a good suggestion, thank you pherjung. | 08:26 |
| Thaodan | A test meeting in between would be better I think since if it works we can switch the channels over again. | 08:26 |
| flypig | Okay, let's do that. | 08:26 |
| flypig | I'll make an action (exciting!) | 08:26 |
| T42_ | <unknown> #info foobar | 08:26 |
| thilo[m] | #info thigg - community | 08:27 |
| pherjung | I was on the right channel. It just the pinned message that point to the wrong link | 08:27 |
| flypig | #action Thaodan to run a Telegram group test meeting. | 08:27 |
| flypig | Alright, let's move to general discussion. | 08:27 |
| T42_ | <unknown> #link foobar.com | 08:28 |
| flypig | #topic General discussion (20 min) | 08:28 |
| *** sailbot changes topic to "General discussion (20 min) (Meeting topic: Sailfish OS, open source, collaboration -- 3rd February 2022)" | 08:28 | |
| Thaodan | lets see if that appears in the channel history | 08:28 |
| Thaodan | eh meeting history | 08:28 |
| flypig | We're not in a rush today, so can extend the time if there's lots of discussin. | 08:28 |
| flypig | I'd guess the <unkonwn> prefix will throw it, but let's see. | 08:28 |
| Thaodan | The unknown will go away when the telegram side is not a channel | 08:29 |
| flypig | But will it prefix <handles> instead? | 08:29 |
| Thaodan | Telegram Channels are ro except for the admin of it | 08:30 |
| Thaodan | yes | 08:30 |
| Thaodan | <T42_> <foobar> | 08:30 |
| Thaodan | Usernames are an issue with telegram users since most don't set them | 08:31 |
| Aminda[m] | did you ever migrate from dead fruitiex/teleirc to either Matterbridge or the other teleirc? At least Matterbridge is working on fixing the unknown | 08:32 |
| Thaodan | Matterbridge now | 08:33 |
| Thaodan | *its Matterbridge now | 08:33 |
| flypig | To tackle the prefix issue properly, probably requires changes to meetbot. | 08:35 |
| flypig | In case there are any python devs out there who'd like a challenge. | 08:36 |
| Thaodan | The issue is that the telegram users are not real users for the irc side. | 08:36 |
| dcaliste | As general discussion, are you aware of this issue at Jolla : https://forum.sailfishos.org/t/incoming-voice-calls-dont-get-rejected-hangup-same-bug-via-the-ui-and-programmatically/10076? | 08:38 |
| dcaliste | It makes rejected call, not rejected on first attempt. | 08:38 |
| dcaliste | Condition to reproduce are not clear though. | 08:38 |
| thilo[m] | Flypig: repo link and preferably an issue with the spec? | 08:38 |
| flypig | #link https://forum.sailfishos.org/t/incoming-voice-calls-dont-get-rejected-hangup-same-bug-via-the-ui-and-programmatically/10076 | 08:39 |
| dcaliste | I can reproduce from my work landline, but not from my home one for instance. | 08:39 |
| flypig | thilo[m], sorry, could you clarify please? | 08:39 |
| thilo[m] | For meetbot | 08:39 |
| flypig | Ah, yes, thanks thilo[m]. | 08:39 |
| flypig | #link http://meetbot.debian.net/Manual.html#id11 | 08:40 |
| flypig | #undo | 08:40 |
| sailbot | Removing item from minutes: <MeetBot.items.Link object at 0x7f8589a72ac8> | 08:40 |
| flypig | #link http://meetbot.debian.net/Manual.html | 08:40 |
| ExPLIT[m] | I have also one bug, which is difficult to reproduce. On XA2 Plus, since 4.3 after some time phone is hanging in the black screen and only green light is blinking. Only reset helps. I think it has something to do with CalDav/CardDav sync, but i am not sure... | 08:40 |
| Thaodan | that's the old meetbot | 08:40 |
| Thaodan | For the issue on the matterbridge side: https://github.com/42wim/matterbridge/issues/667 | 08:41 |
| Thaodan | #link https://github.com/42wim/matterbridge/issues/667 | 08:41 |
| flypig | I suppose this is the repo? | 08:41 |
| flypig | #link https://github.com/emonty/meetbot | 08:41 |
| dcaliste | ExPLIT[m], can you setup persistant journal and look at the journal log of last boot when it's happening ? Maybe post on the forum the relevant part of the log ? | 08:42 |
| ExPLIT[m] | dcaliste: Thanks, will do that | 08:42 |
| flypig | dcaliste, thanks for flagging that call rejection bug. I'm checking if we have a bug about it. | 08:43 |
| dcaliste | ExPLIT[m] : https://www.golinuxcloud.com/enable-persistent-logging-in-systemd-journald/ for persistent journal. | 08:44 |
| dcaliste | Thank you flypig. | 08:44 |
| dcaliste | I'm looking a bit into it, gathering Ofono logs for failing or successful rejection, to see what are the differences. | 08:44 |
| Thaodan | Meetbot uses supybot which is dead. | 08:44 |
| Thaodan | There's a replacement for that https://pypi.org/project/hcoop-meetbot/ | 08:45 |
| Thaodan | Supybot has been replaced by https://github.com/ProgVal/Limnoria | 08:45 |
| pherjung | When a bug report is published by the community. What is the process on your side? Do you reproduce it and once it's a real bug you create an issue on your bugtracker? If it's so, couldn't be possible to add for instance a tag "tracked" on the reported issue by the community? | 08:46 |
| thilo[m] | Pherjung: +1 | 08:46 |
| flypig | We had something similar on TJC, it would be good to do that, I agree. | 08:48 |
| ViGe | pherjung: The official process is that if it's a real issue we will create a bug and comment on the forum, stating that an internal bug has been filed | 08:48 |
| ViGe | pherjung: So, if you don't see such a comment, you can pretty much assume internal bug hasn't been filed | 08:49 |
| flypig | I'd add, if a bug hasn't been filed, raising it here at the meeting like dcaliste did is a good way to increase visibility. | 08:50 |
| ViGe | the "tracked" thing wasn't just a tag in TJC, it had additional functionality as well. But I also think just having a "tracked" tag on the forum would be an improvement, even without the additional functionality. | 08:50 |
| flypig | We're bumping up against our time allocation. More time, or move on? | 08:51 |
| flypig | Okay, we move on then. | 08:52 |
| flypig | #topic Next meeting time and date (5 min) | 08:52 |
| *** sailbot changes topic to "Next meeting time and date (5 min) (Meeting topic: Sailfish OS, open source, collaboration -- 3rd February 2022)" | 08:52 | |
| flypig | Proposing Thursday 17th February at 08:00am UTC | 08:52 |
| flypig | 17th sound okay? | 08:52 |
| ExTechOp | OK | 08:53 |
| flypig | Okay, silence from everyone else implies acceptance :) | 08:53 |
| flypig | #info Next meeting will be held on Thursday 17th February 2022 at 08:00am UTC: 2022-02-17T0800Z | 08:53 |
| flypig | That's it for today. Thanks everyone for the nice suggestions and discussion. | 08:54 |
| flypig | #endmeeting | 08:54 |
| sailbot | Meeting ended Thu Feb 3 08:54:11 2022 UTC. | 08:54 |
| sailbot | Minutes: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2022/sailfishos-meeting.2022-02-03-08.00.html | 08:54 |
| sailbot | Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2022/sailfishos-meeting.2022-02-03-08.00.txt | 08:54 |
| sailbot | Log: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2022/sailfishos-meeting.2022-02-03-08.00.log.html | 08:54 |
| *** sailbot changes topic to "Next meeting will be held on Thursday 3rd February 2022 at 08:00am UTC. Topics can be made/read here: https://forum.sailfishos.org/t/community-meeting-on-irc-3rd-february-2022/10002" | 08:54 | |
| dcaliste | Thank you flypig for chairing today. | 08:55 |
| flypig | Thanks dcaliste, still finding my feet. | 08:56 |
| pherjung_ | you're doing a great job :) | 08:56 |
| flypig | Thanks :) sledges was very slick, I realise how tricky it is now! | 08:57 |
| *** ChanServ changes topic to "Next meeting will be held on Thursday 17th February 2022 at 08:00am UTC. Topics can be made/read here: https://forum.sailfishos.org/t/community-meeting-on-irc-17th-february-2022/10181" | 08:57 | |
| pherjung_ | Have a nice everybody! | 09:00 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!