On Thu, Jan 18, 2018 at 04:05:23PM +0000, John Cliff wrote:
If we do move them can we get back to separate categories of bugs and feature requests like we had on sourceforge before we went to launchpad? I know we have blueprints on there too, but they always seemed over complicated for simple stuff. Never liked the way launchpad merged them.
Yes, and I've heard this stated from a number of others too.
While moving to launchpad from sourceforge was a benefit, conflating these two types of issues was a drawback. The loss of being able to prioritize feature requests as we'd done in SF was particularly unfortunate.
I had high hopes for the Blueprints system, but frankly the design was flawed and the implementation of it never really evolved or even kept up with other advancements in LP. It had potential, but I have a lengthy list of changes I would like to have seen to make it useful to us.
Ideally, I would love to have an entirely separate system for organizing feature requests. It would allow us to prioritize and refine the ideas, organize them into project lists for GSoC and the like, feed into our Roadmap, facilitate crowdsourced funding, and stimulate development activities.
Anyway, all cards on the table for now, but I do suspect splitting these apart is going to be on everyone's must-have list. :-)
Bryce
Cheers
John
On 18 Jan 2018 3:57 pm, "Martin Owens" <doctormo@...400...> 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.
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.
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel