<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 1, 2013 at 4:55 PM, Russell Bryant <span dir="ltr"><<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 05/01/2013 06:12 PM, Monty Taylor wrote:<br>
><br>
><br>
> On 05/01/2013 06:05 PM, John Griffith wrote:<br>
>><br>
>><br>
>><br>
>> On Wed, May 1, 2013 at 3:57 PM, Mark Washenberger<br>
>> <<a href="mailto:mark.washenberger@markwash.net">mark.washenberger@markwash.net</a> <mailto:<a href="mailto:mark.washenberger@markwash.net">mark.washenberger@markwash.net</a>>><br>
>> wrote:<br>
>><br>
>> Hi folks,<br>
>><br>
>> I was looking into the ASL-2.0, and chanced across the fact that in<br>
>> Apache projects, they require that source files only have the<br>
>> License Header, and may not have any copyright notices [1]. It<br>
>> occurred to me that we waste a fair amount of time on copyrights in<br>
>> license headers, and it would be nice not to have to do that anymore.<br>
><br>
> I would like to hear more about the time waste there - where are we<br>
> spending time? Can we do something to make that better?<br>
><br>
>> I think that only applies to code submitted directly to ASF, but<br>
>> regardless you wouldn't get any objections from me regarding your<br>
>> proposal. Some of the legal teams in companies involved in OpenStack<br>
>> however may feel differently.<br>
><br>
> And some of the developers. I would not like that.<br>
><br>
> I would really like to see more folks learn about appropriate addition<br>
> of copyright attribution when they work on a file, because I think it's<br>
> quite important. Don't think that removing attribution from each file<br>
> would prevent people from needing to do it - if we moved to a NOTICE<br>
> file system, they'd need to put the notice there.<br>
<br>
+1<br>
<br>
> I also think that it's important that the attribution be per-file and<br>
> not just in a NOTICE file, because the world has moved on from the days<br>
> when tarballs were the primary mechanism of source code distribution. We<br>
> publish this all on the web now. So this:<br>
><br>
> <a href="https://github.com/openstack-dev/pbr/blob/master/pbr/packaging.py" target="_blank">https://github.com/openstack-dev/pbr/blob/master/pbr/packaging.py</a><br>
><br>
> without per-file attribution, would not indicate who the license<br>
> associated with this file was from.<br>
><br>
>> I'm actually more troubled by seeing folks put copyright headers on<br>
>> blueprints.<br>
><br>
> Fascinating. I wonder if they realize that they're just asserting<br>
> copyright on the text of the blueprint itself...<br>
<br>
It's quite irritating. It's not clear at all what the intention is.<br>
Here are some examples:<br>
<br>
<a href="https://blueprints.launchpad.net/nova/+spec/accurate-capacity-of-clusters-for-scheduler" target="_blank">https://blueprints.launchpad.net/nova/+spec/accurate-capacity-of-clusters-for-scheduler</a><br>
<br>
<a href="https://blueprints.launchpad.net/nova/+spec/deploy-vcenter-templates-from-vmware-nova-driver" target="_blank">https://blueprints.launchpad.net/nova/+spec/deploy-vcenter-templates-from-vmware-nova-driver</a><br>
<br>
<a href="https://blueprints.launchpad.net/nova/+spec/esx-resource-pools-as-compute-nodes" target="_blank">https://blueprints.launchpad.net/nova/+spec/esx-resource-pools-as-compute-nodes</a><br>
<br>
<a href="https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service" target="_blank">https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service</a><br>
<br>
I emailed the submitted and asked for clarification on the intent, but<br>
haven't heard anything back.<br></blockquote><div><br></div><div style>You're much kinder than I Russell, I've just not accepted them and used equivalents that were written by others without the copyright.</div>
<div style> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Monty, since the ones I've noticed are from HP, perhaps this is<br>
something you can help track down?<br>
<br>
>> I also noticed a previous conversation [2] on this subject. I have<br>
>> not found any policy that actually requires us to include copyrights<br>
>> with each source file license header.<br>
>><br>
>> Feel free to suggest that this is more trouble than it is worth, but<br>
>> I'd like to propose that we discourage new contributions from<br>
>> including copyright attribution, and provide a process to work with<br>
>> the various parties we have to remove the copyrights from existing<br>
>> files. Somewhere along the line, somebody (maybe even me!) could<br>
>> write some appropriate hooks to ensure the (now identical) license<br>
>> header is present in every file for every submission.<br>
>><br>
>> Also, feel free to suggest that I'm plain wrong and am still wet<br>
>> behind the ears--I won't be terribly surprised!<br>
>><br>
>> [1] <a href="http://www.apache.org/legal/src-headers.html#headers" target="_blank">http://www.apache.org/legal/src-headers.html#headers</a><br>
>> [2]<br>
>> <a href="http://markmail.org/message/eawha7pjiqoslm66?q=openstack+license+source+header" target="_blank">http://markmail.org/message/eawha7pjiqoslm66?q=openstack+license+source+header</a><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-TC mailing list<br>
>> <a href="mailto:OpenStack-TC@lists.openstack.org">OpenStack-TC@lists.openstack.org</a><br>
>> <mailto:<a href="mailto:OpenStack-TC@lists.openstack.org">OpenStack-TC@lists.openstack.org</a>><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc</a><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-TC mailing list<br>
>> <a href="mailto:OpenStack-TC@lists.openstack.org">OpenStack-TC@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc</a><br>
>><br>
><br>
> _______________________________________________<br>
> OpenStack-TC mailing list<br>
> <a href="mailto:OpenStack-TC@lists.openstack.org">OpenStack-TC@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc</a><br>
><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
Russell Bryant<br>
<br>
_______________________________________________<br>
OpenStack-TC mailing list<br>
<a href="mailto:OpenStack-TC@lists.openstack.org">OpenStack-TC@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc</a><br>
</font></span></blockquote></div><br></div></div>