How can I get reported Abrowser issues looked at?
- Anmelden oder Registrieren um Kommentare zu schreiben
I recently created 2 issues regarding Abrowser[1][2]. It's been ~2 weeks since then and nobody seems to have read them. I also wanted to try reporting on Trisquel's Gitlab[3] but couldn't because registrations are closed. I asked for an account as recommended there but received no response yet. In this case, what would be the best way to report the issues I found?
Btw, does anybody know where exactly the patches to make Firefox into Abrowser are maintained? I can't seem to find an Abrowser repo on Trisquel's Gitlab o.O
[1] https://trisquel.info/en/issues/28767
[2] https://trisquel.info/en/issues/28768
[3] https://gitlab.trisquel.org
Hello,
About the issues, they are open to be reviewed by anyone, depending on the context of the issue itself (if there is something to add) and availability I comment on them, but as a rule of thumb issues will take time to answer, that's for sure.
Due to spam issues, gitlab automatic registrations are closed.
A workaround is on the making to allow new issuers to sign up soon, over time, gitlab would be the default place to report any issue, as the current issue tracker will be closed on the next website overhaul.
Most of the packages maintained by trisquel are found on the package-helpers repository, abrowser binaries are compiled from the firefox source so you'll find the helper as make-firefox.
https://gitlab.trisquel.org/trisquel/package-helpers
Regards
Thanks a lot! :)
- Anmelden oder Registrieren um Kommentare zu schreiben