[splint-discuss] Moving to a proper issue tracking system

[SF Markus Elfring]

> 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.

This is partly available. The document "http://splint.org/bugs.html" 
refers to the list 
"http://sourceforge.net/tracker/?group_id=9538&atid=109538" which 
belongs to the project "Old LCLint Project". I would appreciate if this 
link will be updated to avoid confusion with the list 
"http://sourceforge.net/tracker/?atid=459911&group_id=34302&func=browse" 
which belongs to the project "splint - secure programming lint".
There is a bit competition between the communication/collaboration in 
mailing lists and issue tracking systems.


> 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.

How do you think about the approach "Importing Data into SVN"?
https://sourceforge.net/docman/display_doc.php?docid=31070&group_id=1#import

Would you like to consider other source control management systems like 
Git for distributed work?
http://en.wikipedia.org/wiki/Git_%28software%29

Regards,
Markus