Difference between revisions of "Where to Report Bugs"

From PINE64
Jump to navigation Jump to search
(changes)
(→‎Overview: wording fixed)
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.
}}
}}


Revision as of 13:32, 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). 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

Issues with the PinePhone and the PinePhone Pro can be reported on the following bug trackers (selection).

Bootloaders and Firmwares

Operating Systems

User Interfaces

Hardware Issues

TBD

Retrieved from "https://wiki.pine64.org/index.php?title=Where_to_Report_Bugs&oldid=12693"