SailfishOS, open source, collaboration meeting planning

asked 2014-08-21 22:22:21 +0300

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2020-08-16 23:56:33 +0300

Sefriol
826 ●9 ●12 ●16

Next meeting on IRC:Thursday6th of Aug 2020 at 08:00 UTC. The meeting will be held on Freenode IRC, #sailifshos-meeting ( https://webchat.freenode.net/?channels=#sailfishos-meeting )

Check here for your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Sailfish+OS+community+collaboration+meeting&iso=20200806T08&p1=1440

Logs of previous meetings: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2020/

Meeting logs before March of 2020: http://merproject.org/meetings/mer-meeting/

Tasks assigned during the meetings: http://meetingwords.com/sailfishos-community-irc

• add your name/nick using the template below to suggest a topic.
• indicate how much time you will need for the topic so we can timebox the meeting accordingly
• please be as thorough as you can with your question/topic
• if you can't make the meeting please ask and then name a substitute who can in your place.

It is expected that you show up and present your topic, or name a substitute and make sure they attend in your absence. These IRC meetings are for real time participation and live discussions, otherwise you can post the topic on here on TJC or on the mailing list and get responses that way.

We need you to be present to clarify details in the topic, and to ensure the discussion is leading to the answers you are looking for! If you do not participate or your question/topic isn't clear enough it will be postponed. Also: Always ask for *more time than you anticipate your topics needs!!*

Please try and have your topics ready by at least 3 days before the meeting. This will help us have answers ready beforehand to save time. Topics announced afterwards will be postponed to the next meeting.

Template for topic proposal: (edit this wiki directly to add your topics)

• Name / IRC nick:
• topic:
• some details about the topic:
• approx time needed:
• optional: name of substitute if you cannot make it to the upcoming meeting (and inform your substitute!)

Agenda/topics:

• Name / IRC nick: rinigus
• topic: AOSP10 based ports
• some details about the topic: From looking at https://github.com/libhybris/libhybris and Android Q PR specifically, it seems that there is not much activity on development of Android 10 support. I wonder what is the current status of AOSP10 support (in case if it is not all published). If work has not started on it by Jolla developers, whether it is planned and, if it is, when do you plan to work on it.
• approx time needed: 20 min
• optional: I hope to make it; if not, please discuss with others

• Name / IRC nick: Sefriol
• topic: E2E testing in Sailfish
• some details about the topic: E2E testing is one of the key aspects to make reliable and tested software, most popular (or atleast user friendly) webapp testers being Cypress.io. There seems to be little to no E2E testing capabilities provided as a base line or atleast the documentation is very limited. I stumbled upon https://www.researchgate.net/publication/320649391_Method_and_tools_for_automated_end-to-end_testing_of_applications_for_sailfish_OS and https://bitbucket.org/yarfruct/sailfish-os-qml-test-runner/src/default/ which provide some solutions. Is there anything that Jolla uses internally? I would assume that e2e frameworks would also be useful for porters who could more rapidly test out that certain functions do work when porting OS to another SoC or phone.
• approx time needed: 10 min
• optional: I hope to make it; if not, please discuss with others

• Name / IRC nick: Mister_Magister
• topic: Multiple 2+ cameras support
• some details about the topic: Lately i've successfuly created initial support of multi-camera. On some devices auxiliary cameras are provided same way as other 2 but sfos is based around front and back camera while we need to support camera id 2 and higher. My initial changes are nowhere near merging, it needs to be done properly but it's something jolla should start think about regarding jolla-camera ui.
• approx time needed: 15 min
• optional: I hope to make it; if not, please discuss with others

• Name / IRC nick: Sefriol
• topic: Native Banking Apps for SailfishOS
• some details about the topic: Currently, you are pretty much required to have a second device if your bank only allows SafetyNet passing devices to run as credential client. VTB24 seems to have an closed source banking app for AuroraOS. Any insight from Jolla's side if there is any posssible progress in bringing native banking apps to Sailfish. https://together.jolla.com/question/11734/mobilebanking/
• approx time needed: 10 min
• optional: I hope to make it; if not, please discuss with others

• Name / IRC nick: Sefriol
• topic: Separating QML components from closed source and publishing them to git
• some details about the topic: This has come up before. Currently, if community sees a bug or wants to propose a change in core app's UI, the source is only available within the phone / emulator / SDK. Is there a problem with separating these components from the closed source repositories and publishing them in gitso that community could do pull requests on them?
• approx time needed: 5 min
• optional: I hope to make it; if not, please discuss with others

For background info and invitation to this series of meetings, please see this post. Past meeting minutes, list of action points and further information are here, more recent minutes are here

Meeting Chair: (volunteers, suggestions,nominations...)

Responsibilities of meeting chair: send invitation/agenda before the meeting, keep time and order during the meeting, send minutes and next meeting planning info after the meeting.

• James Noori (Jaymzz)
• Simonas Leleiva (Sledges)
• Steph Gosling (stephg)
• Carol Chen (cybette)
• Andrew Branson (abranson)
• (your name here)