Are you over 18 and want to see adult content?
More Annotations
A complete backup of timeforcambio.org
Are you over 18 and want to see adult content?
Bowen University | Excellence & Godliness
Are you over 18 and want to see adult content?
Alquiler Autobús Minibús Comparar Ofertas | Rent-Autobus
Are you over 18 and want to see adult content?
Гуми зимни, летни за автомобили и джипове на топ цени | Медина-Мед
Are you over 18 and want to see adult content?
Inicio | GM Financial es la financiera captiva de General Motors
Are you over 18 and want to see adult content?
Minecraft Serwer Serwery Minecraft Lista Serwerów Minecraft
Are you over 18 and want to see adult content?
Hand-painted kitchens, furniture & period property
Are you over 18 and want to see adult content?
Favourite Annotations
A complete backup of elmundodelamitologiacelta.blogspot.com
Are you over 18 and want to see adult content?
A complete backup of torontohondaparts.com
Are you over 18 and want to see adult content?
A complete backup of himoneybyescams.com
Are you over 18 and want to see adult content?
A complete backup of magazinaquafeline.blogspot.com
Are you over 18 and want to see adult content?
A complete backup of rawdognpowerpup.tumblr.com
Are you over 18 and want to see adult content?
Text
MER WIKI
Mer aims to be a FOSS, inclusive, meritocratically governed and openly developed Core optimised for QML/JS, providing a mobile-optimised base distribution for use by device manufacturers. Mer is based upon the work from the Core section of the MeeGo project . We have some clear goals: To have a device manufacturer oriented structure, processesADAPTATIONS
Adaptations. Mer Core does not provide hardware adaptations itself but several have been developed or are in progress, and may or may not be maintained by the community. For a longer list, see Community_Workspace . For creating a new adaptation, see the Adaptation Guide . The list below is organized by processor family (Mer port name, see OBS SAILFISH/PYTHON DEVELOPMENTPLATFORM SDK
U-BOOT ADAPTATION GUIDE Basic assumptions / scope. This guide is meant for converting a working u-boot to boot to mer / nemo from SD card or internal eMMC . "loadaddr" environment variable is defined. It is assumed that you have some way of accessing u-boot console. Mer / Nemo / etc image with separate FAT or Ext2 boot partition and a root partition on your bootmedia
BUTEO/MTP - MER WIKISEE MORE ON WIKI.MERPROJECT.ORG ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR DAVINCI Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt. ADAPTATIONS/PINEPHONE64 Hardware Support. Full information of hardware spec Here. PostMarket OS hardware information PostMarketOS Wiki. WiFi/BT RTL8723CS WiFi . The WiFi driver isn't available in the Linux kernel yet. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR FP2 ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR MAKO ChangeLog . gamma8 - 29th of Dec, 2016. New Sailfish OS release 2.0.5.6 Dirty Cow kernel fix Kernel support for JBD, XFS, iso9660 and UDF filesystems added.MER WIKI
Mer aims to be a FOSS, inclusive, meritocratically governed and openly developed Core optimised for QML/JS, providing a mobile-optimised base distribution for use by device manufacturers. Mer is based upon the work from the Core section of the MeeGo project . We have some clear goals: To have a device manufacturer oriented structure, processesADAPTATIONS
Adaptations. Mer Core does not provide hardware adaptations itself but several have been developed or are in progress, and may or may not be maintained by the community. For a longer list, see Community_Workspace . For creating a new adaptation, see the Adaptation Guide . The list below is organized by processor family (Mer port name, see OBS SAILFISH/PYTHON DEVELOPMENTPLATFORM SDK
U-BOOT ADAPTATION GUIDE Basic assumptions / scope. This guide is meant for converting a working u-boot to boot to mer / nemo from SD card or internal eMMC . "loadaddr" environment variable is defined. It is assumed that you have some way of accessing u-boot console. Mer / Nemo / etc image with separate FAT or Ext2 boot partition and a root partition on your bootmedia
BUTEO/MTP - MER WIKISEE MORE ON WIKI.MERPROJECT.ORG ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR DAVINCI Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt. ADAPTATIONS/PINEPHONE64 Hardware Support. Full information of hardware spec Here. PostMarket OS hardware information PostMarketOS Wiki. WiFi/BT RTL8723CS WiFi . The WiFi driver isn't available in the Linux kernel yet. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR FP2 ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR MAKO ChangeLog . gamma8 - 29th of Dec, 2016. New Sailfish OS release 2.0.5.6 Dirty Cow kernel fix Kernel support for JBD, XFS, iso9660 and UDF filesystems added.ADAPTATIONS
Adaptations. Mer Core does not provide hardware adaptations itself but several have been developed or are in progress, and may or may not be maintained by the community. For a longer list, see Community_Workspace . For creating a new adaptation, see the Adaptation Guide . The list below is organized by processor family (Mer port name, see OBS ADAPTATIONS/LIBHYBRIS Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Downloadable Image Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys VibraPLATFORM SDK
The platform SDK rootfs contains a helper script to enter the chroot named 'mer-sdk-chroot'. The helper script is located in the root directory (/) of the rootfs. It requires you to have sudo ability. As mentioned, the SDK is location independent so it uses the location of ADAPTATIONS/PINEPHONE64 Hardware Support. Full information of hardware spec Here. PostMarket OS hardware information PostMarketOS Wiki. WiFi/BT RTL8723CS WiFi . The WiFi driver isn't available in the Linux kernel yet. OBS SETUP - MER WIKI These steps show how to set up a Mer Open Build Service (OBS) on an openSuSE 11.4 installation. An OBS installation will usually consist of an OBS web server, aSAILFISH - MER WIKI
Sailfish is a Linux-based mobile operating system developed by Jolla in cooperation with the Mer project and supported by the Sailfish Alliance. Although it is primarily targeted at mobile phones, it is also intended to support other categories of devices. The Sailfish OS and the Sailfish Software development kit are based on the Linuxkernel
BACON INFO - MER WIKI The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/) ADAPTATIONS/LIBHYBRIS/PORTERS Codename Retail Name Porters Base QCOM_BSP HWC Display RIL Version Active Past idol3: Alcatel Idol 3 (5.5") vknecht: 14.1: y: 1.5: caf/msm8916: 11 fp2-sibon ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISH OS FOR I4113 Install steps for Devices with MERGED partitions: unlock bootloader. flash twrp recovery & format data/cache partition. flash zip with twrp. flash AOSP 9. reboot to AOSP 9, after init down, reboot to recovery. flash sailfishos zip with twrp. flash Sailfish-OS-3.1.0.12-i4113-0.0.1.1.zip. reboot. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR VINCE Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt.MER WIKI
Mer aims to be a FOSS, inclusive, meritocratically governed and openly developed Core optimised for QML/JS, providing a mobile-optimised base distribution for use by device manufacturers. Mer is based upon the work from the Core section of the MeeGo project . We have some clear goals: To have a device manufacturer oriented structure, processesADAPTATIONS
Adaptations. Mer Core does not provide hardware adaptations itself but several have been developed or are in progress, and may or may not be maintained by the community. For a longer list, see Community_Workspace . For creating a new adaptation, see the Adaptation Guide . The list below is organized by processor family (Mer port name, see OBS SAILFISH/PYTHON DEVELOPMENTPLATFORM SDK
U-BOOT ADAPTATION GUIDE Basic assumptions / scope. This guide is meant for converting a working u-boot to boot to mer / nemo from SD card or internal eMMC . "loadaddr" environment variable is defined. It is assumed that you have some way of accessing u-boot console. Mer / Nemo / etc image with separate FAT or Ext2 boot partition and a root partition on your bootmedia
BUTEO/MTP - MER WIKISEE MORE ON WIKI.MERPROJECT.ORG ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR DAVINCI Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt. ADAPTATIONS/PINEPHONE64 Hardware Support. Full information of hardware spec Here. PostMarket OS hardware information PostMarketOS Wiki. WiFi/BT RTL8723CS WiFi . The WiFi driver isn't available in the Linux kernel yet. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR FP2 ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR MAKO ChangeLog . gamma8 - 29th of Dec, 2016. New Sailfish OS release 2.0.5.6 Dirty Cow kernel fix Kernel support for JBD, XFS, iso9660 and UDF filesystems added.MER WIKI
Mer aims to be a FOSS, inclusive, meritocratically governed and openly developed Core optimised for QML/JS, providing a mobile-optimised base distribution for use by device manufacturers. Mer is based upon the work from the Core section of the MeeGo project . We have some clear goals: To have a device manufacturer oriented structure, processesADAPTATIONS
Adaptations. Mer Core does not provide hardware adaptations itself but several have been developed or are in progress, and may or may not be maintained by the community. For a longer list, see Community_Workspace . For creating a new adaptation, see the Adaptation Guide . The list below is organized by processor family (Mer port name, see OBS SAILFISH/PYTHON DEVELOPMENTPLATFORM SDK
U-BOOT ADAPTATION GUIDE Basic assumptions / scope. This guide is meant for converting a working u-boot to boot to mer / nemo from SD card or internal eMMC . "loadaddr" environment variable is defined. It is assumed that you have some way of accessing u-boot console. Mer / Nemo / etc image with separate FAT or Ext2 boot partition and a root partition on your bootmedia
BUTEO/MTP - MER WIKISEE MORE ON WIKI.MERPROJECT.ORG ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR DAVINCI Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt. ADAPTATIONS/PINEPHONE64 Hardware Support. Full information of hardware spec Here. PostMarket OS hardware information PostMarketOS Wiki. WiFi/BT RTL8723CS WiFi . The WiFi driver isn't available in the Linux kernel yet. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR FP2 ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR MAKO ChangeLog . gamma8 - 29th of Dec, 2016. New Sailfish OS release 2.0.5.6 Dirty Cow kernel fix Kernel support for JBD, XFS, iso9660 and UDF filesystems added.ADAPTATIONS
Adaptations. Mer Core does not provide hardware adaptations itself but several have been developed or are in progress, and may or may not be maintained by the community. For a longer list, see Community_Workspace . For creating a new adaptation, see the Adaptation Guide . The list below is organized by processor family (Mer port name, see OBS ADAPTATIONS/LIBHYBRIS Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Downloadable Image Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys VibraPLATFORM SDK
The platform SDK rootfs contains a helper script to enter the chroot named 'mer-sdk-chroot'. The helper script is located in the root directory (/) of the rootfs. It requires you to have sudo ability. As mentioned, the SDK is location independent so it uses the location of ADAPTATIONS/PINEPHONE64 Hardware Support. Full information of hardware spec Here. PostMarket OS hardware information PostMarketOS Wiki. WiFi/BT RTL8723CS WiFi . The WiFi driver isn't available in the Linux kernel yet. OBS SETUP - MER WIKI These steps show how to set up a Mer Open Build Service (OBS) on an openSuSE 11.4 installation. An OBS installation will usually consist of an OBS web server, aSAILFISH - MER WIKI
Sailfish is a Linux-based mobile operating system developed by Jolla in cooperation with the Mer project and supported by the Sailfish Alliance. Although it is primarily targeted at mobile phones, it is also intended to support other categories of devices. The Sailfish OS and the Sailfish Software development kit are based on the Linuxkernel
BACON INFO - MER WIKI The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/) ADAPTATIONS/LIBHYBRIS/PORTERS Codename Retail Name Porters Base QCOM_BSP HWC Display RIL Version Active Past idol3: Alcatel Idol 3 (5.5") vknecht: 14.1: y: 1.5: caf/msm8916: 11 fp2-sibon ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISH OS FOR I4113 Install steps for Devices with MERGED partitions: unlock bootloader. flash twrp recovery & format data/cache partition. flash zip with twrp. flash AOSP 9. reboot to AOSP 9, after init down, reboot to recovery. flash sailfishos zip with twrp. flash Sailfish-OS-3.1.0.12-i4113-0.0.1.1.zip. reboot. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR VINCE Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt. PLATFORM SDK AND SB2 The most straightforward way to use Scratchbox2 is within the Mer Platform SDK.This page will go through the steps of using SB2 to compile a simple program in a tutorial-like manner. U-BOOT ADAPTATION GUIDE Basic assumptions / scope. This guide is meant for converting a working u-boot to boot to mer / nemo from SD card or internal eMMC . "loadaddr" environment variable is defined. It is assumed that you have some way of accessing u-boot console. Mer / Nemo / etc image with separate FAT or Ext2 boot partition and a root partition on your bootmedia
ADAPTATIONS
Adaptations. Mer Core does not provide hardware adaptations itself but several have been developed or are in progress, and may or may not be maintained by the community. For a longer list, see Community_Workspace . For creating a new adaptation, see the Adaptation Guide . The list below is organized by processor family (Mer port name, see OBSPLATFORM SDK
ADAPTATIONS/LIBHYBRIS Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Downloadable Image Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR DAVINCI Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR FP2 ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR ARIES Install steps for Devices with MERGED partitions: unlock bootloader. flash twrp recovery & format data/cache partition. flash zip with twrp. flash CyanogenMod 12.1 ROM cm-12.1-20190804-UNOFFICIAL-aries.zip. reboot to CyanogenMod, after init down, reboot to recovery. flash sailfishos zip with twrp. flash sailfishos-aries-release-3.0.3.9-L-alpha ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISH OS FOR I4113 Install steps for Devices with MERGED partitions: unlock bootloader. flash twrp recovery & format data/cache partition. flash zip with twrp. flash AOSP 9. reboot to AOSP 9, after init down, reboot to recovery. flash sailfishos zip with twrp. flash Sailfish-OS-3.1.0.12-i4113-0.0.1.1.zip. reboot. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR GEMINI Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt. PLATFORM SDK AND SB2 The most straightforward way to use Scratchbox2 is within the Mer Platform SDK.This page will go through the steps of using SB2 to compile a simple program in a tutorial-like manner. U-BOOT ADAPTATION GUIDE Basic assumptions / scope. This guide is meant for converting a working u-boot to boot to mer / nemo from SD card or internal eMMC . "loadaddr" environment variable is defined. It is assumed that you have some way of accessing u-boot console. Mer / Nemo / etc image with separate FAT or Ext2 boot partition and a root partition on your bootmedia
ADAPTATIONS
Adaptations. Mer Core does not provide hardware adaptations itself but several have been developed or are in progress, and may or may not be maintained by the community. For a longer list, see Community_Workspace . For creating a new adaptation, see the Adaptation Guide . The list below is organized by processor family (Mer port name, see OBSPLATFORM SDK
ADAPTATIONS/LIBHYBRIS Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Downloadable Image Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR DAVINCI Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR FP2 ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR ARIES Install steps for Devices with MERGED partitions: unlock bootloader. flash twrp recovery & format data/cache partition. flash zip with twrp. flash CyanogenMod 12.1 ROM cm-12.1-20190804-UNOFFICIAL-aries.zip. reboot to CyanogenMod, after init down, reboot to recovery. flash sailfishos zip with twrp. flash sailfishos-aries-release-3.0.3.9-L-alpha ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISH OS FOR I4113 Install steps for Devices with MERGED partitions: unlock bootloader. flash twrp recovery & format data/cache partition. flash zip with twrp. flash AOSP 9. reboot to AOSP 9, after init down, reboot to recovery. flash sailfishos zip with twrp. flash Sailfish-OS-3.1.0.12-i4113-0.0.1.1.zip. reboot. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR GEMINI Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt.MER WIKI
Mer aims to be a FOSS, inclusive, meritocratically governed and openly developed Core optimised for QML/JS, providing a mobile-optimised base distribution for use by device manufacturers. Mer is based upon the work from the Core section of the MeeGo project . We have some clear goals: To have a device manufacturer oriented structure, processes PLATFORM SDK AND SB2 The most straightforward way to use Scratchbox2 is within the Mer Platform SDK.This page will go through the steps of using SB2 to compile a simple program in a tutorial-like manner.PLATFORM SDK
The platform SDK rootfs contains a helper script to enter the chroot named 'mer-sdk-chroot'. The helper script is located in the root directory (/) of the rootfs. It requires you to have sudo ability. As mentioned, the SDK is location independent so it uses the location ofPLEASE LOG IN
Please Log In. Username: Password: Or sign up as a new user. Locations. Projects; SearchIRC GUIDELINES
IRC in the Mer project. We use IRC for a variety of real-time conversations: Meetings; Discussion Troubleshooting Collaboration Chatting with other contributors BUTEO/MTP - MER WIKI The MTP applications provides the functionality of file exploration from a PC that supports the initiator role of MTP. The purpose of this wiki document is to provide the design details of the MTP stack implementation and the MTP application. The MTP application uses the stack and provides Maemo specific MTP functionality. BACON INFO - MER WIKI The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/) ADAPTATIONS/PINEPHONE64 Hardware Support. Full information of hardware spec Here. PostMarket OS hardware information PostMarketOS Wiki. WiFi/BT RTL8723CS WiFi . The WiFi driver isn't available in the Linux kernel yet. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISH OS FOR I4113 Install steps for Devices with MERGED partitions: unlock bootloader. flash twrp recovery & format data/cache partition. flash zip with twrp. flash AOSP 9. reboot to AOSP 9, after init down, reboot to recovery. flash sailfishos zip with twrp. flash Sailfish-OS-3.1.0.12-i4113-0.0.1.1.zip. reboot. ADAPTATIONS/LIBHYBRIS/INSTALL SAILFISHOS FOR Legend: Y - Working (y=hack), Y - HAL works, not hooked up to UI/MW/init yet, N - Not working, ? - Untested, N/A - N/A on device. Device released Linux Kernel Display Touch LED Audio NFC Bluetooth GSM WLAN GPS Camera Fingerprint Sensors Keys Vibra Haptics Power Mgmt.SAILFISH OS FORUM
* Documentation
* Harbour
* Blog
Sign UpLog In
*
*
Changes needed to merge the project names to Sailfish OSAnnouncements
You have selected 0 posts.select all
cancel selecting
20 Aug
1 / 35
20 Aug
18d ago
maajussi
1
20 Aug
In early 2019 we, together with the Mer project, announced that we will unify Mer and Sailfish operations under the Sailfish OS domain. The blog post 31 we released at the time explains the full rationale for the decision, but here’s a brief summary. In public _Mer_ as a name is still in use along with Nemo, Maemo and even Meego at times. All these names are related to developing a Linux-based mobile operating system. Many of us in Jolla have been part of this story from the beginning, since the times when also Nokia was involved in the project, and we appreciate and cherish the legacy that is carried in these names. At the same time we have undergone a transformation during the past few years, and we need to develop the offering further. Sailfish OS is a European-based mobile operating system based on open source software, offering a transparent and customizable alternative to dominant operating systems. It is independent from large industry players developing closed ecosystems. Building the community under one brand - Sailfish OS - is a very meaningful factor in our joint effort to create a viable Linux-based mobile operating system. It is evident that we cannot do this alone and we need the support of the whole mobile OS community. The commitment and the amount of contributions from the community is significant and important part of Sailfish OS - past, present and in the future. Let’s make Sailfish OS even better - together! SERVICES AND CHANNELS IMPACTED Now as the migration project is reaching its end, it’s time to provide an update on the changes we described in the earlier blog post31 . In addition to
unifying our services and offering, we are merging the brands under the Sailfish OS name. This will be done in phases and you may have already noticed some of the changes taking place. For example https://git.sailfishos.org/ 27 (including https://git.merproject.org 23 ) will be migrated to https://github.com/sailfishos 59 . We are also changing naming conventions, so our repository names will use Sailfish OS instead of Mer. The process is slow as there are dependencies, but we are closing in on the last tasks in this effort. Issue handling will be simplified, with discussion and issues moving to this forum. Our old bug tracker at https://bugs.merproject.org/ 13 will therefore be closed. Sometimes it may be more appropriate or effective to post bugs as issues against specific projects on Github rather than the forum, and that’s fine too. For example we’ve already been handling Sailfish OS browser bugs also using the Github issue tracker for some time now (e.g., https://github.com/sailfishos/sailfish-browser/issues 25).
We will also start the process to close the Open Build Service (OBS) https://build.merproject.org/ 52 . Before we close the community OBS we will provide detailed documentation on how to build packages, including guidance on repository structure best practices. This should help to reduce any problems caused by this change. We understand the importance of OBS to community and especially to Sailfish OS porters. We will plan this transition in close co-operation with the developers using theservice.
In all cases, we will do our best to provide guidance to all who is impacted by these changes. Feel free to start a discussion on anything that we might have missed.1 Reply
10
* OBS shut down and next steps2 * Issues between Jolla and the Users/Community2 * Idea: Development log for better communication*
CREATED
20 Aug
*
LAST REPLY
18d
* 34
REPLIES
* 21.7k
VIEWS
* 18
USERS
* 166
LIKES
* 20
LINKS
*
5
5
3
tanriol
20 Aug
maajussi:
> Our old bug tracker at https://bugs.merproject.org/ > will therefore be closed. Could you please clarify whether this means “archived in readonly mode”, “migrated” (where?) or “just deleted with all the bugs” (are they considered too old and/or bad to be worth saving)?1 Reply
5
rla88
20 Aug
In general there should be a service which creates the app from the source published like OBS does. That could be integrated e.g. to the Harbour as an option. The app user then could rely the app is created from the open source . Not every user can download SDK for thatpurpose .
3
rinigus
20 Aug
Unless it is cost-cutting measure, I do not understand why are you * moving git.sailfishos.org 14* closing OBS
If it is due to the running costs, please state it clearly in theannouncement.
If I remember correctly, gitlab instance git.sailfishos.org 14 was done recently, it looks to be integrated into the workflows. Why move again? Not sure it costs that much to maintain it, but you know better. Closing OBS is a major problem and we have to find some service that would be able to replace it. Currently, OBS makes development for SFOS easier and this model is attractive for me, as a developer. Note that not only porters are going to be hit. All mapping stack that I work on is possible, in part, to OBS. There is a large number of dependencies and OBS allows us to keep all in sync with the SFOS and dependencies updates. In less extent, due to smaller number of dependencies, same goes for Flatpak support. Closing OBS will hit Nemo with such important work for SFOS as Qt update. Please be aware that SFOS is not the only one mobile linux around with the other options either there for some time (Ubuntu Touch) or gaining momentum (PureOS and Plasma). Hence it is important to keep the best possible development environment, something that has been quite good for SFOS for a while. Don’t break it. Assuming that OBS closure is due to it’s high costs, what would be an alternative? Should we move to openSUSE OBS? What could be other build services available? We should probably look for something that has ability to build complex projects and provide repository from thebuild artifacts.
1 Reply
28
dcaliste
21 Aug
Thank you @rinigus for expressing exactly my thoughts when I read this annoucement. Particularly about closure of git.sailfishos.org 5 and the OBS. It’s personal taste, but I like much Gitlab (thus git.sailfishos.org 5 ) for collaborative development. The activity page is extremely convenient to follow the development with a clear view of comments, MRs… I’ve learn a lot of best practices just looking at others MRs and related comments. I don’t know if Github provides such a convenient overview. At least, I didn’t findit.
1 Reply
8
maajussi
tanriol
21 Aug
We will evaluate what should and could be done to possibly preserve the information (https://bugs.merproject.org/ 1 ). Your input is welcome! It is meaningful for example from the point, that it maintains the background information of why certain changes have been conducted. At this point the immediate action we guide towards is that we should stop using the service.rinigus
dcaliste
21 Aug
@dcaliste : maybe somewhat similar, try https://github.com/search?q=org%3Asailfishos 10. but, as we are
limited to one organization, maybe not as organized as in gitlabinstance
dcaliste
21 Aug
Thanks, but it lacks the best of Gitlab activity page, a list (time sorted is better when there are 600 projects like in mer-core) of last MRs and related comments.1
attah Regular
21 Aug
@maajussi Just to double-check. Is OBS being removed, full stop? Or are there still discussions on floating a replacementsomehow?
Personally i never got around to using it, but automatic builds sure would have been nice many times. If it turns out the community has to step up and fill this gap, I’m interested in helping. (I’ll keep an eye out for threads about this :))3
Kabouik
2
21 Aug
I am afraid this may be a major blow to the whole porting efforts, which have only been getting bigger over the years, and also developers of native applications. Those developers and/or porters greatly contribute to the Sailfish ecosystem with their work, and overall make it more robust and more attractive as more devices or applications are available. There may be consequences of this on Jolla and Sailfish itself, which I guess have been weighed before coming to this, but this is very concerning. I hope the reception by the developers can help reconsidering the decision, or that proper _and equally convenient_ alternatives maintained by Jolla can be proposed in return of what the porters and developers made of Sailfish. Self-hosting and building locally sounds like a huge pain that would surely discourage a good fraction of those key community people. They are literally already saying it all over the various Telegram or IRC servers, or here; this can’t beoverlooked.
Well, a significant contributor already left the boat and moved to another OS today with an announcement on his repository. :\1 Reply
9
Mister_Magister
21 Aug
If OBS is going to be removed, i’ve talked with basil from openrepos and he will accept use of openrepos for OTA packages!Original email
> You can create a single application (one per release or device) and > upload all packages to it. > Make sure to have the main package(meta package or whatever you have > as a base installation package) as a #1 in list of uploaded apps > (version settings as well some other info will be pulled from it).>
> Check this application as an example: > https://openrepos.net/content/koenigseggccgt/developer-mode 10> (note
> lots of apps)
> or this one: https://openrepos.net/content/hanhsuan/libchewing 4 > (note main and> devel package).
>
> You may select the “Libraries” category for them. Such > applications are not displayed on main pages or within the storeman > app when updated.7
rinigus
21 Aug
@maajussi , just a reminder and to be clear. As we discussed at the meeting, please reply to my questions above and let’s continue the discussion. To make it relevant to the topic - I don’t think these “Changes are needed to merge the project names to Sailfish OS”. You could just rename OBS domain. So, the main part of the announcement has nothing to do with the project names.13
KuroNeko
22 Aug
This is discouraging. First of all the title of this post is wrong. These changes are not needed only for the name change. This is certainly also for other reasons, that are not communicated properly. OBS and the git.sailfishos.org 2 instance have been pretty valueable so far. While the move to github can be somewhat reasoned about, if you want to be more visible to the open source community, that uses Github primarily, closing OBS does not really fall in line with anything as far as I can tell. I would really like to know the actual reasons for this!10
szopin
Kabouik
22 Aug
> Well, a significant contributor already left the boat and moved to > another OS today with an announcement on his repository. :\ Who did we lose? And why so early before jolla confirmed any of those as definitive changes?Kabouik
22 Aug
It’s not for me to say¹ until they voice it themselves here to firmly correlate it with the OBS closure, as I cannot tell if there were other reasons; it seems multiple devs were tolerating some issues so far and this new hit could be one too many. : If you are interested about running SFOS on X Compact, it’s easyto find.
2
Kabouik
1 szopin
22 Aug
I’m sorry you are taking it this way, I was trying to support devs, not looking for a fight. He just confirmed on IRC that this is relatedto OBS, so: g7.
Also, this was just an edit to my initial post, not the main point, and not really worded as you summed it up.szopin
22 Aug
Not sure if anyone here is not supporting devs, but ‘ballerinas’ that quit at any whiff of what they don’t like, probably not many (add to that: dev I mean is very important but also wants to stay anon), just say it or stop pretendingKabouik
22 Aug
It was just me being overcautious until he confirmed explicitly; hejust did.
Back to the general topic, discussions since yesterday here or on IRC show that others are waiting for the final decision on OBS, but are considering this could be the reason to move on. Not only because of it, there are other issues they’ve been living with so far, but OBS closure, if confirmed, will make their work more difficult to the point that some think it won’t be worth it. I wanted to voice my concerns in one post, but I’m no dev and can’t make more valuable contributions to this discussion, so I’ll just leave the space for the questions @rinigus hasasked.
2
mips_tux
22 Aug
I am not a developer, so it is very difficult for me to have a goodjudgment.
But what i don’t understand is the choice by Jolla of Microsoft (Github, a proprietary service !). For me the choice of Github is not really safe. Cf : https://carlchenet.com/le-danger-github-revu-et-augmente/ 7 Sorry it’s in french. But it’s really a good reading.1
Kabouik
1 szopin
22 Aug
I am not following you. What I said is “significant contributor”, and that was merely an edit several hours after my initial post, not the point. “Huge”, “big name overground”, those are your interpretation of “significant contributor”. Please don’t put words in my mouth and then accuse me of using those words, or of disappointing you because the name is not big enough for you. I didn’t sell anything you are expecting. About the name, you asked me to name the person multiple times after I named him. Not sure if you were dissatisfied with the name, or just didn’t see it in the post. I can’t make up names out of my hat if you are not satisfied with the only one I said had already left theboat.
Just because you posted four messages in a row doesn’t mean I was here all along to answer but in the end chickened out, as you said. Therefore I am sorry if that took 20 hours, but you only asked for thename. Here 28
is the
announcement on the repository. Jeez. Also, I am not the one who flagged your messages as spam and I haven’t reported anything, so I would appreciate if you could keep me out of the lie and censorship accusations, or funny filenames. I don’t see where this is going but I don’t like it and I don’t want to turn what I think is a crucial discussion into an individual fight. I’ll leave this thread to people who can post more relevant things than I can, and just continue reading because I want to know what’s up with OBS and how it affects developers.1 Reply
4
Invalid date Invalid dateDetails
Copyright © 2024 ArchiveBay.com. All rights reserved. Terms of Use | Privacy Policy | DMCA | 2021 | Feedback | Advertising | RSS 2.0