SailfishOS, open source, collaboration meeting planning

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

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

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

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)

edit retag flag offensive close delete

Comments

7

Nice that you decided to move this here from the previous pad - I think TJC will serve well in this purpose also, also good to have many different topics under the same roof. Meetings might get new people too?

simo ( 2014-08-21 23:19:11 +0200 )edit

9

@cybette I wonder about the outcome of the action items 2 and 3 from the September 23th meeting:
> 2. Jolla to possibly spare some engineering time and fix up the proprietary bits to at least not crash and burn on SIP
> 3. cybette to poke SIP/dialer guys in Jolla
Unfortunately SIP is still not usable using the latest Jolla update.

alex25 ( 2014-10-28 08:46:46 +0200 )edit

bump. next meeting 7th Jan ?

kimmoli ( 2015-01-05 23:09:51 +0200 )edit

@kimmoli: yes

sledges ( 2015-01-06 16:49:45 +0200 )edit

4

@kimmoli @sledges thanks for the reminder. Sending email...

cybette ( 2015-01-06 16:54:55 +0200 )edit

69

answered 2015-05-18 14:21:50 +0200

coderus

22985 ●253 ●337 ●370

https://coderus.openrepos...

coderus
opensourcing and allowing to use jolla qml components
there are many cool proprietary qml components made by jolla: CameraExtensions, TextLinking, Email ComposerPage, Gallery ThumbnailImage/Video, Sailfish.Pickers (including allowing to use QtDocGallery), TransferEngine. It's always pain to develop applications using camera/email/gallery(filesystem)/thumbnailing, because every developer should implement own hacks for application and can't use native components. If it's not possible (please tell us why) then it will be great to have these components opensources so developer can compile and bundle it to application.
10 min +/- 5 min, really depends how fast jolla sailors can explain about current situation.
any jolla sailor responsible for qml components

edit flag offensive delete publish link

Comments

4

Thanks! added to agenda.

cybette ( 2015-05-18 15:20:01 +0200 )edit

1

Hi! With the question above, I want to draw the attention to the following points:

Despite the fact that QML components from jolla-... packages are covered by a proprietary license, they are de facto open source due to a) the content is easily accessible — it isn't encoded/obfuscated; b) they are handled as such by the community — there is Patchmanager with many patches available, the patches are publicly discussed, etc. The latter is the most important thing.
When a community patch, developed in a spirit of open-source collaboration, is adopted by the Jolla developers, it become again a part of the proprietary package in the commercial product. That isn't quite bad by itself because the community that have developed the patch don't yet lose anything. But really sad things might happen if Jolla (by any unpredictable reason) one day would decide to close the access to these QML files (by compilation, obfuscation, encoding, etc...). If that will happen, the already adopted community patches would be lost for the community, wasting out their efforts.

That's why I would like to encourage the Sailfish community developers to strongly ask Jolla to make their licensing policy consistent with the present situation: the QML files are developed in cooperation with the community, so there have to be a legal agreement, guaranteeing the results of that cooperative work to be always accessible for the community for further development.

Paul Wolneykien ( 2018-05-15 13:38:04 +0200 )edit

Book now young and Sensual Hyderabad Escorts.

Ashnai Mittal ( 2020-07-11 15:40:10 +0200 )edit

50

answered 2014-08-22 12:10:57 +0200

Nieldk

4562 ●40 ●70 ●76

nieldk: I would like to add a discussion on a feasable way to distribute a fastboot flashable base image to restore the phone if a 'brick' (or soft-brick if you prefer). Fx. Can we create a basic bootable image, withouth the binary blobs from Qualcom etc, that are not redistributable, to enable the phone to boot, or, provide some tool so that the user can generate a flashable image (fastboot) which can be restored. I have had the situation, with a dead battery, leaving the phone unable to charge and only able to enter fastboot. The phone was only again bootable because I had purchased an external charger, the phone would never charge enough with USB wall charger because of boot-loop.

edit flag offensive delete publish link

Comments

1

And if there are blobs without which device is "not really usable" maybe there would be enough mode to do OTA update after flashing? Basically it would boot to minimum to re-reflash OTA, so you distribute 3rd party parts exactly as with update

ZogG ( 2014-08-22 13:43:15 +0200 )edit

2

@Nieldk don't forget to introduce the topic with what have been done (sailfish-snapshot), what is needed (something to extract qualcomm drivers ? redistribuable parts ? fastboot image maker ?) from Jolla side and from community side.

Sfiet_Konstantin ( 2014-08-22 19:24:06 +0200 )edit

1

@Nieldk discussion proposal added. btw you can edit the wiki directly too :)

cybette ( 2014-08-26 08:40:34 +0200 )edit

29

answered 2015-09-11 16:36:57 +0200

bobsummerwill
451 ●2 ●4 ●5

Name / IRC nick : bobsummerwill

topic: Request more information on Roadmap for open-sourcing more of Sailfish.

some details about the topic: It has been mentioned on several occasions that there is a plan with regard to further open-sourcing of components within Sailfish. It would be great to have some more public information on that. In particular, the status of Silica is a constant 'sore point'. With the company split and the move towards licensing of Sailfish 2.0, perhaps there is an opportunity to restore some lost faith in Jolla with regard to licensing.

approx time needed: 20 mins

optional: name of substitute if you cannot make it to the upcoming meeting

edit flag offensive delete publish link

Comments

1

thanks @bobsummerwill, added to agenda above. will send email to devel list shortly.

cybette ( 2015-09-30 13:42:48 +0200 )edit

1

Just a reminder that this wasn't discussed after all last time, because Carsten Munk was the best person to answer, but was travelling at the time. Please can we be sure to add this to the November meeting? Thanks!

bobsummerwill ( 2015-10-22 00:13:15 +0200 )edit

1

Yep, part of the reason for schedule change is to make sure we have Carsten/someone to prepare some info for this topic at the next meeting. Thanks!

cybette ( 2015-10-22 13:32:41 +0200 )edit

1

Great - thanks!

bobsummerwill ( 2015-10-22 20:44:48 +0200 )edit

1

Just a reminder, @cybette, as per my reply to the mailing list that I likely will NOT be able to attend this Thursday's meeting in person, because it is at 6.30am in my timezone. I will try, but cannot promise. I am not needed. Please proceed without me. The question is on file and can be answered without me being there.

bobsummerwill ( 2015-11-17 23:02:14 +0200 )edit

19

answered 2017-05-03 11:45:32 +0200

leszek
10282 ●101 ●145 ●150

updated 2017-05-03 11:46:46 +0200

Name / IRC nick: leszek
topic: Sony Xperia X camera support full or limited (like AOSP driver) ?
some details about the topic: Sony
disables some camera features for
AOSP (some need proprietary stuff or patented stuff). Is SailfishOS on Xperia X getting the full support or only the AOSP support (which is pretty limited) ?
approx time needed: 5-10 mins

edit flag offensive delete publish link

Comments

The main reason I switch back from Sailfish to Android / LineageOS is camera support. Having good camera support would pull me over.

aerique ( 2020-05-26 17:14:19 +0200 )edit

16

answered 2015-11-19 19:09:59 +0200

bobsummerwill
451 ●2 ●4 ●5

Name / IRC nick : bobsummerwill topic: Explore options to decentralize Jolla, SailfishOS and Mer essential infrastructure - repositories, web-sites, automated build infrastructure, together.jolla.com, etc. Having any single individual or company solely responsible for such foundational infrastructure is a risk in any situation, let alone in the current situation. Backups are always good. Simplest case we would look to "copy". Better would be an ongoing multi-site "mirror". Best would be something truly decentralized based on IPFS as a long-term aim. approx time needed: 15 mins optional: name of substitute if you cannot make it to the upcoming meeting

edit flag offensive delete publish link

Comments

3

Thanks! Added to agenda.

cybette ( 2015-11-20 02:44:36 +0200 )edit

wow amazing topic

minojolla ( 2020-05-28 09:32:20 +0200 )edit

12

answered 2017-04-16 20:29:37 +0200

Toxip
3363 ●39 ●61 ●56

updated 2017-04-16 20:32:39 +0200

Name / IRC nick : bshah, toxip, mariogrip
Topic: Project Halium, collaboration on common android base
Description: Currently Ubuntu Touch, SailfishOS/Mer, Plasma Mobile and others have different android source trees and methods on how our stacks are built even though much of the underlying technologies are the same. There is a lot of unneeded fragmentation. Project Halium aims solve this by the having common android base and perhaps common middleware between different projects so that we could collaborate and distribute each of our resources more efficiently. More details about this project was sent to sailfishos devel list : http://lists.sailfishos.org/pipermail/devel/2017-April/007842.html
Approx time needed: 10-15 mins
Backup: (The whole Halium team will be there so no backup needed)

edit flag offensive delete publish link

11

answered 2014-08-22 10:32:39 +0200

ZogG
717 ●5 ●7 ●10

https://github.com/funkyc...

I would like to request to move those to later hours or/and preferably to weekends, as for most sailors it is part of their job/approved by bosses, I and, I think, most people also work at those hours and not at every job it would be acceptable to open IRC and even if so it would be irresponsible for me to concentrate on chat instead of work.

edit flag offensive delete publish link

Comments

1

You can always propose your topics in enough detail on the piratepad if there is some point you want to raise. Of course it would be nice if you could attend but at least you can make yourself heard if you put something on the piratepad.

Philippe De Swert ( 2014-08-22 12:34:22 +0200 )edit

3

Than there is no point at meetings at all, ah? As i wrote my concerns around internet already and I know few sailors saw them, in other words, RTC is different experience when you can "discuss".

ZogG ( 2014-08-22 13:39:16 +0200 )edit

1

You misunderstood my point. If for some reason you cannot unfortunately attend then there is still an option to get heard. And afaik the meetings are outside of working hours nowadays (starting at 15h UTC)

Philippe De Swert ( 2014-08-22 13:41:30 +0200 )edit

1

If you cannot attend an IRC meeting open a topic here in TJC. Most people there are also around here. There are more than one communication channels.

ApB ( 2014-08-22 13:50:35 +0200 )edit

3

@ZogG we alternate the meetings between 15UTC and 10UTC to try to accommodate participants from different time zones, from Australia to the Americas. You are welcome to propose a different time for a specific meeting if you have an agenda topic for the meeting!

cybette ( 2014-08-25 10:45:39 +0200 )edit

10

answered 2015-06-17 00:49:27 +0200

ljo
606 ●7 ●20 ●20

Please please make these one q per meeting in the same way we sailors are supposed to make qs per merged release. It is very hard to follow these answers on jolla in the chronological order which is the current default from what i can tell.

edit flag offensive delete publish link

Comments

4

ABSOLUTELY AGREE!! +10 This whole thread is a mess. I never know which topics are new and which are old without carefuly reading through the whole thing!

shfit ( 2015-06-17 12:32:24 +0200 )edit

10

answered 2017-02-14 21:32:24 +0200

pavi
1288 ●18 ●36 ●36

http://look-pavi.blogspot...

Name / IRC nick: pavi
Topic: Clarify and cleanup of Wiki's
Details about the topic

We have currently 2 Wikis, one is at https://wiki.merproject.org/ and the other is at https://sailfishos.org/wiki/ . This issue concerns the visiblity of three projects SailfishOS, Mer and Nemo. The three are related to Mer but the information in the wiki is

Too confusing
Repeated
Ambiguous
Written in wrong place
Outdated

So I hope some time is spent to discuss these issues. I am adding this to locusf topic above discussing Nemo. Please discuss this issue close to that topic.

Time Required: 20 minutes
backup:locusf

edit flag offensive delete publish link

Comments

ditto that, roll into one add category like Mer, Sailfish, Nemo, similar to Open Repos way of one website but with filter to screen out messages related to mer for example.

DarkTuring ( 2017-02-14 22:48:25 +0200 )edit

A similar idea that I had https://together.jolla.com/question/148537/structuring-together-jolla/ was posted long back. I some times feel we need some more structure. For example, it would be difficult to understand the topics to be discussed in the meeting as it carries all the topics in single thread. I feel that it would be better if a new thread is opened for each meeting with pointer to older meetings (if required) would be good for following threads. Similarly lots of things.

walkingzen ( 2018-02-15 11:36:33 +0200 )edit

10

answered 2017-07-17 00:43:35 +0200

adamski
111 ●2 ●4 ●6

updated 2017-07-17 00:44:17 +0200

Name / IRC nick: adamski

topic: Jolla Harbour paid apps

some details about the topic: What is holding things up regarding paid apps and IAP on Jolla Harbour?

approx time needed: 3 mins

edit flag offensive delete publish link

Comments

Edit first post and add your topic there

atlochowski ( 2017-07-17 09:38:30 +0200 )edit

2

OK, I see, however I am a new user on here and don't have enough karma points to edit wiki posts. Thanks

adamski ( 2017-07-17 12:16:14 +0200 )edit

1

@adamski I've added that for you, welcome :)

r0kk3rz ( 2017-07-17 15:24:36 +0200 )edit

SailfishOS, open source, collaboration meeting planning

Comments

61 Answers

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

SailfishOS, open source, collaboration meeting planning

Comments

61 Answers

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions