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

Re: Tortoise is Beatiful - Job / Contract opportunity for TortoiseSVN related project.

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-09-15 22:00:36 CEST

Jay Crouch wrote:
> Hi all, I didn't know how else to get ahold of the main developers so I am
> posting to this list -- this is not an advertisement, please read.
> I've been using SVN for a while now - as a developer, and the Tortoise is
> especially nice; the way it is implemented as hook system into windows
> explorer.

Actually, it's not a system hook but a "shell extension" (ok, several
shell extensions). Just to avoid confusions.

> My company is creating a document/content management system for corporate
> professionals. In most respects, the system we are envisioning is identical to
> SVN, and we would like it to work behind the scenes in explorer much the same
> way Tortoise does. However, the system would primarily be working with Office
> type documents (.doc, .xls, etc) instead of text (code). Also, we would be
> simplifing and automating many of the features to make it easy for dummys to
> use.

What would you like to simplify and automate?
You know that you can mount a Subversion repository (hosted on apache)
in explorer as a web folder? When you do that, the user doesn't even
realize that the folder isn't a normal folder, and still every "save"
creates a new revision in the repository. I think it can't get simpler
than that :)

> So it looks like we may be building a custom app that runs over svn (or
> perhaps even a custom protocol layer) and I thought who better to develop this
> system than the guys who built Tortoise.

TortoiseSVN is 'only' a Subversion client. It uses the Subversion
library for any network or repository access and all protocols. So if
you really want to implement a custom protocol, then you should ask the
Subversion guys for help.

If however you only want to build a shell extension (icon overlays,
adding entries to the explorer menu, additional columns in explorer
detailed view) then of course we can help.

> Anyone with significant experience/understanding of how Tortise is built is
> welcome to respond. I would be interest to talk with anyone about the overall
> project and general estimates of budget and timeline for what we want to do.

That might be harder than you think. You see, all people here working on
TortoiseSVN do that in their free time. We all have jobs which keep us
busy during the day. That means time will be an important factor here.
We can't just quit our jobs :)

> Lastly, as svn and tortoise are open source projects I would really like to
> talk with the main developers to discuss licensing issues because we would
> would probably want to build our app on a lot of the tortoise base - but need
> to make sure we do it legally.

TortoiseSVN is under the GPL. Which means that if you plan to use any
part of TSVN's sourcecode, your application would have to be under the
GPL too. There's no way around that, believe me. I've tried once to
change the license to another license, but I failed. The reason I failed
was because some of the developers involved in this project refused the
license change.
If you however just want to *use* TortoiseSVN or a part of it, you can
do the same as VisualSVN currently does: just tell your customers to
install TortoiseSVN first.

> Thanks, and please forward this to the appropriate people if you know them.

We're all reading this list, so you've reached the right people :)


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Sep 15 22:00:47 2006

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

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