-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of all ports #75
Comments
Perhaps split the icon "Supported Devices" and add a link to officially supported devices and another one to community supported devices. Community port could be stored under this page. |
I'm all for this (as you can see from the linked posts!). As soon as I get the chance I'll propose a PR, unless someone else gets there first. |
Mmh, actually IMHO it should be better to rename this page: https://docs.sailfishos.org/Develop/HW_Adaptation/Devices/ to https://docs.sailfishos.org/Develop/HW_Adaptation/OfficialDevices/ (or something similar) And add another page called CommunityDevice. |
Separate pages seem unnecessary in my opinion. Section for each porter would better I think. First ports done by Jolla and then each community porter. |
In bigger picture I'd not add all information under hardware adaptation simply as there are two kind of information seekers; to which device I could buy Sailfish X license & how do I contribute to the HW adaptation xyz. I started drafting structure for the SupportedDevices. Let's see how that turnout to be. More detailed information can certainly be kept under HW adaptation. |
A list of devices with brief information similar as in and then a page for each device would be useful. Something like this but less technical for the first page: |
As mentioned here and here, it could be a good point to have a page listing all active and inactive ports.
Such information are in my opinion relevant:
Possibility is to add some more details about the port, such what is not working if help is needed, etc. Let's use this issue to discuss about it :)
The text was updated successfully, but these errors were encountered: