![]() First, Wolthera and Halla sat down together to investigate our closest competitor. So earlier this year, we sat down together, every developer who could make the virtual meeting to discuss what fun stuff we wanted to work on after all the pandemic depression, resource system rewrite and bug fixing. Some for nearly two decades, in fact, and we know what we want Krita to be. Some of us have been working on Krita for more than a decade. Working in response to bugs and feature requests is also reactive: it prevents the Krita team from developing a vision, and then using that vision to develop and improve Krita.Īnd that’s just frustrating. And since there’s so much of it, it’s not possible for the Krita developers to meaningfully engage with all the ideas artists bring to the table. That is not only discouraging, it is also a big timesink. Say, on average, half an hour of engagement with the report and reporter before the real work starts, just triaging these bugs takes 50 hours a month!Īt the same time, every artist who starts using Krita will have ideas that must be implemented, so there is a never ending stream of feature requests, often of the form “Photoshop has X, it’s incredible that Krita still hasn’t X, too!”. ![]() ![]() Even if the bug report is more a cry for user support than a real bug report, it will take time to evaluate and close. Not that there haven’t been other things happening!Īnd not just bug reports, though with on average a hundred new bug reports a month, that’s taking a lot of work as well. Krita 5.1 is nearing its release, and working on that has claimed a lot of our attention. What the Krita Developers Are Up To, Part II
0 Comments
Leave a Reply. |