KSVG Homepage
Helping Out
Currently the design of KSVG2, while in a quite advanced state, is not finalized yet. Furthermore, since not all of the svg specs is implemented, we want to wait with setting up a bugzilla entry for KSVG2 until a release is done. Taking all that into account, here is what we think makes most sense right now:
- Help general development. This will probably mean you need good skills in C++ and KDE coding. If you have trouble getting familiar with the codebase, fixing isolated problems/bugs can be a good way to get more familiar with it.
- Bug reporting, but instead of using bugzilla, mail us directly or even better visit us on irc.
- Testing KSVG2 from HEAD on complex svgs that we do not test ourselves. The current list of complex svg tests can be found here. It would be best to contact us on irc to find out whether the svg testcase you found is worth adding to the custom tests.
- Documentation of code. Ofcourse this would make most sense for non-trivial methods and code sections. Also explanation of concepts and designs would be welcomed. Note that some kinds of documentation writing may need a good understanding of the codebase.
Note that in general, if you are serious about helping out with KSVG2, the best is to just drop by on #ksvg, and then we can work out further steps from there.
[ Edit ]
