<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 01/14/2014 01:35 PM, Colin McNamara
wrote:<br>
</div>
<blockquote
cite="mid:DAA07DF7-EF93-46CB-92CE-E8071307BD53@2cups.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Yes, you can both announce copyright via a method, such as a file
in a directory, or at the top of each individual file.
<div><br>
</div>
<div>For reference, here is a great presentation from Rowan Wilson
at Oxford - <a moz-do-not-send="true"
href="http://www.slideshare.net/crmwilson/copyright-in-software-and-open-source-licensing">http://www.slideshare.net/crmwilson/copyright-in-software-and-open-source-licensing</a></div>
<div><br>
</div>
<div>Again, I’m not a lawyer. I’ve just a guy who loves getting
people to contribute code, and who has to manage that balance of
code contribution combined with protection of intellectual
property rights at work. </div>
</blockquote>
<br>
Yes, that's pretty much what I'm interested in. And when we have
practices that 1) are shown, even anecdotally, to discourage
contribution and 2) don't actually contribute to the legal
protection of copyright, shouldn't we eschew them?<br>
<br>
That presentation doesn't suggest putting copyright statements in
files. It suggests having contributor license agreements and
tracking those contributions via revision control. We do those
things.<br>
<br>
If companies are genuinely concerned about protecting their
copyright on Open Source contributions, then they might
fundamentally misunderstand the concept of Open Source, which would
be kind of worrying.<br>
<pre class="moz-signature" cols="72">--
Rich Bowen - <a class="moz-txt-link-abbreviated" href="mailto:rbowen@redhat.com">rbowen@redhat.com</a>
OpenStack Community Liaison
<a class="moz-txt-link-freetext" href="http://openstack.redhat.com/">http://openstack.redhat.com/</a></pre>
</body>
</html>