Nope, I am not interested in participating at Jolla’s “IRC community meetings” at all:
- Jolla clearly stated that this forum (FSO) is the location to discuss issues, bugs, etc. It was their reasoning that hence they switched off most issue trackers of their source code repositories at GitHub and formerly at Jolla’s own GitLab instance (which is not reasonable IMO, because filing an issue for a specific component by a developer is vastly different from the character of issue reports in this forum).
- These “IRC community meetings” appear to be a measure to create just another hurdle (i.e., gate) by enforcing synchronous communication at an inappropriate time for most, by requiring to be willing and able to “speed-type”, etc., so Jolla can and already did easily claim, “this was not presented at a ‘community meeting’” rsp. “this must be presented at a ‘community meeting’” for issues well documented in this forum or at GitHub, and then ignore them.
- Looking at Jolla’s usual responses at “IRC community meetings”, the whole process is a waste of effort and time: “We will look into it” to be never mentioned again, “We cannot answer this”, “We may consider this” to be never mentioned again, “Currently we have no plan to address this” are the regular “answers”.
As stated in the issue thread, this issue is at least 7 years old, was reported multiple times at TJC, has been silently addressed by Jolla at least once (which alleviated it a bit, but never really resolved it), while never acknowledging it.
Jolla’s policy always was and still is to be absolutely closed up and to stay mum (contentually, for both technical as well as business aspects), plus I see no indication for this to change. If Jolla would, e.g., allow read access to their internal bug tracker, or report openly that they recently have been becoming bankrupt (or close to that) another time and how this was resolved, then I will believe that Jolla is trying to do better; until then all these efforts are more or less futile.
P.S.: In the light of Jolla’s recurring economic (close) failures, I also expect Jolla to commit themselves legally binding and publicly to release all proprietary components which comprise SailfishOS (i.e., all but Alien Dalvik aka “AAS”: Silica, Lipstick, etc.), in order to enable the community to continue development of SailfishOS, in case Jolla ultimately fails economically; until then it makes more sense for community developers to spend efforts and time on FLOSS software which runs independently of SailfishOS, because such work is implicitly sustainable.