On 5 June 2016 at 06:58, Bryce Harrington wrote:
> On Tue, May 31, 2016 at 02:40:01PM -0400, Martin Owens wrote:
>> Although we encourage bug fixing socially ;-) so if you've written some
>> code this year, please please fix some bugs for the next release. My
>> own personal plea which will hopefully encourage me to also fix some
>> bugs for the release.
>
> I'd love to hear ideas on how we could stimulate better focus onto bug
> fixing (and general code cleanup / refactoring), particularly as we
> advance towards 1.0.

How about something like Bugs Ahoy[1], which is used by Mozilla to
track the bugs and features related to the interests of the users and
degree of complexity?
That doesn't have to be a separated website but could just be a page
in the wiki categorizing bugs a bit.

Sebastian

[1] http://www.joshmatthews.net/bugsahoy/

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel