Re: What to do with CvsGui

I also vote for officially retiring the csvgui project. Maybe Arthur's sugg=
estion to mark the project as "no further development done" is not too bad =
- at least the WinCvs version is still very useful.

Unfortunately, the same is not true for MacCvsX, since it's PowerPC based a=
nd - as I outlined on the cvsgui mailing list - it's quite some work gettin=
g this migrated to the Intel architecture. Even then, as Richard mentioned,=
 the application framework used is completely outdated and the it's not eve=
n sure it can be made running on the latest versions of OS X with this code=
 base. Migrating to a modern code base (Cocoa) would be substantial work al=
most equalling a complete rewrite.

Anyway, while I understand there's still quite a bit of interest in having =
a CVS GUI client, I won't be able to spend the time getting MacCvsX even go=
ing on Intel, not mentioning updating it to a modern runtime.

I also agree with Arthur that we should not point users to other source con=
trol systems - my impression is that whoever is looking for a CVS GUI clien=
t already has a CVS repository and wants to/must stick  with it for whateve=
r reasons. We might want to point users to alternative CVS GUI clients, tho=
ugh.

my =80.02,
-jens


Am 19.03.2013 um 01:27 schrieb Arthur Barrett:

>=20
> My 2c:
>=20
> - Commercially we find a LOT of interest in CVSNT. User defined
> changesets, failsafe commits etc, it's the only 'open source' solution,
> and least expensive 'commercial' solution that provides support for
> those change management features if you need them.
>=20
> - WinCVS GUI is liked by a segment of our users, and we have our own
> 'branch' of this for code fixes if required (the few we've found already
> had fixes in the sourceforge tree).
>=20
> - I think the way forward (for GUI's at least) are native
> implementations. That's our approach.
>=20
> - We've been trying to get traction internally on a native MacCVS GUI
> for a while, but it's happening very slowly
>=20
> - For 'transparency' I think a notice on the web site that the project
> is 'stable' but not undergoing any active 'feature' development is good
>=20
> - I think that providing a 'list of alternative' is a flame war waiting
> to happen..., and besides it's unnecessary.
>=20
> Regards,
>=20
> Arthur Barrett
> Product Manager - CVSNT
>=20
> > -----Original Message-----
> > From: [email protected]=20
> > [mailto:[email protected]] On Behalf Of Richard Wesley
> > Sent: 19 March 2013 10:57
> > To: [email protected]
> > Cc: CvsGui Dev
> > Subject: Re: [cvsgui-dev] What to do with CvsGui
> >=20
> >=20
> > This has my vote. MacCvs is barely carbon based, which makes=20
> > it 10 years out of date.=20
> >=20
> > Best regards,
> > Richard Wesley
> > (Typed on my PDA)
> >=20
> > On Mar 18, 2013, at 16:36, Guy Rouillier=20
> > <[email protected]> wrote:
> >=20
> > > But honestly, due to the declining use of CVS, I think the=20
> > right course=20
> > > of action at this time is to put CvsGui into a retired status, and=20
> > > encourage anyone who visits the page to consider more=20
> > modern and popular=20
> > > source control options.
> > >=20
> > > Appreciate hearing from other devs. Thanks.
> >=20


[Non-text portions of this message have been removed]



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

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]=20
    [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/