08:00:11 <rainemak> #startmeeting Sailfish OS, open source, collaboration -- 28th November 2024
08:00:11 <sailbot> Meeting started Thu Nov 28 08:00:11 2024 UTC. The chair is rainemak. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:11 <sailbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:00:19 <rainemak> #info Meeting information and agenda can be found here:
08:00:19 <rainemak> #link https://forum.sailfishos.org/t/community-meeting-on-28th-november-2024/21050
08:00:19 <rainemak> I 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:19 <rainemak> #topic Brief introduction (5 min). Please prefix your name/handle with #info
08:00:23 <ViGe> morning
08:00:59 <rainemak> #info Raine Mäkeläinen, Jolla
08:01:02 <ViGe> #info Ville Nummela, community
08:01:06 <tuplasuhveli[m]> #info tuplasuhveli, community
08:01:09 <pvuorela> #info Pekka Vuorela, Jolla
08:01:16 <tuplasuhveli[m]> Good morning all!
08:01:26 <rainemak> Good morning!
08:01:27 <abr> #info Andrew Branson, Sailing by
08:01:33 <Crabster> #info Crabster - lurker
08:01:49 <arisel> #info arisel, community
08:02:33 <rainemak> We have 3 topics today so we should also time for general discussion
08:04:48 <rainemak> let's get going
08:05:03 <rainemak> #topic bluetooth/ble support for android apps (5 mins -- asked by arisel)
08:05:18 <rainemak> A question from the previous meeting
08:05:26 <rainemak> #link https://forum.sailfishos.org/t/community-meeting-on-28th-november-2024/21050/2
08:05:26 <rainemak> #info <Jolla> Too long question to be pasted here. Hence, above link.
08:05:42 <rainemak> good morning flypig and daiboiade as well
08:05:53 <flypig> Morning! Sorry for being late.
08:05:59 <rainemak> no worry
08:06:03 <flypig> #info David Lllewellyn-Jones, community
08:06:31 <daiboiade> good morning everyone
08:06:36 <rainemak> #info <Jolla> You can be rest assured that we are also aware of current limitations.
08:06:36 <rainemak> #info <Jolla> We certainly want to have bluetooth support for AppSupport, it is not
08:06:36 <rainemak> #info <Jolla> about that, and we have some novel ideas regarding this.
08:07:15 <daiboiade> #info daiboade, community member
08:07:33 <rainemak> Having bt support for AppSupport would certainly unlock use cases
08:08:20 <arisel> rainemak: do you have any ideas on prioritization, or on which way you might most possibly be following / evaluating?
08:09:19 <arisel> rainemak: also: my Q was a bit about being able to find an information you just posted, somewhat more publicy. So: will there be any statement in the forum, maybe?
08:11:10 <rainemak> arisel, some decision making needed first. I'll try to get above copy-pasted to the forum as well on a topic xyz
08:11:48 <rainemak> arisel, for time being I guess this is satisfying answer :-)
08:12:08 <rainemak> let's move on
08:12:16 <rainemak> #topic More generic features enabled in kernel configs  (5 mins -- asked by nephros)
08:12:22 <rainemak> #info <nephros> I’d like to raise awareness for this feature request, maybe for
08:12:22 <rainemak> #info <nephros> SFOS5 we could get a couple of the more desktop-y kernel functions
08:12:22 <rainemak> #info <nephros> enabled?
08:12:23 <rainemak> #info <nephros> My personal wish would be filesystems like NFS, CIFS and UDF, but
08:12:23 <rainemak> #info <nephros> there are some other requests in the linked topic.
08:12:23 <rainemak> #info <nephros> Where would a “formal” request with specific features have to be
08:12:25 <rainemak> #info <nephros> directed? mer-hybris/mer-kernel-check? Somewhere else?
08:12:28 <rainemak> #link https://github.com/mer-hybris/mer-kernel-check/
08:12:35 <rainemak> #info <Jolla> You are right. The mer-hybris/mer-kernel-check is the right place to
08:12:37 <rainemak> #info <Jolla> look at. Opening a PR is a good way to start discussion regarding
08:12:39 <rainemak> #info <Jolla> needed kernel options.
08:13:07 <arisel> rainemak: ty! (and knowing that you aim for that is nice!)
08:15:19 <rainemak> #topic Jolla C2 adaptation repos and source code (5 mins asked by nephros)
08:15:26 <rainemak> #info <nephros> This is a bit of a Folllow-up question to an older one forum topic
08:15:26 <rainemak> #info <nephros> meeting log: The answer to the earlier question was: Opening up
08:15:26 <rainemak> #info <nephros> adaptation sources got J Tablet and JollaC (one) was “are tricky as
08:15:26 <rainemak> #info <nephros> there were some proprietary sources”.
08:15:26 <rainemak> #info <nephros> Will such components be made available for the C2 device?
08:15:27 <rainemak> #info <nephros> Also, as noted here, open source tarballs are not currently
08:15:29 <rainemak> #info <nephros> available e.g. at Index of /sources/. Will these be available? If
08:15:33 <rainemak> #info <nephros> so, when?
08:15:35 <rainemak> #info <nephros> Do users who want to have access to e.g. the GPLv2 kernel sources,
08:15:37 <rainemak> #info <nephros> indeed have to put that as a written request to Jolla, as noted in
08:15:39 <rainemak> #info <nephros> the Sailfish OS License Terms?
08:15:41 <rainemak> #link https://forum.sailfishos.org/t/community-meeting-on-14th-march-2024/18132/8
08:15:43 <rainemak> #link https://forum.sailfishos.org/t/jolla-c2-open-source-code/20959
08:15:45 <rainemak> #link http://releases.sailfishos.org/sources/
08:15:47 <rainemak> #info <Jolla> Current adaptation build process for C2 is complex making also OBS
08:15:49 <rainemak> #info <Jolla> building difficult. That is making source code publishing to Index
08:15:51 <rainemak> #info <Jolla> of /sources/ also difficult. There are tons of topics to be sorted
08:15:53 <rainemak> #info <Jolla> out. No schedule promises at this point.
08:19:01 <flypig> Is it just a technical difficulty (i.e. not legal or something else)?
08:19:16 <flypig> (I'm refering to the difficulty of building on OBS).
08:21:25 <rainemak> I'd say mostly technical difficulty
08:22:02 <flypig> Okay, thank you! It sounded like that from the way you described it, but I just wanted to make sure.
08:22:23 <rainemak> time to move on
08:22:29 <rainemak> #topic Open PR discussion (5 mins -- asked by Jolla)
08:27:25 <rainemak> Seems that none today. Maybe on next meeting.
08:27:28 <rainemak> #topic General discussion (10 mins)
08:27:44 <flypig> A quick question about the kernel modules, as I'm clueless on the topic. How easy or hard is it to change these settings? Is it just a case of changing the value in the "mer_verify_kernel_config" file, or is it much more infolved than that?
08:29:39 <ViGe> I'm as clueless, but "mer_verify_kernel_config" sounds like something that just verifies the config instead of actually creating the config
08:29:54 <flypig> Yes, it does rather, doesn't it.
08:30:51 <abr> but getting something added to that would mean that all adaptations including ports would be strongly encouraged to add it to their kernel configs.
08:30:55 <ViGe> Personally, I would like to see midi sequencer enabled in the config, but as I'm probably the only one I'm not going to even suggest it to be added :-D
08:31:04 <abr> of course there's nothing stopping them adding extra configs anyway
08:31:23 <flypig> ViGe, I think poetaster asks for something similar in the forum thread?
08:31:25 <arisel> ViGe: +1 ;))
08:32:18 <flypig> So, abr, the idea is that by getting it added there, warnings will be thrown up somewhere else that'll provoke the actual work needed (which, I suppose, could be considerable)?
08:33:16 <abr> I don't think there's much extra work needed. There's nothing more to do than change the config file and make sure the kernel still works.
08:34:03 <flypig> abr, thanks, that's interesting. I guess you still have to compile the kernel, which is no small task in itself.
08:34:12 <abr> But I don't think it's feasible to enable absolutely everything. There has to be a line somewhere. Else the kernel might end up too big and maybe even unstable.
08:35:08 <flypig> But for someone really keen to have a specific feature, it sounds like they could do it themselves and try it out?
08:35:34 <abr> iiuc adding the the kernel-check won't really get older adaptations updated either. just new ones. to add stuff to those you can create a PR on the repo (in the case of the xperias or other public adaptations)
08:36:00 <abr> building kernels isn't easy iirc. pretty serious HADK.
08:36:57 <flypig> Thanks abr, I find this really helpful for perspective.
08:37:18 <rainemak> very good discussion indeed
08:37:25 <abr> Hope I know what I'm talking about :D
08:38:21 <flypig> You always know what you're talking about! :)
08:39:11 <abr> no i just sound like I do :P
08:41:01 <rainemak> yeah, right :-)
08:41:30 <rainemak> let's schedule next meeting
08:41:38 <rainemak> #topic Next meeting time and date (5 min)
08:41:55 <rainemak> Proposing Thursday 12th December at 08:00am UTC
08:42:22 <flypig> No objection here!
08:42:25 <abr> btw, here's how bt tethering was enabled recently in the xperia kernels: https://github.com/mer-hybris/android_kernel_sony_msm/pull/137/files
08:42:40 <abr> +1
08:43:10 <flypig> Nice, thanks abr! That looks pretty straightforward... as long as you know what you're doing.
08:43:26 <abr> yeah the tough bit is the building and testing
08:43:57 <rainemak> #info Next meeting will be held on Thursday 12th December 2024 at 08:00am UTC: 2024-12-12T0800Z
08:44:32 <flypig> It looks like we're heading for a meeting on Boxing day ;)
08:44:47 <rainemak> Thank you everybody! Once again a very good meeting and nice to see some new nicknames.
08:45:19 <rainemak> flypig, let's try to avoid that Dec 26 / Boxing Day collision
08:45:27 <flypig> Yes please :)
08:46:15 <rainemak> I guess we'll just skip that continue 2nd Jan 2025
08:46:33 <rainemak> ^ but that's to be decided on the next meeting
08:46:49 <rainemak> I guess we'll just skip that and continue 2nd Jan 2025
08:47:08 <rainemak> that's it for today
08:47:11 <rainemak> thanks
08:47:30 <rainemak> #endmeeting