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.

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@...1656...784...sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel