On Fri, 2013-11-08 at 10:02 +1300, Bryan Hoyt | Brush Technology wrote:
I'm suggesting that I'd be happy to have a go at fixing it myself at some stage in the nearish future, if it's not likely to be a big project, but if there were someone else who was keen to do it, I'd be happy to let them! I'm not offering sponsorship.
Oh, no problem, I just read "I'd be keen to (have someone) add" as that because to have someone is basically to have them work on your behalf.
Anyway! I have some ideas for you regarding getting into the code.
I know C++ well, but don't know Inkscape's codebase. Am I looking at a 2-day project or a 2-week (or 2-month) project?
You're not just going to be learning codebase, there's also a bit of a process to committing at first when you don't have commit access.
The best way to learn what you need to learn is to keep the website documentation open:
http://staging.inkscape.org/en/develop/getting-started/
And pick some bugs with the blending or similar areas from the list of bug reports:
http://tiny.cc/q3y34w <- these ones first, then any other
Fixing these issues will get you more familiarity with the codebase as well as commit access to trunk. Although I recommend keeping the branch/merge process for larger tasks as it makes it easier to review.
Good luck Bryan, let us know if you need any help.
Best Regards, Martin Owens