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

Re: [Subclipse-dev] Copyright headers etc.

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-08-16 14:44:10 CEST

"Martin Letenay" <mle@whitestein.com> wrote on 08/16/2005 07:11:51 AM:

> during the last commits I've added few classes to the sources and I'm
not sure
> whether I correctly followed some "legal" guidelines.
> I quickly went through the code in core and it seems not all source
files are
> following the same schema.
> I'm not at all fluent in all these legal issues with multiple types of
public
> licenses, but I believe there is one for subclipse and the source code
> should clearly state it ...
>
> Is there a correct file header copyright statement specified somewhere ?

A can of worms I have tried to look away from!

I agree that most of the source is wrong. For example, lots of them
assign copyright to IBM, but only because the headers were copied from
Eclipse source code. The header in SVNClientManager seems the closes to
"right to me.

/******************************************************************************
 * This program and the accompanying materials are made available under
 * the terms of the Common Public License v1.0 which accompanies this
 * distribution, and is available at the following URL:
 * http://www.eclipse.org/legal/cpl-v10.html
 * Copyright(c) 2003-2005 by the authors indicated in the @author tags.
 *
 * All Rights are Reserved by the various authors.
 
*******************************************************************************/

> P.S. Since Eclipse 3.1 now supports project specific settings, should
such
> settings be directly commited ( I mean stuff in .settings folder) ?

I do not know much about what is in those files. I do not really have any
problem with including them in the repository. Just make sure there is
nothing that is very specific to your machine.

I guess on the other side of the argument, are there really any settings
that we feel that strongly about standardizing on? Part of the problem
with a file like this is that once we add it we are forcing settings on
everyone and if the user decides to change the settings, I presume that
will then update this file, which they might then commit back etc...

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Tue Aug 16 22:44:10 2005

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