=============================================================================
#sailfishos-meeting: Sailfish OS, open source, collaboration -- 28th Sep 2023
=============================================================================


Meeting started by rainemak at 07:00:06 UTC. The full logs are available
at
https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2023/sailfishos-meeting.2023-09-28-07.00.log.html
.



Meeting summary
---------------
* Meeting information and agenda can be found here:  (rainemak,
  07:00:15)
* LINK:
  https://forum.sailfishos.org/t/community-meeting-on-irc-28th-september-2023/16726
  (rainemak, 07:00:20)
* Brief introduction (5 min). Please prefix your name/handle with #info
  (rainemak, 07:00:32)
  * Raine Mäkeläinen, sailor @ Jolla, chairperson today  (rainemak,
    07:01:22)
  * Otto Mäkelä, community  (ExTechOp, 07:01:33)
  * @poetaster, Mark Washeim, community  (poetaster, 07:01:54)
  * Crabster - lurker  (Crabster, 07:02:15)
  * Damien Caliste, community  (dcaliste, 07:03:57)

* Notification popups in lipstick (10mins -- asked by thigg)  (rainemak,
  07:05:41)
  * <thigg> Sometimes (especially when using android apps)  (rainemak,
    07:05:52)
  * <thigg> notifications are hiding other ui elements (forum:
    Notifications hiding buttons).  (rainemak, 07:05:52)
  * <thigg> My idea to handle this was to mute notifications for some
    time (30s) if the  (rainemak, 07:05:52)
  * <thigg> notification is swiped to the left. After 30s a notification
    is shown that  (rainemak, 07:05:52)
  * <thigg> notifications are enabled again and the notifications from
    the queue are shown.  (rainemak, 07:05:52)
  * <thigg>  (rainemak, 07:05:54)
  * <thigg> This looks quite simple to implement at
    https://github.com/nemomobile-ux/lipstick/blob/e6e336f4c7e190f8c24802cc1337efa39be7bf93/src/notifications/notificationpreviewpresenter.cpp#L88
    (rainemak, 07:05:55)
  * <thigg> by returning early if the current time is <= the time in a
    muted_until value  (rainemak, 07:05:58)
  * <thigg> and patching the notification popup Notifications hiding
    buttons - #6 by thigg.  (rainemak, 07:06:00)
  * <thigg> When the notifications are muted, a timer is started which
    fires a “notifications  (rainemak, 07:06:02)
  * <thigg> enabled” notification after the mute period and this would
    trigger the appearance  (rainemak, 07:06:05)
  * <thigg> of all other notifications. And probably a dbus interface
    for lipstick to set muted_until  (rainemak, 07:06:10)
  * <thigg> from the popup.  (rainemak, 07:06:13)
  * <thigg>  (rainemak, 07:06:15)
  * <thigg> Because modifications to lipstick are hard (impossible?) to
    deliver to users,  (rainemak, 07:06:17)
  * <thigg> collaboration with jolla would be helpful. At least the
    dbus- interface to set  (rainemak, 07:06:19)
  * <thigg> muted_until would have to be done by jolla.  (rainemak,
    07:06:21)
  * <thigg>  (rainemak, 07:06:23)
  * <thigg> I’d like to discuss the problem, this proposed workaround
    and if jolla is willing to  (rainemak, 07:06:25)
  * <thigg> collaborate on this (or even do it on their own)  (rainemak,
    07:06:28)
  * LINK:
    https://forum.sailfishos.org/t/notifications-hiding-buttons/16717
    (rainemak, 07:06:30)
  * LINK:
    https://github.com/nemomobile-ux/lipstick/blob/e6e336f4c7e190f8c24802cc1337efa39be7bf93/src/notifications/notificationpreviewpresenter.cpp#L88
    (rainemak, 07:06:32)
  * <Jolla> Thank you thigg! This is a very good and interesting topic.
    This is indeed  (rainemak, 07:06:57)
  * <Jolla> something occasionally annoys users. One idea that was
    brought up could be  (rainemak, 07:06:57)
  * <Jolla> using similar adaptive mechanisms that is used for display
    dimming. For example,  (rainemak, 07:06:57)
  * <Jolla> it could be so that first notification that is dismissed by
    swipe could suppress  (rainemak, 07:06:57)
  * <Jolla> notification queue for 5sec, next new notification that is
    dismissed by swipe  (rainemak, 07:06:57)
  * <Jolla> would prolong suppress to 10sec, and so on.  (rainemak,
    07:06:58)
  * <Jolla>  (rainemak, 07:07:05)
  * <Jolla> Related to this, one problematic app category is navigation
    apps as those might start  (rainemak, 07:07:05)
  * <Jolla> showing notifications from your route and those might be
    triggered too frequently.  (rainemak, 07:07:05)
  * <Jolla> In this kind of scenario, one might want to have
    notification suppressed completely  (rainemak, 07:07:10)
  * <Jolla> from the app that spams notifications. Worth exploring
    whether this kind of action  (rainemak, 07:07:13)
  * <Jolla> could be visible by default.  (rainemak, 07:07:16)

* Guidance about maintaining an HADK-faq wiki page (5mins -- asked by
  poetaster)  (rainemak, 07:21:32)
  * <poetaster> In the main, a number of porters have mentioned the
    difficulty in  (rainemak, 07:21:32)
  * <poetaster> working on the HADK docs. And ad-hoc etherpad is the
    present hacking  (rainemak, 07:21:32)
  * <poetaster> approach. To get the more structured I created HADK |
    SailfishOS community  (rainemak, 07:21:32)
  * <poetaster> wiki 4 This contains a dump of the etherpad and a first
    transfer of the faq  (rainemak, 07:21:32)
  * <poetaster> PDF to a wiki page. This is far from ideal. Is source
    for the pdf available  (rainemak, 07:21:34)
  * <poetaster> or is it a classic ‘word like’ document?  (rainemak,
    07:21:35)
  * LINK: https://sailfishos.wiki/books/hadk   (rainemak, 07:21:37)
  * <Jolla> Thank you for asking. Which ad-hoc etherpad you’re referring
    to? We moved  (rainemak, 07:22:03)
  * <Jolla> http://piratepad.net/hadk-faq-v2 content to
    https://github.com/mer-hybris/hadk-faq  (rainemak, 07:22:04)
  * <Jolla> some time back already. Intention there is that hadk-faq
    would be used wiki like  (rainemak, 07:22:04)
  * <Jolla> and people would create PRs to it.  (rainemak, 07:22:04)
  * <Jolla>  (rainemak, 07:22:04)
  * <Jolla> HADK is not a word document rather a set of rst from which
    pdf is generated.  (rainemak, 07:22:05)
  * David Llewellyn-Jones, community, latecomer  (flypig, 07:26:04)

* Open PR discussion (10 mins -- asked by jolla)  (rainemak, 07:30:01)
  * <Jolla> Any other open PRs to discuss?  (rainemak, 07:30:08)
  * LINK: https://github.com/sailfishos/gcc/pull/4   (rainemak,
    07:32:12)

* Untracked bug reports (5 min -- asked by pherjung)  (rainemak,
  07:41:44)

* Untracked bug reports (5 min -- asked by pherjung)  (rainemak,
  07:41:53)
  * <pherjung> Untracked bug reports  (rainemak, 07:41:53)
  * LINK:
    https://forum.sailfishos.org/t/community-meeting-on-irc-14th-september-2023/16646/3
    (rainemak, 07:41:53)
  * <Jolla> The Community Bug Coordination Team have done a superb job
    once again this fortnight.  (rainemak, 07:41:53)
  * <Jolla> 10 high quality bugs reported. Most of them are/will be
    recorded internally.  (rainemak, 07:41:53)
  * <Jolla> Tracker flags are missing from the forum.  (rainemak,
    07:41:55)

* General discussion (5 min)  (rainemak, 07:46:31)
  * LINK:
    https://codereview.qt-project.org/c/qt-labs/messagingframework/+/507382
    (flypig, 07:56:01)
  * LINK:
    https://codereview.qt-project.org/c/qt-labs/messagingframework/+/507382
    (rainemak, 07:56:44)
  * <dcaliste> Switching QCop to D-Bus for IPC ^  (rainemak, 07:58:09)

* Next meeting time and date (1 min)  (rainemak, 07:59:18)
  * Next meeting will be held on Thursday 12th October 2023 at 07:00am
    UTC: 2023-10-12T0700Z  (rainemak, 07:59:50)

Meeting ended at 08:00:22 UTC.




Action Items
------------





Action Items, by person
-----------------------
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* rainemak (120)
* flypig (24)
* poetaster (16)
* dcaliste (15)
* ExTechOp (4)
* sailbot (2)
* Crabster (2)
* Nico (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot