Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates
 66.249.92.171 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding;
        b=G2gUZNVpbH6l2saTv5XjjyqqzVsA6D32xT8M6x4L9K+ZZJdXVK097pD54ik1jhBOpv6+bwv4Yp8YYOPKeRGjgnP0GxneknmV1zPC8cScZhcdn4YjJXcfRex3u/nk4j1DzdkV1bCx3rVDxQaqEoZJzUUhTYtHVfAMkpf1O3FeiFg=
Message-ID: <4512E248.1050507@gmail.com>
Date: Thu, 21 Sep 2006 20:04:40 +0100
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [legal] change of copyright notice policy
References: <70E7560C-DCC2-42E0-92C3-F54ADD246418@pobox.com>
In-Reply-To: <70E7560C-DCC2-42E0-92C3-F54ADD246418@pobox.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I suggest that committers volunteer to run the script (and verify the
results etc.) on a module-by-module, rather than package-by-package,
basis; plus the VMs of course.

Let's list the units of work on the wiki and have people sign-up to
convert them.

I assume that we will convert *all* copyright blocks in SVN (tools,
website, etc.), not just those that would make it into a release, right?

What a drag.
Tim


Geir Magnusson Jr. wrote:
> The ASF has changed it's copyright notice policy for source files.  The
> policy is noted here :
> 
>   http://www.apache.org/legal/src-headers.html
> 
> Any release after Nov 1, 2006 must conform to this policy.  Since we
> aren't near a release yet, we have plenty of time, but we should do this
> sooner than later.
> 
> First and foremost, any new contributions should follow the policy.
> 
> Second, we should decide how we want to proceed.  It's clear to me that
> we're not going to naturally touch all the files over time in any
> reasonable amount of time, so we can't just do it over time as we work
> on the code.
> 
> The best solution is a script that can be run on an arbitrary source
> tree, so that developers can do this on a package by package basis (or
> the whole thing at once, although it seems package by package over time
> by all the committers seems to be a good way to farm out the work.  :)
> 
> I think that patches are a bad idea for this since the script is neater
> and re-usable for other projects as well.
> 
> Thoughts?
> 
> geir
> 
> 
> 
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> 
> 

-- 

Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org