[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: CVS write access req. for WinSVN UI

From: Bill Tutt <billtut_at_microsoft.com>
Date: 2001-01-06 02:21:02 CET

From: Karl Fogel [mailto:kfogel@galois.collab.net]

> Bill Tutt <billtut@microsoft.com> writes:
> > Re: getting the stuff into CVS
> >
> > I'm not too worried about the copyright stuff on the VBAccelerator stuf,
> > have a feeling that'll all work itself out.

> Do you mind CollabNet having copyright on it, as long as the license
> terms are the same as the other files in Subversion? I ask only so we
> can keep things simple and not have to talk to the legal department --
> just trying to keep obstacles to a minimum (personally, I don't care
> who the copyright holder is as long as the code is Free :-) ).

That's not for me to answer. Steve (VB Accelerator guy) has the copyright on
the original source. Any modifications I make are fine to be copyright
Indeed any stuff I write are more than ok to be copyright CollabNet.

> > The big rush to get it into CVS however is so that Mark and I can
> > independently do useful things to it before I run out of my unusually
> > bout of free time wrt my work load here at MS. (The fact that I don't
> > when this bout will end yet is also fairly annoying.)

> Yup, I can see the convenience.

> This is for a win32 GUI client, using VB, right? I'm thinking a dir
> hierarchy something like this:

> subversion/subversion/clients/win32/

> where the last two are new dirs that don't exist yet. You and Mark do
> whatever you need to do under win32/. How does that sound, folks?

> I realize that this makes the command-line client's location kind of
> weird -- it's currently in subversion/subversion/client/, instead of
> subversion/subversion/clients/cmdline/. That might want to be
> rectified eventually.

> The reason for separating them out is that there may be many clients,
> and their maintenance/dev schedule is probably different from that of
> the subversion core libraries. It probably depends on exactly who's
> volunteering their time to what. In the CVS world, all the GUI
> clients are maintained separately, in fact. I think it's great that
> we'll distribute GUI clients with Subversion, though.

> I've CC'd this to Chris Clarke <chris@collab.net>, who I know has
> strong thoughts on Subversion GUI client interface design. Chris,
> feel free to weigh in (preferably on this list), talk with Bill and
> Mark about what you don't like in some of the CVS GUI's and how
> Subversion can get it right.

Yes the UI portion is in VB, the COM objects are in ATLized C++. All of the
above sounds fine to me. All of VB Accelerators code is in VB, but I was
planning on checking in only the source for modified controls/objects.

I'm no UI expert either, so feel free to take a look at the WinCVS 1.1bX UI,
and the prototype once it's in against your local SVN tree and then start
giving comments!

Received on Sat Oct 21 14:36:19 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.