Join

  • Share this on:

 Krita is always welcoming new contributors! As Krita is a huge and ambitious project, there is always a lot more work than the small core team can handle. The Krita community is very open, welcoming and supportive. We are in particular looking for contributors with a good sense of initiative and commitment (so please don't disappear without warning halfway through the job!). No resume needed!

If you're interested in joining, there are several ways for you to get signed up:

        


 What do we really need? Well, for instance:

For coders:                                 

Developers:

You'll be able to work on one of the coolest and fastest-growing open source painting programs out there.
Krita also benefits from a modular architecture and the use of the Calligra and Qt libraries, wich makes it easier to focus on new features instead of reinventing the wheel. And it makes coding fun!

Krita's developer wiki can be found here. To join up as a developer:

  1. Set up your development environment and build Krita.
  2. Find a few bugs to fix in KDE's Bugtracking system. It's often a good idea to get some experience with the code through fixing bugs, to get familiar with the development process without being overwhelmed. Though there's nothing against working on that cool feature that scratches your itch!
  3. For bugs, it's a good idea to start with "Junior Jobs." These are a set of relatively easy tasks for new developers. In the Bugtracking system, these are the bugs marked with "JJ."

To work on Krita, you have to use C++ and Qt. It's a good way to learn both, actually!   

Maintainers for Windows and OSX versions:
Do you have experience porting and maintaining programs from Linux to Windows or OSX? As we all know, the current Windows version of Krita needs a lot of work. Please help us bring Krita to a wider audience!

 Bug-testers:
The developers do their best to bring you a stable program. However, with many interacting features and several platforms to support, it's easy to overlook the occasional issue. Help make Krita a more stable program by reporting bugs. As Krita uses the KDE bugtracker, simply follow the instructions here. And reported bugs need to be tested on a variety of systems so we can check whether the report is correct: bug triaging is extremely important and very satisfying to do.

Technical writers: 

As you may have already seen, Krita's developer wiki is quite outdated and could use some updates and streamlining. It should become easy, in particular, for new potential developers to:

  • Find documentation for the development process (whether on Linux or other platforms)
  • Find additional resources that will help with coding for Krita
  • Find a list of tasks to do, including priority levels, time and experience needed, and supporting blueprints

College thesis and GSOC:
For students seeking a mentor for a thesis or a GSOC program: please note that through these programs, Krita only accepts students with a pretty good level of programming competence, and the potential to become long-term contributors. Don't wait until the last minute to apply, as Krita will give priority to those who have proved themselves with bug-fixes and other contributions (see above). You can find a list of possible projects here.

Sponsored development work:
Krita will occasionally raise funds to employ a developer to work full-time on Krita over a period of several months. Note that it will only sponsor developers who have already proven themselves through a long track record of contributions to Krita. To see the results of past sponsorship programs, see here.


For non coders:
Krita is far more than just a program, so there is a lot you can help with even if you can't code.

User documentation:
The Krita userbase wiki and Krita Handbook are in need of heavy work. We suggest drawing inspiration from Krita's existing set of tutorials and the documentation of other programs such as Gimp

Translation:
If you are a translator, you can help Krita reach a more international audience by either translating the program itself or translating existing documentation on the Krita userbase wiki .

Website:
Do you want to help maintain, improve the website or write articles? Please contact us!

Are you an artist?:
We'd love to see what you are creating with Krita! Please post your works in the gallery section, and indicate whether you allow us to use them in promotional material. New versions of Krita may also need new splash images and screenshots to demonstrate its new features, so we hope you will be able to contribute then as well.

Tutorials, brushes, patterns, etc.:
Do you have resources to share and contribute? They are always welcome! Please share them in the forum.

Marketing:
Krita needs to regularly announce new releases or fund-raising efforts on a variety of websites/blogs/social networks. This requires a lot of coordination work and perhaps a smart strategist.

 


Feature ideas:

Do you have ideas to make Krita into an even better program? Please submit a feature request on the Bugtracking system. You can also first discuss the suggestion at the Krita forums or IRC Channel. Please keep in mind that it may take years before a feature is implemented. You can help speed this up a tiny bit by working on additional details such as the graphical interface, as well as providing links to relevant resources. See here for an example of a good feature proposal write-up.

 

 

Read 11912 times Last modified on Wednesday, 31 July 2013 08:58
More in this category: « Resources Support Krita »
joomla template
template joomla