Ok guys, update:<br><br>Let's take Richard's advice and go with: <br><br style="color:rgb(0,102,0)"><div style="margin-left:40px"><span style="font-family:courier new,monospace;color:rgb(0,102,0)">/*</span><br style="font-family:courier new,monospace;color:rgb(0,102,0)">
<span style="font-family:courier new,monospace;color:rgb(0,102,0)"> * Copyright 2012 Red Hat, Inc. and/or its affiliates.</span><br style="font-family:courier new,monospace;color:rgb(0,102,0)"><span style="font-family:courier new,monospace;color:rgb(0,102,0)"> *</span><br style="font-family:courier new,monospace;color:rgb(0,102,0)">
<span style="font-family:courier new,monospace;color:rgb(0,102,0)"> * Licensed under the Eclipse Public License version 1.0, available at</span><br style="font-family:courier new,monospace;color:rgb(0,102,0)"><span style="font-family:courier new,monospace;color:rgb(0,102,0)"> * <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></span><br style="font-family:courier new,monospace;color:rgb(0,102,0)">
<span style="font-family:courier new,monospace;color:rgb(0,102,0)"> */</span><br style="font-family:courier new,monospace"><br></div>Sorry if you've already replaced a few files! I just want to make sure we do this right.<br>
~Lincoln<br><div style="margin-left:40px"><br style="font-family:courier new,monospace"></div><div class="gmail_quote">On Sun, Aug 12, 2012 at 11:33 PM, Lincoln Baxter, III <span dir="ltr"><<a href="mailto:lincolnbaxter@gmail.com" target="_blank">lincolnbaxter@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Good question. For now, link to the file in github here (or say which file it is) so we can investigate :)<br><br>Thanks!<span class="HOEnZb"><font color="#888888"><br>
~Lincoln</font></span><div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">On Sat, Aug 11, 2012 at 1:34 PM, <a href="mailto:jdbjunior@gmail.com" target="_blank">jdbjunior@gmail.com</a> <span dir="ltr"><<a href="mailto:jdbjunior@gmail.com" target="_blank">jdbjunior@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey Lincoln, what about files with no license header. Add the header?<br>
<div><div><br>
On Fri, Aug 10, 2012 at 3:40 AM, Lincoln Baxter, III<br>
<<a href="mailto:lincolnbaxter@gmail.com" target="_blank">lincolnbaxter@gmail.com</a>> wrote:<br>
> I think that was me ;)<br>
><br>
> Do we need the file headers at all with the EPL?<br>
><br>
><br>
> /*<br>
> * Copyright 2012 Red Hat, Inc. and/or its affiliates.<br>
> *<br>
> * Licensed under the Eclipse Public License version 1.0,<br>
> * available at <a href="http://www.eclipse.org/legal/epl-v10.html" target="_blank">http://www.eclipse.org/legal/epl-v10.html</a><br>
> */<br>
><br>
> ~Lincoln<br>
><br>
><br>
> On Thu, Aug 9, 2012 at 4:10 PM, Richard Fontana <<a href="mailto:rfontana@redhat.com" target="_blank">rfontana@redhat.com</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> Just a note on that license notice:<br>
>><br>
>> There's nothing inherently wrong with that - it's the Apache License<br>
>> 2.0 standard notice recommended by the ASF but with the EPL<br>
>> substituted as the license.<br>
>><br>
>> However, I recently recommended to a developer of a new EPL-licensed<br>
>> JBoss-related project to use a simpler notice:<br>
>><br>
>><br>
>> Copyright 2012 Red Hat, Inc. and/or its affiliates.<br>
>><br>
>> Licensed under the Eclipse Public License version 1.0, available at<br>
>> <a href="http://www.eclipse.org/legal/epl-v10.html" target="_blank">http://www.eclipse.org/legal/epl-v10.html</a><br>
>><br>
>><br>
>> That would be my recommendation here, just because we don't have any<br>
>> true standard and simpler legal notices seem preferable.<br>
>><br>
>> (Substitute another copyright holder if appropriate, but for Red<br>
>> Hat-copyrighted source files use "Red Hat, Inc. and/or its affiliates"<br>
>> as above.)<br>
>><br>
>> I dis-recommended the notice commonly used by Eclipse Foundation<br>
>> projects, for any of you who've seen those, because I find them<br>
>> annoying and they are not quite a 'standard'.<br>
>><br>
>> - Richard<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On Thu, Aug 09, 2012 at 03:17:32PM -0400, Lincoln Baxter, III wrote:<br>
>> > Hey everyone,<br>
>> ><br>
>> > Thanks for "volunteering" to help with the EPL license effort.<br>
>> ><br>
>> > The first thing we should do to get started migrating the Forge license<br>
>> > is each<br>
>> > choose module(s) that we'd like to help migrate. Simply reply here with<br>
>> > the<br>
>> > forge/core module you are taking on, and we will try not to overlap.<br>
>> ><br>
>> > Once you've chosen your module(s), we'll need to take the following<br>
>> > steps.<br>
>> ><br>
>> > 1. In all of the source file, check the /** License */ header to ensure<br>
>> > that<br>
>> > the (c) Copyright is owned by JBoss.<br>
>> ><br>
>> > □ If it is, replace the header with the following License:<br>
>> ><br>
>> > /**<br>
>> > * Copyright 2012 Red Hat, Inc. and/or its affiliates.<br>
>> > *<br>
>> > * Licensed under the Eclipse Public License Version 1.0 (the<br>
>> > "License");<br>
>> > * you may not use this file except in compliance with the<br>
>> > License.<br>
>> > * You may obtain a copy of the License at<br>
>> > *<br>
>> > * <a href="http://www.eclipse.org/legal/epl-v10.html" target="_blank">http://www.eclipse.org/legal/epl-v10.html</a><br>
>> > *<br>
>> > * Unless required by applicable law or agreed to in writing,<br>
>> > software<br>
>> > * distributed under the License is distributed on an "AS IS"<br>
>> > BASIS,<br>
>> > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express<br>
>> > or<br>
>> > implied.<br>
>> > * See the License for the specific language governing<br>
>> > permissions and<br>
>> > * limitations under the License.<br>
>> > */<br>
>> ><br>
>> > □ If it is not, then record the name of the file and at the end of<br>
>> > your<br>
>> > review, send a list of all such files discovered as a reply to<br>
>> > this<br>
>> > thread so that we can review the necessary actions to take (most<br>
>> > likely<br>
>> > no action will be required, and we will simply leave the header<br>
>> > in<br>
>> > tact.)<br>
>> ><br>
>> > 2. Send your changes as a pull request for review.<br>
>> ><br>
>> > 3. Another committer will review your pull request and merge the<br>
>> > changes. Note<br>
>> > - please DO NOT merge your own pull requests. We should have at<br>
>> > least two<br>
>> > sets of eyes reviewing each license change. We don't want to get<br>
>> > this<br>
>> > wrong!<br>
>> ><br>
>> > 4. Drink beer.<br>
>> ><br>
>> > Thanks folks! Let the re-licensing begin!<br>
>> ><br>
>> > --<br>
>> > Lincoln Baxter, III<br>
>> > <a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>
>> > "Simpler is better."<br>
><br>
><br>
><br>
><br>
> --<br>
> Lincoln Baxter, III<br>
> <a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>
> "Simpler is better."<br>
><br>
</div></div><div><div>> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
><br>
<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."<br>