<p>Lincoln is a big fan of simple :)</p>
<p>As always, thanks for the prompt and insightful response!</p>
<p>-Dan</p>
<p>--<br>
Sent from my CyanogenMod-powered<br>
Android device, an open platform for<br>
carriers, developers and consumers.</p>
<div class="gmail_quote">On Aug 8, 2012 6:10 PM, "Richard Fontana" <<a href="mailto:rfontana@redhat.com">rfontana@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On Wed, Aug 08, 2012 at 05:01:54PM -0400, Lincoln Baxter, III wrote:<br>
> Hey Richard, Max,<br>
><br>
> Do you know what type of tasks we need to complete in order to be "correctly<br>
> licensed" under the EPL?<br>
><br>
> Such as:<br>
><br>
> 1. Include LICENSE file in base of project and deliverable archives.<br>
<br>
Yes.<br>
<br>
> 2. Include license header in all source files<br>
<br>
Good idea. I've never liked the IBM/Eclipse-style license notices<br>
(probably what Max is using :) and recently recommended this to<br>
Galder:<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>
I'd say use something as simple as that.<br>
<br>
- Richard<br>
<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">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>
</blockquote></div>