#sailfishos-meeting: Sailfish OS, open source, collaboration -- 31st March 2022
Meeting started by flypig at 07:00:19 UTC
(full logs).
Meeting summary
-
- Meeting information and agenda can be found
here: (flypig,
07:00:27)
- https://forum.sailfishos.org/t/community-meeting-on-irc-31st-march-2022/10714
(flypig,
07:00:31)
- Brief introduction (5 min). Please prefix your name/handle with #info (flypig, 07:00:44)
- thigg - community dev (thilo[m],
07:01:41)
- David Llewellyn-Jones - sailor@jolla
(flypig,
07:01:56)
- lolek - just a regular user (lolek,
07:01:56)
- pherjung - community (pherjung,
07:02:01)
- Björn Bidar - Sailor@Jolla (Thaodan,
07:02:08)
- Otto Mäkelä - community (ExTechOp,
07:02:16)
- Eric Ric9k - user (Ric9k,
07:03:41)
- Andrew Branson - sailor (abr,
07:03:44)
- Simonas Leleiva - privateer (sledges,
07:05:37)
- Sebix - community member (sebix[m],
07:06:02)
- Better tracking of bug report (15 min -- asked by pherjung) (flypig, 07:06:50)
- <pherjung> I noticed some bug report
written by the community on the forum are not always followed up by
Jolla and only become tracked so once they mentioned in a community
meeting. (flypig,
07:06:56)
- <pherjung> Couldn't a system like the
translation one be set up? Some members of the community implicated
in the community could act as bridge with Jolla. (flypig,
07:07:04)
- <pherjung> So various member could be in
charge to verify bug reports, test them, get more information if
necessary and ping Jolla to fill up a bug report on their own bug
tracking system. (flypig,
07:07:12)
- <pherjung> Or even easier, these people
could have access to Jolla's bug tracking system. (flypig,
07:07:20)
- <Jolla> We do our best to keep track and
follow up on bug reports noted on the forum, and the fact we
addressed at least 33 bugs reported this way in the 4.4.0 release is
a good sign. (flypig,
07:07:54)
- <Jolla> However, you're right that we
could improve the process, and more support from the community would
help. (flypig,
07:08:02)
- <Jolla> As a proposal, would you,
pherjung, be willing to take a lead on this? Initially, one way to
proceed would be for you to provide a list of bugs at the next
community meeting that aren't tracked, but which are well-formed
enough for us to log internally? (flypig,
07:08:14)
- <Jolla> Minimum requirements would be
that the bug is in the correct format, with a clear description,
clear version info, and with steps to reproduce it. (flypig,
07:08:24)
- <Jolla> If this works out, we can look to
refine the process. (flypig,
07:08:30)
- <thilo[m]> thus I identify the task as:
get all bug reports, filter already tracked, filter non well
formed (flypig,
07:15:16)
- piggz, community, late to the party
(piggz,
07:16:16)
- Damien Caliste, community (dcaliste,
07:17:32)
- Carmen F.B. sfos user (cfb014,
07:21:45)
- ACTION: flypig to
look into a "Bug noted for meeting" tag. (flypig,
07:22:16)
- ACTION: flypig to
look into forum tag permissions. (flypig,
07:31:35)
- Decided process: "encourage people to split out
their bugs into a separate report and tag bug reports that are
well-formed. For a meeting a list is compiled from the tagged ones.
After the meeting all processed bug reports a re linked to the
meeting. Is that correct?" (flypig,
07:33:26)
- thilo[m] and pherjung will coordinate.
(flypig,
07:33:30)
- What's Jolla's position on financial participation in the company? (15 min -- asked by pherjung) (flypig, 07:34:04)
- <pherjung> Some users would be interested
to invest in the company. (flypig,
07:34:11)
- <pherjung> See this topic:
https://forum.sailfishos.org/t/interest-to-create-a-cooperative/10799
(flypig,
07:34:17)
- https://forum.sailfishos.org/t/interest-to-create-a-cooperative/10799
(flypig,
07:34:21)
- <pherjung> Another possibility would be
for the community to fund features. (flypig,
07:34:24)
- <Jolla> Thank you for your question, it's
great to see that the community is so willing to engage with Jolla.
We have taken the matter to top management for consideration.
(flypig,
07:34:39)
- <Jolla> However, we are not able to move
further with this issue until the new ownership structure of Jolla
has been resolved on a wider scale and we have a clearer view of the
future. (flypig,
07:34:46)
- BlackBerry picture password license (10 min -- asked by lolek) (flypig, 07:51:32)
- <lolek> on previous meeting I got
informed that Jolla is unable to implement picture password like the
one from BBOS10 because BlackBerry has patent on it. (flypig,
07:51:46)
- <lolek> So my question is if maybe it
would be possible to get this type of a lock as a paid option as
part of Sailfish license? (flypig,
07:51:51)
- <lolek> Then maybe it would be possible
to just pay the fee to BB for this but at least a decent and a
secure lock screen would be available. (flypig,
07:51:56)
- <lolek> If it's for me, this would be a
key point to finally buy an SFOS license cause right now I see no
point in doing so. (flypig,
07:52:03)
- <lolek> BB is no longer manufacturing any
phones not any other company for them from what I understand, so
maybe it's worth asking them? (flypig,
07:52:10)
- <lolek> More info:
https://forum.sailfishos.org/t/community-meeting-on-irc-20th-january-2022/9549/4?u=lolek
(flypig,
07:52:14)
- https://forum.sailfishos.org/t/community-meeting-on-irc-20th-january-2022/9549/4?u=lolek
(flypig,
07:52:17)
- <Jolla> Thanks for raising this issue
again. We're still open to exploring good alternatives, but as we
mentioned last time, an important consideration is that any
alternative must fit with the existing authentication components and
UI. (flypig,
07:52:38)
- <Jolla> So making any change like this
requires a great deal of care. (flypig,
07:52:44)
- <Jolla> Our feeling is that our focus
would be more usefully spent on providing a better mechanism in the
OS for installing additional authentication methods and letting
users choose what they prefer. (flypig,
07:52:49)
- <Jolla> This would then allow a
third-party developer to implement the picture password
approach. (flypig,
07:52:54)
- <Jolla> Nevertheless we of course welcome
discussion on the topic. (flypig,
07:52:59)
- <pherjung> "coderus wrote a patch
implemeting an alternative. It doesn't work anymore" (flypig,
08:02:08)
- https://github.com/CODeRUS/sailfishos-mazelock-patch
(flypig,
08:02:16)
- <dcalsite> "not that I volunteer to do
it, my todo list is alreday full ;) But that could be a nice
exercice for interested community devs" (flypig,
08:05:33)
- General discussion (15 min) (flypig, 08:06:19)
- thilo[m] created the a post in relation to the
community bug coordination. (flypig,
08:17:39)
- https://forum.sailfishos.org/t/new-role-community-bug-coordinator/10935
(flypig,
08:17:46)
- Next meeting time and date (5 min) (flypig, 08:23:32)
- Next meeting will be held on Thursday 14th
April 2022 at 07:00am UTC: 2022-04-14T0700Z (flypig,
08:26:41)
Meeting ended at 08:27:00 UTC
(full logs).
Action items
- flypig to look into a "Bug noted for meeting" tag.
- flypig to look into forum tag permissions.
Action items, by person
- flypig
- flypig to look into a "Bug noted for meeting" tag.
- flypig to look into forum tag permissions.
People present (lines said)
- flypig (118)
- thilo[m] (43)
- pherjung (29)
- lolek (20)
- Thaodan (13)
- sebix[m] (13)
- dcaliste (12)
- ExTechOp (9)
- cfb014 (8)
- abr (6)
- Ric9k (5)
- sledges (3)
- johnny (3)
- sailbot (2)
- piggz (1)
Generated by MeetBot 0.1.4.