On Sun, 2014-01-05 at 00:49 +1100, Nathan Hurst wrote:
and I wonder whether this has any messages for inkscape's use of bzr.
Actually, the most interesting part for me was about managing project direction:
We lost sight of what mattered for our users, focusing on features that were nice but perhaps not as necessary as we thought. We overengineered. We didn't get rid of the crufty unnecessary features. It's harder to comprehend, contribute to or fix performance issues in a large layered codebase. And the larger a codebase becomes, the larger the surface for bugs, the harder it is to refactor.
I think Inkscape is on the winning side of cruft management overall. But it's something I'm aware of as exciting features are always going to have the most energy.
As for focusing on users... that's a hard problem for Inkscape since there's no nice big juicy connection there between the two.
kinda makes me happy we do have really smart people who have a good sense of direction in Inkscape.
Martin,