[Box Backup] Future development plan

[Nick Knight]

Agree with all - I will try to commit some time to this it is an
important project.

The diffing time patch is in the win32 port - it would be good to agree
to on the approach.

Coding standard - definitely the way to go if this is going to be a team
effort!

Nick

-----Original Message-----
From: boxbackup-admin@fluffy.co.uk [mailto:boxbackup-admin@fluffy.co.uk]
On Behalf Of Jonathan Morton
Sent: 18 August 2005 13:37
To: boxbackup@fluffy.co.uk
Subject: Re: [Box Backup] Future development plan

> I propose:
>
> * Set up SVN repository. Import 0.09 + my minor modifications
>
> * Add in the following code in branches:
>     - Win32 port (Nick)
>     - Solaris port (Martin)
>     - Autoconf, 64 bit stuff, etc (LinuxOnPower) (Martin)
>     - Optimised diffing (Jonathan)
>     - (anything I've forgotten?)
> trying to keep different changes in different branches.

Seems reasonable.

> * Has everyone got enough time to get this done?

It may be slow at my end, but I can get things done.

> * Will people put up with my insistence on the style of the code being

> consistent?

Consistent code style is a good idea, although I think yours is=20
slightly different from mine...

> * Where should the SVN repository live? (Sourceforge don't provide=20
> one, but there are a few "free" providers listed. I might set up a=20
> repository on one of my servers, however.)

No idea about this.

> * What do we do about the license, and who holds the copyright?

> I use the various libraries to build other private projects, and I'd=20
> quite like to be able to bring changes into my own code. I have a=20
> preference for the BSD license, because BSD licensed projects have=20
> been so helpful to me in the past. But apart from that, I have no=20
> strong feelings either way.

For "private" projects, which are never released, the licence doesn't=20
matter at all (unless it's an EULA that prohibits reverse-engineering=20
or something stupid like that - and even that's debatable).  The GPL=20
specifically encourages this kind of code sharing.

The only problem would be if you wanted to take some of the modified=20
code and use it in a commercial project.  Then you'd either need to=20
stipulate to your customer that the result will be released under the=20
GPL, or ensure you have the right to use all the relevant code in a=20
closed-source project, or go back to your original code that you own=20
yourself.

One solution would be to gather all "library type" code under an LGPL=20
licence, which encourages code-sharing but does not preclude use in a=20
commercial, closed-source project.  Not everyone will be happy with=20
this, but I would hazard that it's the same set of people who would be=20
unhappy with simply assigning copyright.

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@chromatix.demon.co.uk
website:  http://www.chromatix.uklinux.net/
tagline:  The key to knowledge is not to rely on people to teach you it.

_______________________________________________
boxbackup mailing list
boxbackup@fluffy.co.uk
http://lists.warhead.org.uk/mailman/listinfo/boxbackup