What to do with CvsGui

Both Jens and I have responded to recent emails on the public CvsGui 
mailing list about issues with the current clients (me: gCvs, Jens: 
MacCvs.) Our responses were honest but not encouraging.  Basically, both 
of these clients are dated with significant functionality issues.  I 
take responsibility for that state of gCvs.  I continue to use WinCvs on 
a daily basis - the 2.1.1.1 version that was never released.

While trying to discover if my subscription to this dev list was still 
active, I noticed that this list hasn't had any messages since 2011. 
One final fact: Cvs use is declining.  Our SourceForge host has put it 
into legacy status.

So, what do we want to do with CvsGui?  Do we want to continue to 
support it?  With a little prodding, I could be convinced to put some 
work into gCvs again.  But honestly, I don't think the approach used in 
the current code base is even desirable.  As I commented on the public 
list, the code base requires the GTK implementation into a Windows-like 
messaging approach, and it just doesn't fit; when I was working on gCvs, 
I found that square peg-round hole situation aggravating to program.  I 
believe a better approach would be just to use base CVS classes as a 
foundation, and implement a native client on each platform.

But honestly, due to the declining use of CVS, I think the right course 
of action at this time is to put CvsGui into a retired status, and 
encourage anyone who visits the page to consider more modern and popular 
source control options.

Appreciate hearing from other devs.  Thanks.

-- 
Guy Rouillier


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui-dev/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/cvsgui-dev/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/