We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2017-09-20 14:36:35 +0200

Damien Caliste gravatar image

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. For those interested, most of the sources are openly available in MER gitlab and the SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though.

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.

The list of closed source parts are presented as answers to this post so one can vote. Please feel free to amend this post or the list and create new answers as wiki also so one can modify or add contributions.

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. For those interested, most of the sources are openly available in MER gitlab and the SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though.

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.

The list of closed source parts are presented as answers to this post so one can vote. Please feel free to amend this post or the list and create new answers as wiki also so one can modify or add contributions.

To be also constructive, here is a list of open source contributions from community thanks to OSS parts:

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. For those interested, most of the sources are openly available in MER gitlab and the SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though.

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.

The list of closed source parts are presented as answers to this post so one can vote. Please feel free to amend this post or the list and create new answers as wiki also so one can modify or add contributions.

To be also constructive, here is a list of open source contributions from community thanks to OSS parts:

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. For those interested, most of the sources are openly available in MER gitlab and the SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though.

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.

The list of closed source parts are presented as answers to this post so one can vote. Please feel free to amend this post or the list and create new answers as wiki also so one can modify or add contributions.

To be also constructive, here is a list of open source contributions from community thanks to OSS parts:

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. For those interested, most of the sources are openly available in MER gitlab and the SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though.

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.

The list of closed source parts are presented as answers to this post so one can vote. Please feel free to amend this post or the list and create new answers as wiki also so one can modify or add contributions.

To be also constructive, here is a list of open source contributions from community thanks to OSS parts:

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. For those interested, most of the sources are openly available in MER gitlab and the SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though.though, see the wiki entry (feel free to update this list by the way).

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.

The list of closed source parts are presented as answers to this post so one can vote. Please feel free to amend this post or the list and create new answers as wiki also so one can modify or add contributions.

To be also constructive, here is a list of open source contributions from community thanks to OSS parts:

click to hide/show revision 7
No.7 Revision

updated 2017-10-02 15:39:42 +0200

rinigus gravatar image

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. For those interested, most of the sources are openly available in MER gitlab and the SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though, see the wiki entry (feel free to update this list by the way).

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.

The list of closed source parts are presented as answers to this post so one can vote. Please feel free to amend this post or the list and create new answers as wiki also so one can modify or add contributions.

To be also constructive, here is a list of open source contributions from community thanks to OSS parts:

click to hide/show revision 8
No.8 Revision

updated 2018-01-11 12:55:11 +0200

rinigus gravatar image

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. For those interested, most of the sources are openly available in MER gitlab and the SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though, see the wiki entry (feel free to update this list by the way).

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.

The list of closed source parts are presented as answers to this post so one can vote. Please feel free to amend this post or the list and create new answers as wiki also so one can modify or add contributions.

To be also constructive, here is a list of open source contributions from community thanks to OSS parts:

Edit Jan 2018: As a community member, I would expect to get some kind of reply to the requests presented as answers in this topic. As far as I can see, there is nothing on the subject here nor in 2018 plans (https://blog.jolla.com/summer-2017-ceo-update/). Since each proprietary component is shown separately, it allows to structure the official response of copyright owner(s) to reply specifically regarding that component. Taking into account that there are now several months passed from raising and structuring this topic, such reply should be expected. Please address it here, as it is an official communication channel between Jolla and SFOS users. Signed: rinigus

click to hide/show revision 9
No.9 Revision

updated 2018-01-14 21:42:16 +0200

rinigus gravatar image

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. For those interested, most of the sources are openly available in MER gitlab and the SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though, see the wiki entry (feel free to update this list by the way).

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.

The list of closed source parts are presented as answers to this post so one can vote. Please feel free to amend this post or the list and create new answers as wiki also so one can modify or add contributions.

To be also constructive, here is a list of open source contributions from community thanks to OSS parts:

Edit Jan 2018: As a community member, I would expect to get some kind of reply to the requests presented as answers in this topic. As far as I can see, there is nothing on the subject here nor in 2018 plans (https://blog.jolla.com/summer-2017-ceo-update/). Since each proprietary component is shown separately, it allows to structure the official response of copyright owner(s) to reply specifically regarding that component. Taking into account that there are now several months passed from raising and structuring this topic, such reply should be expected. Please address it here, as it is an official communication channel between Jolla and SFOS users. Signed: rinigus

click to hide/show revision 10
No.10 Revision

updated 2018-02-28 00:37:15 +0200

rozgwi gravatar image

Open source roadmap, from the community point of view

This post originates from the discussion during the Sept. 20th 2017 community meeting where it was suggested to provide to Jolla incites insights of what can be achieved from open sourcing or what is currently blocked by closed source parts in SailfishOS. As depicted in the Sailfish wiki, a lot of OS parts are already open source softwares, software, almost all backend services, most QML plugins allowing to directly deal from QML with email, calendars, notifications…, and two system applications. applications. For those interested, most of the sources are openly available in at the MER gitlab and the Gitlab repository and the various SailfishOS various components are well described in the wiki. Most UI related parts are still closed sources though, see source though (see the this wiki entry (feel - feel free to update this list by the way).

The objective of this wiki is to list and sort out by preference which parts the community would like be open so contributions may come. To be a bit more incentive, this wiki should list also the current contributions and how they are blocked by closed source softwares.software.

The list of closed source parts are is presented as answers to this post so one can vote. Please feel free to amend this post or the list and create list. Create new answers as wiki also as well so one can modify or add contributions.

To be also constructive, here is a list of open source contributions from community thanks to OSS parts:

Copyright © Jolla Ltd. 2013-2019. All rights reserved.
about | faq | help | privacy policy | terms of service | give feedback
Powered by Askbot version 0.7.49