Realising after some time that itās possible to consult bug reports but not participate / create a bug report.
Searching on PureOSā wiki and not finding any mention of bug reports either.
Coming on this forum to explain my frustration on something that is generally well indicated
Suggestions
If users cannot create new accounts to report bugs, I respect that but it should be clearly stated either on the PureOS website or on the Bug Tracker website instead of leaving the users confused.
I think it is more complicated than that. It is āclosed but not closedā. The antecedent āIf users cannot create new accounts to report bugsā is not necessarily true. Itās just that it is now harder to get an account than it used to be - and if the reason that it is now harder is because of malicious parties, you donāt necessarily want to make it either easy or obvious to those malicious parties.
So in this case the score may be: malicious parties 1, all the rest of us 0.
I think you want the āStandardā login option, not the LDAP login option, but you should contact support (support@puri.sm) because, as I understand it, requests for accounts have to be approved manually anyway.
Also, if this is a bug in the hardware, that particular mechanism for reporting may not be the right one.
What hardware (i.e. what model) are we talking about?
Thank you! But how it works? For example Iād like to report mozilla firefox settings window bigger than screen that doesnāt resize neither using purism mobile tool. In which section Iād report it?
Iām not sure. I often have difficulties finding the correct project/repository as well. The structure of the groups and projects in GitLab confuses me. @jonathon.hall: what is the correct place for reporting issues, I think you wrote it once in a blog, but I could not find it any more.
Edit 2: I found the blog. It states: āAs you try it out, review the known issues and let us know about your experience.ā But this seems to be in the context of the Crimson alpha release. Iām not sure if other issues should go there as well, like your mentioned Firefox issue.
Youāre right we have some cleanup to do in GitLab, and progress is being made, but weāre taking a slow and deliberate pace since it can be disruptive to reorganize repositories.
(I put this in the specific repo since in this case itās clear that this issue will be fixed there. You can always report issues like this in Issues Ā· PureOS / Tasking Ā· GitLab, and weāll move them to the specific place.)
