Computerkid (talk | contribs) (Change IRC references to libera.chat) |
Silliewous (talk | contribs) No edit summary |
||
| (10 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
''Some parts of this wiki may not be up to date. We are working on updating it.'' | |||
= Fedora Mobility = | = Fedora Mobility = | ||
Fedora Mobility SIG is a group of contributors that are interested in running Fedora on portable devices such as phones and tablets. The revitalised SIG relaunched when open phone and tablet devices started to become available such as the [https://fedoraproject.org/wiki/Architectures/ARM/PinePhone Pine64 Pinephone]. | Fedora Mobility SIG is a group of contributors that are interested in running Fedora on portable devices such as phones and tablets. The revitalised SIG relaunched when open phone and tablet devices started to become available such as the [https://fedoraproject.org/wiki/Architectures/ARM/PinePhone Pine64 Pinephone]. | ||
'''We are looking for people to [[#Getting Involved|join the SIG]].''' | |||
== Mission == | == Mission == | ||
| Line 14: | Line 18: | ||
We communicate in the usual [[Communicate| Fedora channels]]. | We communicate in the usual [[Communicate| Fedora channels]]. | ||
* {{fpchat|#fedora- | * [https://matrix.to/#/#mobility:fedoraproject.org Matrix] is the preferred channel currently. | ||
* {{fpchat|#fedora-mobility}} on Libera.chat | |||
* [https://t.me/fedoraphone Telegram] | |||
* We use the arm mailing list [https://admin.fedoraproject.org/mailman/listinfo/arm subscribe to here]. | * We use the arm mailing list [https://admin.fedoraproject.org/mailman/listinfo/arm subscribe to here]. | ||
There currently is no bridge set up between matrix and the other channels. | |||
== Getting help == | |||
In case you are having trouble running Fedora on a mobile device. Join one of the communication channels to see if anyone can help. | |||
== Getting Involved == | |||
If you are interested in this SIG and want to help out, join one of the communication channels and express your interest. Some examples of ways you can help out: | |||
* '''Packagers:''' There are so many interesting packages that are not yet packaged for Fedora. You can find a list of things we need to package on [https://pagure.io/fedora-mobility/issues Fedora Mobility issue tracker]. Or of course you can contribute by packaging them yourself. | * '''Packagers:''' There are so many interesting packages that are not yet packaged for Fedora. You can find a list of things we need to package on [https://pagure.io/fedora-mobility/issues Fedora Mobility issue tracker]. Or of course you can contribute by packaging them yourself. | ||
* '''Reviewers:''' People able to do [[Packaging/ReviewGuidelines| package reviews]] can find a list of packages currently needing review in the [https://bugzilla.redhat.com/show_bug.cgi?id=1817424 Tracker Bug]. | * '''Reviewers:''' People able to do [[Packaging/ReviewGuidelines| package reviews]] can find a list of packages currently needing review in the [https://bugzilla.redhat.com/show_bug.cgi?id=1817424 Tracker Bug]. | ||
| Line 26: | Line 38: | ||
* '''Hardware Enablement:''' If you have the skills to work with low level early firmware, kernel and related components there's a need for assistance for device bring up, kernel development, debug and fixes to get support upstream and fix issues with hardware. | * '''Hardware Enablement:''' If you have the skills to work with low level early firmware, kernel and related components there's a need for assistance for device bring up, kernel development, debug and fixes to get support upstream and fix issues with hardware. | ||
* '''Software Develment:''' Fixes, features, mobile applications, improvement to existing Fedora applications to better run on phones and tablets. | * '''Software Develment:''' Fixes, features, mobile applications, improvement to existing Fedora applications to better run on phones and tablets. | ||
* '''Documentation:''' Keeping Wiki pages and documentation up to date. | |||
There are no skill requirements to join the SIG, interest is the most important. | |||
== Current Status == | == Current Status == | ||
Fedora Mobility has a reasonable amount of mobile focused packages available in Fedora Rawhide. Packages groups include: | Fedora Mobility has a reasonable amount of mobile focused packages available in Fedora Rawhide. Packages groups include: | ||
* A functional touch desktop environment, | * A functional touch desktop environment, Phosh. | ||
* A compatible touchscreen keyboard, squeekboard. | * A compatible touchscreen keyboard, squeekboard. | ||
* A Calling application for making/receiving phone calls, [https://source.puri.sm/Librem5/calls Calls] | * A Calling application for making/receiving phone calls, [https://source.puri.sm/Librem5/calls Calls] | ||
* Numerous other Fedora applications such as Calendar, Maps, Contacts etc | * Numerous other Fedora applications such as Calendar, Maps, Contacts etc | ||
Plasma-Mobile is now also available for the PinePhone, with all Gear apps ported. | |||
Fedora recently added support for building aarch64 FlatPaks so we'll be looking at what applications can be packaged as FlatPaks to make them easily consumable. | Fedora recently added support for building aarch64 FlatPaks so we'll be looking at what applications can be packaged as FlatPaks to make them easily consumable. | ||
| Line 42: | Line 59: | ||
The list of devices we're planning to initially support are as follows: | The list of devices we're planning to initially support are as follows: | ||
* [https://fedoraproject.org/wiki/Architectures/ARM/PinePhone Pine64 Pinephone] | * [https://fedoraproject.org/wiki/Architectures/ARM/PinePhone Pine64 Pinephone] | ||
* Pine64 PinePhone Pro | |||
* [https://fedoraproject.org/wiki/Architectures/ARM/PineTab Pine64 Pinetab] | * [https://fedoraproject.org/wiki/Architectures/ARM/PineTab Pine64 Pinetab] | ||
* [https://fedoraproject.org/wiki/Architectures/ARM/Librem5 Purism Librem 5] | * [https://fedoraproject.org/wiki/Architectures/ARM/Librem5 Purism Librem 5] | ||
We will review other devices as opportunity and interest arises, if you | We will review other devices as opportunity and interest arises, if you are capable and interested in adding support for other devices do reach out or file a RFE in the [https://pagure.io/fedora-mobility/issues Fedora Mobility issue tracker] with details of how you can assist in adding support for the new device. | ||
== Reporting Bugs == | == Reporting Bugs == | ||
| Line 55: | Line 73: | ||
* The [[Architectures/ARM|ARM]] architecture project. | * The [[Architectures/ARM|ARM]] architecture project. | ||
= Where to get Images = | = Where to get Images = | ||
| Line 63: | Line 80: | ||
Note that while both builds somewhat deviate in terms of features and ''goodies'', both provide at least basic functionality. | Note that while both builds somewhat deviate in terms of features and ''goodies'', both provide at least basic functionality. | ||
== | == Repositories == | ||
Available code is being worked on and linked to on [https://gitlab.com/fedora/sigs/mobility/ Fedora Mobility Special Interest Group Gitlab]. | |||
== Nightly Builds == | |||
The builds on [ftp://pine.warpspeed.dk/nightly/pinephone FTP] are released and rebuilt every night (hence the "nightly"). These are currently based on Minimal images of (usually) the latest release of Fedora. Upon a new release of Fedora, it may take some time to get these changes into the nightly. | |||
Due to the nature of the nightly builds, there is no guarantee about expected system stability. | |||
There are images for both Phosh and Plasma-Mobile in the Nightlies repo. | |||
= Roadmap to Fedora Spin = | = Roadmap to Fedora Spin = | ||
The group is currently working on getting an official [https://spins.fedoraproject.org/ Fedora Spin] going. There is no strict schedule at the moment, as the situation is evolving dynamically. This section tracks the progress and what needs to be done towards this goal. | The group is currently working on getting an official [https://spins.fedoraproject.org/ Fedora Spin] going. There is no strict schedule at the moment, as the situation is evolving dynamically. This section tracks the progress and what needs to be done towards this goal. | ||
== Official Kernel with Networking == | == Official Kernel with Networking == | ||
The builds are currently reliant on a custom kernel built by [https://megous.com/git/linux/log/?h=pp-5. | The builds are currently reliant on a custom kernel built by [https://megous.com/git/linux/log/?h=pp-5.17 megous] that includes a variety of patches. The patches are slowly accepted by the upstream kernel devs, which is required for them to land in the official Fedora kernel. | ||
The biggest missing part as of currently is a working WiFi/BT driver for the Realtek RTL8723CS chip in the Pinephone, as well as some bits regarding GPS in the ModemManager. | The biggest missing part as of currently is a working WiFi/BT driver for the Realtek RTL8723CS chip in the Pinephone, as well as some bits regarding GPS in the ModemManager. | ||
== Phosh Environment DNF Group == | == Phosh Environment DNF Group == | ||
| Line 95: | Line 107: | ||
[https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html Phosh] is a '''Pho'''ne '''Sh'''ell developed by [https://puri.sm/ Purism]. It is based on [https://en.wikipedia.org/wiki/GNOME GNOME] and currently provides the default desktop for all Mobility images based on Fedora. Phosh is required because the default GNOME doesn't work well on devices with form factors as small as Smartphones and isn't optimized for touch inputs. | [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html Phosh] is a '''Pho'''ne '''Sh'''ell developed by [https://puri.sm/ Purism]. It is based on [https://en.wikipedia.org/wiki/GNOME GNOME] and currently provides the default desktop for all Mobility images based on Fedora. Phosh is required because the default GNOME doesn't work well on devices with form factors as small as Smartphones and isn't optimized for touch inputs. | ||
== Official Image Infrastructure == | == Official Image Infrastructure == | ||
| Line 103: | Line 114: | ||
Currently there is no Mobility-specific kickstart file to use with Image Factory yet. | Currently there is no Mobility-specific kickstart file to use with Image Factory yet. | ||
== Members == | |||
* Leigh Griffin - @lgriffin | |||
* Eric Curtin - @ecurtin | |||
* Justin - @Justinzobel | |||
* Kevin Fenzi - @nirik | |||
* Markus Rathgeb - @maggu2810 | |||
* Niko - @nikodunk | |||
* Tor - @Torbuntu | |||
* alho2 - @alho2 | |||
Images are currently generated by collections of shell scripts (see above). In order to become an official spin, the images must be generated with more official tooling. As it isn't intended for the user to boot a live .iso on the phone, [https://imgfac.org/ Image Factory] will be used to generate the PinePhone images. | |||
Currently there is no Mobility-specific kickstart file to use with Image Factory yet. | |||
[[Category:SIGs]] | [[Category:SIGs]] | ||
[[Category:Fedora special-interest groups]] | [[Category:Fedora special-interest groups]] | ||
Latest revision as of 18:15, 26 April 2024
Some parts of this wiki may not be up to date. We are working on updating it.
Fedora Mobility
Fedora Mobility SIG is a group of contributors that are interested in running Fedora on portable devices such as phones and tablets. The revitalised SIG relaunched when open phone and tablet devices started to become available such as the Pine64 Pinephone.
We are looking for people to join the SIG.
Mission
Fedora Mobility is aiming to eventually create an official Fedora spin to run on mobile phones, tablets and other similar portable battery powered devices. Initial focus is on the PinePhone, but we hope to support other smartphones such as the Librem 5. The aim is to get a stable, open source Phone platform that can be used as a daily driver, with full upstream software.
Meetings
Meetings are 16:30 UTC on #fedora-meeting[?] on Libera.chat on the second Monday of each month. See: [1]
Communication
We communicate in the usual Fedora channels.
- Matrix is the preferred channel currently.
- #fedora-mobility[?] on Libera.chat
- Telegram
- We use the arm mailing list subscribe to here.
There currently is no bridge set up between matrix and the other channels.
Getting help
In case you are having trouble running Fedora on a mobile device. Join one of the communication channels to see if anyone can help.
Getting Involved
If you are interested in this SIG and want to help out, join one of the communication channels and express your interest. Some examples of ways you can help out:
- Packagers: There are so many interesting packages that are not yet packaged for Fedora. You can find a list of things we need to package on Fedora Mobility issue tracker. Or of course you can contribute by packaging them yourself.
- Reviewers: People able to do package reviews can find a list of packages currently needing review in the Tracker Bug.
- Testers: If you have a small device and use Fedora on it, file bugs and add them as a blocker for the Fedora Mobility Tracker Bug.
- Bugs: Become a BugZapper and help us with Fedora Mobility related bugs.
- Hardware Enablement: If you have the skills to work with low level early firmware, kernel and related components there's a need for assistance for device bring up, kernel development, debug and fixes to get support upstream and fix issues with hardware.
- Software Develment: Fixes, features, mobile applications, improvement to existing Fedora applications to better run on phones and tablets.
- Documentation: Keeping Wiki pages and documentation up to date.
There are no skill requirements to join the SIG, interest is the most important.
Current Status
Fedora Mobility has a reasonable amount of mobile focused packages available in Fedora Rawhide. Packages groups include:
- A functional touch desktop environment, Phosh.
- A compatible touchscreen keyboard, squeekboard.
- A Calling application for making/receiving phone calls, Calls
- Numerous other Fedora applications such as Calendar, Maps, Contacts etc
Plasma-Mobile is now also available for the PinePhone, with all Gear apps ported.
Fedora recently added support for building aarch64 FlatPaks so we'll be looking at what applications can be packaged as FlatPaks to make them easily consumable.
As of currently, some core packages are maintained in Copr. Work is done to get all patches upstreamed. You can find an overview of packages that use downstream patches (and what they patch) here.
Supported devices
The list of devices we're planning to initially support are as follows:
- Pine64 Pinephone
- Pine64 PinePhone Pro
- Pine64 Pinetab
- Purism Librem 5
We will review other devices as opportunity and interest arises, if you are capable and interested in adding support for other devices do reach out or file a RFE in the Fedora Mobility issue tracker with details of how you can assist in adding support for the new device.
Reporting Bugs
We have a few different places to report bugs and request features:
- For bugs in packages we use the Fedora package bugzilla. Please add the Tracker Bug as a blocking bug to the bug report so we're aware the issue relates to Mobility.
- For issues with the images, new package requests or RFEs we use the Fedora Mobility issue tracker.
Related Fedora projects
- The ARM architecture project.
Where to get Images
As mentioned above, the effort is still quite early on and thus we have no official build infrastructure yet. Currently two different builds are maintained, see below for details.
Note that while both builds somewhat deviate in terms of features and goodies, both provide at least basic functionality.
Repositories
Available code is being worked on and linked to on Fedora Mobility Special Interest Group Gitlab.
Nightly Builds
The builds on FTP are released and rebuilt every night (hence the "nightly"). These are currently based on Minimal images of (usually) the latest release of Fedora. Upon a new release of Fedora, it may take some time to get these changes into the nightly.
Due to the nature of the nightly builds, there is no guarantee about expected system stability.
There are images for both Phosh and Plasma-Mobile in the Nightlies repo.
Roadmap to Fedora Spin
The group is currently working on getting an official Fedora Spin going. There is no strict schedule at the moment, as the situation is evolving dynamically. This section tracks the progress and what needs to be done towards this goal.
Official Kernel with Networking
The builds are currently reliant on a custom kernel built by megous that includes a variety of patches. The patches are slowly accepted by the upstream kernel devs, which is required for them to land in the official Fedora kernel.
The biggest missing part as of currently is a working WiFi/BT driver for the Realtek RTL8723CS chip in the Pinephone, as well as some bits regarding GPS in the ModemManager.
Phosh Environment DNF Group
Just like there are Package Groups for *Workstation*, *KDE* or *Development Tools* that pull in bundles of packages related to each other, a Package Group for Phosh is required.
Phosh is a Phone Shell developed by Purism. It is based on GNOME and currently provides the default desktop for all Mobility images based on Fedora. Phosh is required because the default GNOME doesn't work well on devices with form factors as small as Smartphones and isn't optimized for touch inputs.
Official Image Infrastructure
Images are currently generated by collections of shell scripts (see above). In order to become an official spin, the images must be generated with more official tooling. As it isn't intended for the user to boot a live .iso on the phone, Image Factory will be used to generate the PinePhone images.
Currently there is no Mobility-specific kickstart file to use with Image Factory yet.
Members
- Leigh Griffin - @lgriffin
- Eric Curtin - @ecurtin
- Justin - @Justinzobel
- Kevin Fenzi - @nirik
- Markus Rathgeb - @maggu2810
- Niko - @nikodunk
- Tor - @Torbuntu
- alho2 - @alho2
Images are currently generated by collections of shell scripts (see above). In order to become an official spin, the images must be generated with more official tooling. As it isn't intended for the user to boot a live .iso on the phone, Image Factory will be used to generate the PinePhone images.
Currently there is no Mobility-specific kickstart file to use with Image Factory yet.