Hi all,
I'm delighted with the quick and enthusiastic response. This obviously is a great community to work with. Instead of responding to all the suggestions right now, I'm going to ponder this and come up with a specific plan later today. Meanwhile, more ideas are definitely helpful. The better I understand how this project and its people operate, the more effective my plan will be.
More soon, and thanks for the welcome! Vaughn
-----Original Message----- From: Joshua A. Andler [mailto:scislac@...400...] Sent: Tuesday, August 03, 2010 9:30 AM To: Vaughn Spurlin Cc: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] How to manage hundreds of bugs found by static analysis of Inkscape source?
On Mon, 2010-08-02 at 23:10 -0700, Vaughn Spurlin wrote:
What I’m requesting at this point is a discussion about my suggestions, and some decisions about how best to proceed. As an example, here’s one defect found by Coverity analysis, with my proposed code fix.
Hi Vaughn,
I think you got people a little excited about potential contributions. :) There is one thing that no one has brought up so far. We currently have three ongoing Google Summer of Code projects that will be modifying significant portions of the codebase. So what you have run analysis on is probably significantly different than what the codebase will look like in a month from now. I'm not trying to discourage you, just giving a heads up. :)
Cheers, Josh