I’ve the same problem. Does a replacement for that GitLab instance exist anymore, even for solely the FP2? I remember being able to visit it a year ago, and Discourse isn’t a particularly competent issue tracker in the meantime, whereas ZenDesk is both private and entirely overwhelmed, (to the point of non-response to any technical report).
Even if FP had considered a FOSS OS unmaintainable, I don’t see why a tracker isn’t desirable. ZD is a private and/or more formal version of Discourse, which are both support forums. They are not issue trackers, not least due to the thread default to lock threads after a few months, which would be nonsensical on an issue tracker.
Open source OS efforts were superseded by Murena involvement and FPOpenOS is probably deprecated and replaced by /e/OS as the official Opensource OS for Fairphones
Why going back to this old broken record over and over again.
Both is gone since 6 years and the reasons have been speculated in circles many timea in the forum and both is off-topic here in this (4 year old) topic.
@yvmuell, a search for about 5 relevant terms didn’t return anything. If you have relevant information, I’ll be glad to see it. Thanks.
I don’t believe so. I’m primarily interested in the issue tracker, which is a normal accompaniment for an OSS project. That this topic discusses its license and mentions the tracker itself demonstrated to me that my question might be best placed here.
Had I created a separate thread, all anyone would have done is speculate. I have less interest in speculation.
Regardless, us discussing this is what provides noise to the thread. I wouldn’t have minded waiting a few years for a response, or not having been responded to. It was solely pitted for the eventuality that someone knew the answer, which @koumilak helpfully did, for ½ of it.
@yvmuell, that’s why I directly asked those who would have to have been involved. It wouldn’t be worth a ticket on ZD, since they’re incredibly busy, and the information wouldn’t be public.
Thanks, though, because this at least leaves an indicator at the original thread. I think this is perfect now.
@Meaghan, that kind of insane triage policy is why they’re so swamped. If they were to utilise an issue tracker, the onus would be on the user to locate a relevant ticket for their report, rather than always file a duplicate. Imagine if every user filed an issue for each issue they encountered! The amount of time wastage on both sides would be extraordinary.
@rokejulianlockhart kindly not again this broken record and as it was off-topic I moved it again. Kindly refrain from placing this repeatedly in various topics. @Meaghan the FP4 had no real issue tracker especially not what @rokejulianlockhart is looking for.
@yvmuell, it appeared relevant in that thread. I’m glad that you merged them, but is a single post’s digression a problem?
Especially, because it’s not per se about what the topic of this thread is. This thread is about why the FP2’s GL instance was dismissed, whereas that comment was an observation about ticket triage policies, where I merely mentioned the concept of a public issue tracker, because we were discussing a software bug.
Well even the other point was rather off-topic in the topic it was placed in.
Sure it was already touched in this topic, still I think we should rather focus on topic especially as there are several other general topics to discuss support times. If you want it moved elsewhere send me a PM.
I would like to help @rokejulianlockhart. Can you please tell me what seems to be the issue? I am a bit lost in all these threads. I will try to get more info internally to help you out!
@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.
I checked internally, when FP2 reached its end-of-life, we closed it down as part of that process, but all the content was backed up and is still accessible internally if needed.
For newer devices, issue tracking happens differently: private issue trackers are used, to which only a select number of forum users participate. You can see them in the category “Participate”.
@anon76468197, that doesn’t make an awful lot of sense to me, considering that many an issue tracker merely requests that users discuss a problem on Discourse first before elevating it to the tracker. [1] Having private reporting channels means an enormous duplication of effort on both the users’ and triagers’ sides.
Surely, if this worked, other OSS organisations would copy it. They don’t appear to.
That’s good to hear, although because it’s not indexed, it’s not much use to anyone else anymore. FB ZenDesk reponse times are so slow that accessing any of that documentation would be nigh equivalent to an FOIA request. [2]
