@anon76468197, thank you! For the fp2, a GitLab instance was once provided at issuetracker.fairphone.org. In case you’re unaware, GitLab is an issue tracker. If you’re unfamiliar with that concept, if you look at Fairphone’s GitHub repositories, it was similar to that: technically an asynchronous forum, but one significantly more geared to bug tracking than this Discourse instance is. (As an example, to my knowledge, solely FP and Discourse themselves utilise Discourse as an issue tracker.)
It’s also a source code repository. Currently, Fairphone utilises a combination of Gerrit and its own solution to distribute and maintain its code. That’s veritably arcane; comparable solely to Google’s AOSP development infrastructure, but worse. The FP2 GitLab instance was a significant improvement over it, that I expected FP to migrate to (as Google, amongst others, have recently done).
Strangely, when this issue tracker was brought offline, no notification was provided to the community, thereby denying them the ability to export their old, filed issues, etcetera (to my knowledge). I’ve always wondered why login wasn’t merely disabled so that old URIs to its issues would remain active, or, barring that, its issues weren’t transferred to equivalent GitHub repositories under the Fairphone organisation.
As an example, if you’ve access to FP’s ZenDesk instance, compare it with:
I presume that the ZenDesk ticket lacks all formatting. It’s also private.