Where to Report Bugs - Revision history

Earboxer: /* Hardware Issues */

2022-07-02T18:26:36Z

Hardware Issues

← Older revision		Revision as of 18:26, 2 July 2022
Line 49:		Line 49:

	===Hardware Issues===		===Hardware Issues===
	~~TBD~~
			The page [[PinePhone Hardware Issues]] can be used to track known problems with the hardware (and how to fix them). If you're not exactly sure how to describe the issue, try the discussion tab for that page, or other community resources.

	=== Accessories ===		=== Accessories ===

Fxc: Fxc moved page User:Fxc/Where to Report Bugs to Where to Report Bugs

2022-04-08T17:21:53Z

Fxc moved page User:Fxc/Where to Report Bugs to Where to Report Bugs

← Older revision

Revision as of 17:21, 8 April 2022

Fxc: Added more information

2022-04-01T23:24:39Z

Added more information

← Older revision		Revision as of 23:24, 1 April 2022
Line 3:		Line 3:
	== Overview ==		== Overview ==

	Issues should '''only''' be reported in the correct '''bug trackers''', not in the community chats.		Issues should '''only''' be reported in the correct '''bug trackers''', not in the community chats. The following list is a selection of common bug trackers.

	== PinePhone and PinePhone Pro ==		== PinePhone and PinePhone Pro ==

Fxc: /* PinePhone and PinePhone Pro */

2022-04-01T23:21:17Z

PinePhone and PinePhone Pro

← Older revision		Revision as of 23:21, 1 April 2022
Line 49:		Line 49:

	===Hardware Issues===		===Hardware Issues===
			TBD

			=== Accessories ===
	TBD		TBD

Fxc: more devices

2022-04-01T23:20:49Z

more devices

← Older revision		Revision as of 23:20, 1 April 2022
Line 50:		Line 50:
	===Hardware Issues===		===Hardware Issues===
	TBD		TBD

			== PineTime ==
			* InfiniTime: https://github.com/InfiniTimeOrg/InfiniTime/issues?q=is%3Aissue

			== PineTab ==
			* Arch Linux ARM: https://github.com/dreemurrs-embedded/Pine64-Arch/issues?q=is%3Aissue+label%3A%22device%3A+pinetab%22
			* Manjaro ARM: https://gitlab.manjaro.org/manjaro-arm/issues
			* Mobian: https://gitlab.com/mobian1/issues
			* postmarketOS: https://gitlab.com/postmarketOS/pmaports/-/issues?sort=created_date&state=opened&label_name%5B%5D=device-pine64-pinetab
			* Ubuntu Touch: https://gitlab.com/ubports/community-ports/pinephone/-/issues?sort=created_date&state=all

Fxc: /* Overview */

2022-04-01T23:10:08Z

Overview

← Older revision		Revision as of 23:10, 1 April 2022
Line 3:		Line 3:
	== 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.~~		Issues should '''only''' be reported in the correct '''bug trackers''', not 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). Reports in the chat are not designated to be a part of that process (until an advanced artificial intelligence some day can evaluate them and automatically ask the user for more details).
	* Talking about an issue and workarounds carries the discussion further away from the actual development and leads to discussions in forums and chatrooms.
	* 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 repetitive for everyone involved and leads to future users with the same or similar issues not getting pointed to the correct places anymore.
	* It is expected that people mentioning issues will also report them properly. Conversations about bugs without reporting them makes users and developers think it is reported already and as a result the issue will never be reported (and therefore not fixed).
	* Unlike many commercial and/or proprietary projects, developers are part of the open community and there is therefore no need of having to solve issues via side channels.
	}}

	== PinePhone and PinePhone Pro ==		== PinePhone and PinePhone Pro ==

Fxc: /* PinePhone and PinePhone Pro */ fixed

2022-04-01T23:08:25Z

PinePhone and PinePhone Pro: fixed

@@ Line 19: / Line 19: @@
 Issues with the PinePhone and the PinePhone Pro can be reported on the following bug trackers (selection).
-===Bootloaders and Firmwares===
+===Operating Systems and Distributions===
 * Arch Linux ARM (DanctNIX): https://github.com/dreemurrs-embedded/Pine64-Arch/issues?q=is%3Aissue
 * ExpidusOS: https://github.com/orgs/ExpidusOS/repositories
@@ Line 57: / Line 44: @@
 * Swmo: https://todo.sr.ht/~mil/sxmo-tickets
 * Ubuntu Touch: https://gitlab.com/ubports/community-ports/pinephone/-/issues?sort=created_date&state=all
 ===Hardware Issues===
 TBD

Fxc: /* PinePhone and PinePhone Pro */ order changed

2022-03-21T13:34:54Z

PinePhone and PinePhone Pro: order changed

← Older revision		Revision as of 13:34, 21 March 2022
Line 25:		Line 25:
	* Crust: https://github.com/crust-firmware/crust/issues?q=is%3Aissue		* 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		* Pinephone Modem SDK: https://github.com/Biktorgj/pinephone_modem_sdk/issues?q=is%3Aissue

			===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

	===Operating Systems===		===Operating Systems===
Line 51:		Line 57:
	* Swmo: https://todo.sr.ht/~mil/sxmo-tickets		* Swmo: https://todo.sr.ht/~mil/sxmo-tickets
	* Ubuntu Touch: https://gitlab.com/ubports/community-ports/pinephone/-/issues?sort=created_date&state=all		* 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===		===Hardware Issues===
	TBD		TBD

Fxc: /* Overview */ wording fixed

2022-03-21T13:32:16Z

Overview: wording fixed

← Older revision		Revision as of 13:32, 21 March 2022
Line 7:		Line 7:
	{{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). Reports in the chat are not designated to be a part of that process (until an advanced artificial intelligence some day can evaluate them and automatically ask the user for more details).
	* 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~~.		* Talking about an issue and workarounds carries the discussion further away from the actual development and leads to discussions in forums and chatrooms.
	* Shared and accepted workarounds don't find their way back into the code and may be accepted as "tolerable evil".		* 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.		* Bug reports in chats are getting scrolled out, repeated and as a result repetitive for everyone involved and leads to future users with the same or similar issues not getting pointed to the correct places 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).		* It is expected that people mentioning issues will also report them properly. Conversations about bugs without reporting them makes users and developers think it is reported already and as a result 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~~.		* Unlike many commercial and/or proprietary projects, developers are part of the open community and there is therefore no need of having to solve issues via side channels.
	}}		}}

Fxc: changes

2022-03-21T13:15:46Z

changes

← Older revision		Revision as of 13:15, 21 March 2022
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?

	~~Reporting issues in the community chats is actually a bad idea for multiple reasons:~~

	* 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