[splint-discuss] Moving to Google Code

[Andy Lester]

On Jul 15, 2007, at 10:38 AM, SF Markus Elfring wrote:

> How many developers care to resolve the open issues (http:// 
> splint.org/bugs.html) in the software?
> Can its internal design be improved so that more participation  
> would be possible by other interested programmers?

I would be glad to help out however I can.  If the open issues were  
moved to the bug tracker in SourceForge, it would make it easier to  
see what's what.  It would also be far better to can the static page  
of "known bugs" and replace it with a searchable database.

Better still, if the entire project were moved to Google Code, it  
would be a quantum leap forward in usability.  You'd get a bug  
tracker that's usable, a wiki, and Subversion support instead of  
clunky old CVS.

I realize that splint has been quiet for a while, but its value  
cannot be underestimated to projects still alive today.  A move to  
Google Code would help re-energize this incredibly useful tool.

xoxo,
Andy

--
Andy Lester => andy at petdance.com => www.petdance.com => AIM:petdance