On Thu, Jan 18, 2018 at 10:56:12AM -0500, Martin Owens wrote:
Add also the question: Should we have one system for users and another for developers?
There are pros and cons to a split, but if we have a technical issues tracker on gitlab and a user focused needs tracker somewhere else. I could see the benefits.
From what I've seen of how our users interact with the bug tracker, this
is certainly the direction I'm leaning. We discussed this a fair bit at the last Vectors team meeting, and hope to see some refinement of this approach.
However, at this stage I think we should keep all cards on the table, and focus on brainstorming and analysis. There's a number of different stakeholders, and it'd be too easy to jump to a solution that ends up being a poor fit for many (or too challenging to get implemented).
Do we have a wiki page setup for discussing/brainstorming bug tracker ideas? Maybe that'd be a good starting point?
Bryce
Best Regards, Martin Owens
On Wed, 2018-01-17 at 17:01 -0800, Bryce Harrington wrote:
let me know. The next steps are analytical -- essentially requirements gathering, and assembling a listing of questions that need researched.
Should we move bugs to gitlab? Or stick with Launchpad? Or investigate other bug systems? Or something else completely?
There's several different constituencies with differing needs that'll need to be balanced. It'd be great if we could find a plan that works well for bug reporters, triagers, and developers.