On Mon, Apr 9, 2012 at 2:14 PM, jan pulmann <jan.pulmann@...400...> wrote:
I didn't contact with you before this proposal, because I forgot about the deadline, but I have been thinking about submitting proposal to inkscape for a while. Reading the mailing list, I see that you are more inclined to agree with internal structure refactoring project, and not my feature adding one. I would like to ask about my chances on this proposal. I don't know how far is it possible to bend the proposal, but I am much more confident with my math skills that software engineering skills, which is partly reason I chose this subject.
Hi Jan,
Unfortunately, contacting us prior to the deadline as well as having two accepted patches are really important to us as a project. They tend to be good indicators if students will actually complete their summer projects and if they will remain in touch with their mentors and the community. We do definitely favor things that will benefit the project internally rather than "flashy" new features. I have gone ahead and allowed you to modify your proposal to change it as much as you would like. As to your "chances", we can't really speak to that vs other proposals, however your chances are really slim unless you get 2 patches submitted and accepted ASAP.
I also have a technical question.
Getting comfortable with inkscape source, I was trying to find a source of bug https://bugs.launchpad.net/inkscape/+bug/953593 and I found out that poppler is returning wrong unicode codes (at least I think). What should I do next? I can write workaround (it won't be very nice, just swapping the two unicode values), or will just reporting to poppler suffice?
If the bug is indeed in poppler, rather than Inkscape or how we utilize poppler, submitting a bug upstream is highly recommended. However, if you do not actually patch either Inkscape or Poppler, it doesn't count as a fix in our eyes.
Cheers, Josh