Please report issues to GitHub Issues (feel free use Forum Bugs as well) and label issues with camera. You can also filter by label. There is droidmedia where you can report issues close to Camera hardware adaptation but generic issues should go to GitHub issues.
Regarding contributing see details from Notes app annouchement. You’ll find more details from following link:
Happy hacking and let’s make the native Sailfish Camera to flourish!
@Jolla is there a wiki or something?
It would be great to have tables for devices and current status of features as well as a table to show the licences of the features so we can have a quick overview of the current status of this wave of open sourcing.
Pinned threads could also work but then the community can’t help
Thanks and yet, I still think a table would be better as new columns like original licence, new licence, date of change, planed strategy, planed date of change, blocking (like QT upgrade) and more. Also links to pages explaining, what the item is, what it does, where the repository is located …
would be immensely more valuable information then just a list of items and the current licence.
I don’t think we create that kind of table for tracking packages. If we’d have one, it would just get outdated (maintenance burden) and this way generating more problems. Prefer sticking with rpm --qa --queryformat (short version --qf). If you’d like to know repository location, you can add %{url} to the query. Let’s say that there is in an an error in the repository url, primary source to be fixed is the spec of the package.
One could create a nice command line command to create pretty printed table.
The idea would be a wiki, where the community and non programmers could contribute to maintain it. @rainemak would just need to drop the info and/or can also input stuff like ETA dates.
It’s just hard to find all the info and have an overview of the state of things for devices and packages here in the forums, documentation and release notes.
Ah nice, I din’t notice that it’s managed via GitHub. Not quite as friction less as a wiki but will do.
As soon as I find a moment, I will put a table together for the Devices and Components and hand in a pull request. I guess next would be a pinned entry here with a invitation to keep it up to date for the community by the community.
I just noticed by following the links, that the forum has a wiki function: Community Hardware Adaptations BTW, why isn’t that one pinned?
indeed and finally s.o. listened to the committers of this fine community !!
Next choose Fairphone as your next future partner to run and experience SailfishOS as it really should be for the upcomming future : beautiful - straight-forward - privacy- and sustainability-respecting to further enhance the recognition and philosophy behind this fine piece of independent, European heritage of OS-craftsmanship
To sad for ending up as just a tool for nerds or autocracies ( which certainly are not two of a kind )
. Please find it from GitHub - sailfishos/jolla-camera: Camera application for Sailfish
!
