Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Date: Sun, 22 Feb 2004 11:35:27 -0800
From: Greg Stein <gstein@lyra.org>
To: geronimo-ppmc@incubator.apache.org, geronimo-dev@incubator.apache.org
Subject: Re: License Change Day, was: Change of License
Message-ID: <20040222113527.B11984@lyra.org>
References: <Sea1-F88nZUjEyXLwS600016453@hotmail.com>
 <4038D7CB.3080205@coredevelopers.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <4038D7CB.3080205@coredevelopers.net>;
 from jeremy@coredevelopers.net on Sun, Feb 22, 2004 at 08:24:43AM -0800

On Sun, Feb 22, 2004 at 08:24:43AM -0800, Jeremy Boynes wrote:
>...
> Given the short time to do the migration, I see the biggest challenge as 
> getting everyone to sync their versions. As weekends seem to be the most

Sync? If somebody is changing the header of a file, it shouldn't interfere
with anything you're doing within the file. Before you commit, you'll just
do a "cvs update" and CVS will merge the license change into your files.

The only way that you'll see a problem is if *two* people try to change
the headers. Then you'll get a merge conflict in the headers, *maybe*. CVS
is also pretty good about seeing that a change made on the server is equal
to what you did in your local working copy.

For Apache HTTPD, one person volunteered and then proceeded to relicense
the whole codebase over a day or two. I didn't hear of any problems, and
we certainly din't have a "sync day".

The tools take care of this for you.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/