Thanks for reply
Based on that logic you'll be using Mantis indefinitely (e.g. in 10
years) because new issues are created there
Simply request new issues are created at GitHub and if there are GitHub
duplicate issues then cross-link the Mantis issue until the issue is
resolved
If it takes 10 years to close all Mantis issues then no problem but at
least you won't have made it hard for the community to create new issues
for a further 10 years from now
FYI I have no affiliation with GitHub but I'm sure _any_ modern issue
tracker will be a UX improvement on Mantis (sorry!). Also GitHub, GitLab
et al. all offer a degree of content portability (e.g. issues) for 10
years from now when you move to the next issue tracker 🙂
//
Yours hopefully
On 22/05/2019 15:41, Francis Lachapelle ([email protected]) wrote:
Hi Lewis
On May 12, 2019, at 11:08 PM, Lewis Dexter Litanzios ([email protected])
<[email protected]> wrote:
Apologies if this has been mentioned before - I tried to search your mailing
list archive but surprisingly no results
Why is SOGo not using GitHub Issues - you obviously host [c]ode there so why
not use their vastly better issue tracker?
I just started vetting SOGo web mail as a Thunderbird replacement and created
my first [i]ssue today. While interacting with GitHub's issue tracker is
geneally pleasant UX using your issue tracker is painful! I made a typo in my
issue which I want to correct and there doesn't even appear to be a way to edit
the issue once submitted. This is basic stuff.
You have a great product and what seems to be the best chance of a FOSS gmail
replacement - please prioritise making it as easy as possible for contributors,
including a better way to report and manage issues
I have a ton of issues to report but unfortunately I'll seriously have to
consider the time burden in future
I understand your concern. We're big fans of Github too. However, we started
SOGo at about the same time Github was founded, and Mantis (the bug tracking
system we use) seemed the best option; it was open source, mature, and could be
deployed on-promise. A few years later, when we moved the source code to Github
(anyone remembers monotone?), we decided to keep Mantis because of the enormous
quantity of tickets already in our system.
Francis
--
logo <https://ldexterldesign.uk>
--
[email protected]
https://inverse.ca/sogo/lists
