Re: svn commit: r22853 - in trunk: build/win32 packages/windows-innosetup subversion/bindings/swig/python subversion/libsvn_subr www

On 1/2/07, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:
> Well, you're right that at the moment there isn't much to distinguish
> our tree at the end of 2006 from the current one, but I'm sure we'll
> commit _something_ that's legally significant from a copyright
> perspective at some point fairly soon. At which point, as I understand
> it, the collection becomes a derivative work of something with a
> copyright date of 2007, so the whole lot gets to have that date.

While technically correct, the issue with that argument is that our
notice claims '2000-2007' which doesn't jive with that statement.

> The alternatives, I guess, is to either bump the dates immediately
> before a release (though I don't see that publication via release is any
> different to publication via ViewVC), or to decide at what point during
> the year we've committed something legally significant.

Another alternative is to drop copyright years altogether. =)

> > Can we please get the SVN Corp Board to deal with this definitively?
> >
>
> Sure, it'd be good to get definitive advice if we can.

From a strictly legal perspective, it's very clear what we're doing
doesn't conform to copyright notice standards. Yet, it's just a
matter of someone setting a clear policy for us to follow. The legal
downside of having an incorrect/invalid copyright notice is minimal,
but the pain comes from having to go through this argument every year
and seeing diffs go by that have no value. -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 2 22:24:27 2007