Difference between revisions of "Where to Report Bugs"
Jump to navigation
Jump to search
(Added examples) |
(changes) |
||
Line 1: | Line 1: | ||
Reporting bugs is a great way to contribute and to help bringing order at managing and solving issues. | |||
== Overview == | == Overview == | ||
Issues should '''only''' be reported in the correct '''bug trackers''', not in the community chats. The reasons for this can be found in the following information box. | |||
{{hint|Why shouldn't I report issues in the community chats? | {{hint|Why shouldn't I report issues in the community chats? | ||
* Development takes place in platforms such as GitLab, sourcehut and Github with a certain procedure (issue reports, commits, linking to the issues and marking them solved). Chat reports are not a part of that procedure. | * Development takes place in platforms such as GitLab, sourcehut and Github with a certain procedure (issue reports, commits, linking to the issues and marking them solved). Chat reports are not a part of that procedure. | ||
Line 14: | Line 16: | ||
== PinePhone and PinePhone Pro == | == PinePhone and PinePhone Pro == | ||
Issues with the PinePhone and the PinePhone Pro can be reported on the following bug trackers (selection). | |||
===Bootloaders and Firmwares=== | ===Bootloaders and Firmwares=== | ||
* U-Boot: | * U-Boot: TBD | ||
* Tow-Boot: https://github.com/Tow-Boot/Tow-Boot/issues?q= | * Tow-Boot: https://github.com/Tow-Boot/Tow-Boot/issues?q= | ||
* Levinboot: https://gitlab.com/DeltaGem/levinboot/-/issues?sort=created_date&state=all | * Levinboot: https://gitlab.com/DeltaGem/levinboot/-/issues?sort=created_date&state=all |
Revision as of 13:15, 21 March 2022
Reporting bugs is a great way to contribute and to help bringing order at managing and solving issues.
Overview
Issues should only be reported in the correct bug trackers, not in the community chats. The reasons for this can be found in the following information box.
Why shouldn't I report issues in the community chats?
- Development takes place in platforms such as GitLab, sourcehut and Github with a certain procedure (issue reports, commits, linking to the issues and marking them solved). Chat reports are not a part of that procedure.
- Talking about an issue and workarounds carries the discussion further away from the actual development and leads to discussions in forums and chatrooms, in contrast to bug trackers.
- Shared and accepted workarounds don't find their way back into the code and may be accepted as "tolerable evil".
- Bug reports in chats are getting scrolled out, repeated and as a result get annoying for everyone involved and leads to future users with the same or similar issues not getting helped anymore.
- It is expected that people mentioning issues also report them. Chatting about them without reporting them makes everyone think it is reported already and then the issue will never be reported (and therefore not fixed).
- The transition from community to developer are fluent, we don't have situations of "they above" versus the "we the users, who have to help themselves" here, like other commercial projects have. Don't even think about trying to bring such mindsets into the community.
PinePhone and PinePhone Pro
Issues with the PinePhone and the PinePhone Pro can be reported on the following bug trackers (selection).
Bootloaders and Firmwares
- U-Boot: TBD
- Tow-Boot: https://github.com/Tow-Boot/Tow-Boot/issues?q=
- Levinboot: https://gitlab.com/DeltaGem/levinboot/-/issues?sort=created_date&state=all
- Crust: https://github.com/crust-firmware/crust/issues?q=is%3Aissue
- Pinephone Modem SDK: https://github.com/Biktorgj/pinephone_modem_sdk/issues?q=is%3Aissue
Operating Systems
- Arch Linux ARM (DanctNIX): https://github.com/dreemurrs-embedded/Pine64-Arch/issues?q=is%3Aissue
- ExpidusOS: https://github.com/orgs/ExpidusOS/repositories
- Fedora: https://github.com/nikhiljha/pp-fedora-sdsetup/issues?q=is%3Aissue
- Gentoo: On the bug tracker of the corresponding unofficial overlay
- GloDroid: https://github.com/GloDroid/glodroid_manifest/issues?q=is%3Aissue
- Kali Linux: https://github.com/Shubhamvis98/kali-pinephone/issues?q=is%3Aissue
- LuneOS: https://github.com/webOS-ports/meta-pine64-luneos/issues?q=is%3Aissue
- Maemo Leste: https://github.com/maemo-leste/bugtracker/issues?q=is%3Aissue
- Manjaro ARM: https://gitlab.manjaro.org/manjaro-arm/issues/pinephone
- Mobian: https://gitlab.com/mobian1/issues
- Multi-distro demo image: -
- Nemo Mobile: https://github.com/nemomobile-ux/main/issues?q=is%3Aissue
- NixOS: https://github.com/NixOS/mobile-nixos/issues?q=is%3Aissue
- OpenMandriva Lx: -
- openSUSE: https://gitlab.com/slem.os/slem.os/-/issues?sort=created_date&state=all
- postmarketOS:
- PureOS: unmaintained
- Sailfish OS: https://github.com/sailfish-on-dontbeevil
- SkiffOS: https://github.com/skiffos/SkiffOS/issues?q=is%3Aissue
- Slackware: -
- Swmo: https://todo.sr.ht/~mil/sxmo-tickets
- Ubuntu Touch: https://gitlab.com/ubports/community-ports/pinephone/-/issues?sort=created_date&state=all
User Interfaces
- Plasma Mobile: https://invent.kde.org/plasma/plasma-mobile/-/issues
- Plasma Mobile applications: https://invent.kde.org/groups/plasma-mobile/-/issues
- Phosh: https://gitlab.gnome.org/World/Phosh/phosh/-/issues?scope=all&state=all
- Phosh projects: https://gitlab.gnome.org/World/Phosh
Hardware Issues
TBD