Krita Team Seeking Sponsorship to Take Krita to Next Level

At the KOffice meeting in Oslo the Krita team had a meeting to put the finishing touches to an ambitious plan. On hearing about it the Dot managed to lure two of the Krita developers in a separate room to question them and find out what was going on. Nobody got seriously hurt in the process.

We spoke with Krita developers Boudewijn Rempt and Lukáš Tvrdý.


Variety of Sumi-e brushes by Lukáš

User Experience

Jos: I sensed some excitement from the Krita developers, what do you guys have in store?

Boudewijn: Well, we realized while working on Krita 2.1 that it was getting to that point where an end user could basically work with it. So we were looking for the next challenge.

Lukáš: It was about that time when I got in contact with David Revoy. He's the concept artist who has been working with the Blender team on Project Durian: their latest open source movie project. I asked him for his opinions on Krita to get some feedback from a professional. I like for people to use my applications, and David has plenty of experience with various tools like the Gimp and MyPaint. His opinions seemed very valuable to me for making Krita ready for actual users.

Jos: And? Did he have experience with Krita?

Lukáš: Yes, actually, he had tried it a while ago. It didn't work for him, even though he liked our interface a lot. The main issue was not really the lack of great features and tools but the slowness of the painting.

Boudewijn: But he was willing to provide us with feedback on the issues he bumped into. So that's when we decided we should put a strong focus on getting Krita ready for him. If he can work comfortably with Krita, so will many other users, both casual users and professionals...

Challenge

Lukáš: That was a challenging goal, but also very exciting. I had been working on a bunch of cool brushes, using the tablet I've been loaned after a previous fundraiser and I thought I could shift my focus a bit.

Boudewijn: Yes, but frankly, the issues David bumped into would need more than a few casual hours a week to fix them properly. The speed issues for example need deep changes in the code. This could take a long time especially with Krita and KOffice being a moving target all the time.

Lukáš: So I mentioned to the team that since I'll have a slow period the first three months of the year I might be able to spend a serious amount of time on this. In 3 months I could certainly fix the performance and usability issues David encountered.

Pledge

Boudewijn: But of course Lukáš would have to find a job to be able to pay his bills - after all, he's a student. So we decided it was worth it to try and raise money to let Lukáš work on Krita full-time for three months!


Krita Art

Jos: So that's the plan - raise money and get Lukáš to work on Krita full-time?

Boudewijn: exactly. Cyrille Berger will go and meet David Revoy next week to talk about the issues in Krita. David has agreed to help us get Krita to the point where a professional like him can use it comfortably. It'd be really cool if for example the Blender artists can use Krita for their next piece of art!

Lukáš: This is only possible because we've been focussing on fixing bugs and improving stability in KOffice so much lately... By restraining ourself to that instead of working on new cool features, we've created something which is usable. But this brings out the performance issues and missing functionality.

Lots of work ahead

Boudewijn: With David's help we have made a specific list of tasks to be accomplished, with a timeline. We'll of course run the results by David every now and then. Lukáš will know exactly what he's supposed to do and in 40-80 hours a week he can get them done.

Lukáš: wait, 80 hours? We didn't talk about...

Boudewijn: Don't worry, if you don't manage to finish a target during the week, the weekend has another 48 hours!

Lukáš: Well, hum. Anyway, we have a realistic plan. We'll start on the performance issues, the fixes for that should make it into the KOffice 2.3 release. Then 4 months later, the 2.4 release will contain the usability and feature improvements - all of this should be in the hands of the users around the end of August or September.

Jos: Next year?!?

Boudewijn: Hence the 80 hours.

Lukáš: It is doable. I'm not alone, the other Krita developers will of course continue working on various other improvements as well.

Boudewijn: And we know what Lukáš can do, he's very good. He has shown that in the earlier summer of code projects and his work with the tablet support, the new brushes, 3D cursors and the infinite canvas. You can look up the code if you like.


Bitmap Spray (more here)

Jos: Sounds good. So where does the money come from? I've seen Lukáš eat...

Boudewijn: Hehe... Well he lives in the Slovak Republic. Life's not that expensive over there. We aim to raise about 2000-3000 euros. And the Krita team has decided to put a bit of personal money in as well. If we manage to raise more money, it'll be used for sponsoring Lukáš for a longer period.

Jos: So this is really a team plan?

Boudewijn: Yes, absolutely, everybody's on board here. We all see this as a great opportunity to raise the bar for Krita and move to the next level. For us it is about enabling a team member to work on a specific set of improvements full time to the benefit of the whole product. The money raising will probably have to be an ongoing effort but I think the community will help us out here.

Lukáš: yeah, everyone really wants to do this. The other team members can can continue to work on the cool things they have been working on, I'll be doing this as if it's a job - do the boring optimizing and usability work. It'll still be a lot more fun than getting a random student job around here for three months...

Boudewijn: And it's good for his resume, I suppose.

Why donate?

Jos: So, sum it up for us, why should the community support the Krita team with this plan?

Lukáš: If you want to use krita on a professional level!

Boudewijn: It is cheaper than a licence of Corel Painter. Not that I would object to any donations the size of a Corel Painter license...


Will code for food!

Boudewijn: And it can fill in a gap in the Free Software world. MyPaint is here for quick sketching, and Gimp is real good at image manipulation but we don't have a good digital painting appliation with all the features artists need. We have been working on this many years and we're close - this is the chance for the big leap forwards. If you care about this, a donation will make a big difference. We can do this!

Jos: Sounds like a plan. Thanks for the interview and of course for the work on KOffice and Krita!

You've all read it, go on to the Donations page and help make Free Software provide a real alternative for digital artists! Be sure to notify others and spread the word...

Read more on the Krita site.

Help raise Krita to the next level and make a donation at www.pledgie.com !

Dot Categories: 

Comments

Donated a rather feeble €10. I'd give more, but I'm a bit tight on cash.

Anything that can put KOffice on OpenSUSE/Kubuntu/Other KDE Distro's default installs, I consider a good thing!

Every donation makes a hero in my books, and 10 euros definitely helps. What makes a bigger difference to Krita is *whether* people support Lukas rather than how much (although multi-million euro donations happily accepted ;-)

Thanks once again for choosing to support Krita dna open source art creation. :)

It's not feeble, it's awesome!

I remember the fundraising campaigns for Quanta Plus... It is not an easy job, but you are doing great. Good luck with it, and make a Krita that rocks.

I will donate EUR 20 (with pleasure!). However, I do not want to use Paypal. Is it possible to donate for Krita via KDE e.V.? Moreover, donating to KDE e.V. would allow me to donate more (as donations are tax deductable).

Through the e.V. is not possible, because this drive is about getting the money to pay someone to do work, instead of things like travel or hardware. If you mail me ([email protected]), we might be able to work something out nevertheless.

Albert Schweitzer said: The little that you can do is a lot.

I am giving 10 Euro too.

Yours,
Kay

If the problem is trying to release a stable version every 4 months, then I think the thing to do is to is too split off from the KOffice suite.

Also, I want to see koffice to succeed. And this is not because I want a cheap program, because I just grudgingly purchased a student edition of photoshop recently. No I want something that will work on my platform of choice, and without having to e-mail a picture of my student ID to get my CD key.

Yes, KOffice has some very nice features. The GIMP has been missing adjustment layers, a feature that photoshop implemented a while ago and that I consider indispensable. Every time that I see that a new version of KOffice has been released, I immediately try out Krita hopping to see some speed improvements, but I've been mostly disappointed.

Why do you think the 4-month schedule is a problem for Krita? I certainly didn't get that impression so the article shouldn't give it either ;-)

Yes, the speed is a big problem, as noted - and the first thing Lukas will work on.

Improving the performance of Krita is the first goal of this project: we do recognize that Krita is too slow for many operations and have already done some research to find the bottlenecks. You can read all about it in the action plan for Lukas: http://wiki.koffice.org/index.php?title=Krita/ActionPlan.

It seems like a lot of the work is going into brushes. The slowness that I was talking about was the preview for effects like levels or curves. Also, if I hear of anything interesting during the time when Lukas is hacking away, then I might have to build from subversion.

One of the advantages of Krita over Gimp was it's simpler and nicer UI. But I've been using Krita 2.1, and man, it is horrible!

- selecting region is buggy as hell (you can't select pixels that are on the edges of the canvas) and the selection looks very strange

- inserting text is ilogic, why there is not a button in the tools for text?

- I can't figure out how to configure the eraser to clear just ONE pixel at time, and I want it erased 100%, not being more clear/translucit and having to click button 5 times to fully clear it. (if possible, the configure tool UI is a mess, because I could not find it after a lot of tries)

- why showing a export dialog every single time I save a png? Once for session is good enought.

- tool configuration aren't saved. Why should I configure the pencil brush to just draw one solid pixel every single time I open a new krita window?

That said, I hope Krita have a plan to address those issues, if true, then I'm willing to donate. But today, I don't see a plan to fix it's UI. SHould I post all those issues on bugs.kde.org or are you aware of that?

So, is there a plan for Krita future? People needs to see what they'll get if they put their money in :)

Yes, we have a plan. A fairly detailed one even. Lukas' action plan is here: http://wiki.koffice.org/index.php?title=Krita/ActionPlan. It has two phases: performance work and usability work. We've already received enough donations to start doing the performance work starting in January (Lukas first needs to finish his exams), and we are starting to get there for the usability work.

The general plan for 2.2 is at http://wiki.koffice.org/index.php?title=Krita/Roadmap22.

However, this doesn't answer most of the points you make above. Some I agree upon, some I'm afraid we'll have to agree to disagree on.

* selections: Sven Langkamp is working on this, so that should indeed be improved.

* location of the text tool/shape. This is the result of a long discussion in KOffice as a whole. We don't have one text tool as such: we have text shapes that can be manipulation with a number of tools. For instance, the standard text shape has an editing tool and a paragraph settings tool. Then there is the artistic text tool that enables you to set type on a path. We chose to make all shapes available through a shape selector instead of putting them all as creation tools in the toolbox, because the toolbox quickly became very crowded. I'm afraid that this is settled for now, pending some future KOffice-wide usability and interaction review.

* pixel eraser. It's a general issue with painting tools in Krita that they are meant for painting, not for changing the value of single pixels. There is a bug for the pencil brush engine to make neat, precise, aliased lines. Together with the "erase" blending mode, this should do what you want, when it is fixed. See bug https://bugs.kde.org/show_bug.cgi?id=148207.

* showing the export dialog. Well, in general, the work flow we aim at is for someone working on a single image for a longer period of time, saving it as .kra often, and only in the end exporting it. Krita isn't a photo manager like Digikam. Still, it's a valid point -- so we'll have to think about it.

* tool configurations not being saved. That's actually my fault. Back in 2003, Krita had some rudimentary code to save tool configurations to the settings file, but that didn't work, and I kept getting confused by gimp remembering my settings when I started it again, so I concluded it was a bad idea and removed the non-working code. There is a bright side here, though, because we're working on making it easy to save and restore brush settings, which would certainly meet the requirements you state above: you will be able to define a one-pixel hard eraser "preset", save it and retrieve it from a combobox. It will work a bit like Corel Painter's brush selection works now.

Hope that clears up your questions!

Well, it yes helped to solve my questions, and I am kind of amazed that you have a plan! 90% of open-source programs out there (and that includes kde and plasma) do not have a clear vision of what they want, but you do!

Congratulations and keep the great work :)

Btw, the particular point you made about selecting pixels on the edge of the canvas, if you can reproduce that reliably, could you add a bug for that to bugzilla? I cannot reproduce that myself.g

Well, if the linked plan is not enough, then perhaps I can offer a few words of reassurance. I've been hanging around KDE for almost 10 years now, and Boud is someone I'd trust 100%. If he says it's good, that's good enough for me to pledge my €10.

The KOffice team have past experience with this sort of sponsorship, for example through KO and work on KWord and the ODF filters, so they know how to make it work.

Well more than three quarters of your financial target in four days is great going! Clearly the community is right behind this project.

Its great to see us coming together to provide resources where they're needed!

Users are clearly willing to pay for good features. Maybe more KDE devs should seek such sponsoring.

- Advance the semantic desktop.
- Expose BtrFS features in KDE.
- ...
I think the list goes on and on.

Maybe that is a new business opportunity for KDAB. I know the numbers have to be much higher, but still. For really popular KDE features the community would be willing to easily spend 10K I guess.

It obviously worked this time with a clear plan, a resource in place a known set of goals etc etc. It would be interesting to see if this model however would continue to work if it became widespread.

I could imagine a scenario in which 100 different ideas were put forward for sponsorship, each attracting a few donations here and there but none of them reaching the critical mass needed to actually allow someone to dedicate substantial chunk of their life to a given piece of work...

This might be one of those practices that needs to be infrequent to remain effective (I'm not trying to come off as cheap here, I already donated $30 ;)

edit: a thought just occurred, what might work is to have a regularly spaced donation drive, say every 3 months for example; people could submit proposals, which could be voted on. The winning proposals could then be subject of the next round of donations.

Proposals would have to be cleared by the project maintainer (no point coding up something that won't be merged) and should be of the standard set by the Krita team, with clear goals, an available and willing coder etc.

Performance, stability and usability issues are not always the most fun things to work on, but someone has to do it.

I'm not a Krita user, but with my rather smallish donation I want show that I support the cause, and that I'm willing to do it for other projects as well. If there's a noticeable improvement in e.g. performance, it's worth every cent.

(Just don't do it too often, a poor student like me also needs food. ;)

i never used krita, but i gave money nevertheless :)

(not because the app is not good, but i like the cause...)

keep up the good work!

I think it's a very good idea to raise money to pay Lukáš to improve Krita.

I don't really want to use KOffice (I like OpenOffice more), but Krita is an exception. It's the best. Gimp is much too hard to use.

I am a bit out of money so I can't donate much, but it looks like by tomorrow you will have enough money raised anyway.

And with €40 left over to spend on champaign... ;)

Cool huh...

If ppl continue to donate, the Krita team can keep Lukas working for another few months!

if we can get a rate of €1000 a month we can keep him employed forever. :)

There have been (and probably still are) schemes like this before, where you could pledge an amount of money to have certain issues addressed or features implemented in KDE software. I'm pretty sure there was something like that for KDE-PIM. Unfortunately, it did not work. At least not for me.

I think that in general, things like this could work, but you probably should not expect to have it raise enough to work full time on it. I am happy to see that this time around, it seems to work out pretty good! I think that also has to do with the clear focus and the publicity around it.

I'm sure it also feels very good for the developers behind Krita to see this work out so well! It must be very satisfactory to see that in a matter of days, the target was met. That does mean the community appreciates your project, I'd say.

edit: this should have been a reply to Thu, 2009/12/03 - 9:32pm — kragil: "Should be done more often".

that is really nice.i will try to contribute too