<div dir="ltr">+1 on removal, +100 on author list(s). I'll stay out of the legal questions.<div><br></div><div>I verified that 'hg blame -u' on a "hg mv'd" file preserves the line-by-line original author name, thus quenching my fear of hg mv's obliterating the easy authorship lookup. </div>
<div><br></div><div>Sam</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 10, 2013 at 2:23 PM, Anthony Scopatz <span dir="ltr"><<a href="mailto:scopatz@gmail.com" target="_blank">scopatz@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Whoops, sorry. I left out the 4th basic option.<div><br></div><div>4. Incorporate: become an LLC or a non-profit which is a legal entity. This is what the HDF Group is for HDF5 or the Plone Foundation for Plone.</div>
<div><br></div><div>I *highly* advise against this option. If you thought working on open source code was overwhelming...</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Sep 10, 2013 at 11:14 PM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank you, Anthony -- this is a very useful reply.<br>
<div><br>
On Tue, Sep 10, 2013 at 5:05 PM, Anthony Scopatz <<a href="mailto:scopatz@gmail.com" target="_blank">scopatz@gmail.com</a>> wrote:<br>
> I have some amount of experience with, though please don't confuse that with<br>
> legal counsel.<br>
><br>
> So both J and Nathan correct. The "yt collaboration" or "yt team" is not a<br>
> legal entity. Because of the that copyright is held by the individual<br>
> contributors. However, in the license document when you say "yt<br>
> collaboration" that is understood as "the authors." Which is part of why<br>
> you should publish an author list. However, what goes along with this is<br>
> that the individual authors are personally liable for the code. This is why<br>
> having a license is important. Open source license shield you from<br>
> liability because they explicitly state that they offer no warranty and the<br>
> user assumes the risk. (And since it is software it is not as if someone<br>
> will accidentally cut off their hand or something...unless you are David<br>
> Beazley.)<br>
<br>
</div>For everyone else out there, our licenses (both new and old) do<br>
explicitly state this. This is the BSD 3-clause. (Caps are not<br>
mine.)<br>
<br>
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS<br>
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT<br>
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR<br>
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT<br>
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,<br>
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT<br>
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,<br>
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY<br>
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT<br>
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE<br>
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.<br>
<div><br>
><br>
> That said, you have three basic options:<br>
><br>
> 1. leave the license and liability and copyright where it is, with the<br>
> individual authors.<br>
> 2. Communally decide to give one person copyright, they are a legal entity,<br>
> 3. Assign copyright to a neutral third party organization which is a legal<br>
> entity, e.g. NumFOCUS*, Software Freedom Conservancy, a University.<br>
><br>
<br>
</div>I would be open to any of these three. Were it to be #3, either<br>
NumFOCUS or SFC would be my preference, in that order. Being under<br>
the NumFOCUS umbrella would be attractive to me, personally.<br>
<div><div><br>
> Note that issues related to this are only ever important if someone decides<br>
> to litigate or you want to trademark something. For the overwhelming<br>
> majority of projects, these never happen.<br>
><br>
> Be Well<br>
> Anthony<br>
><br>
> * Note that this is part of why we started NumFOCUS. Though I admit that<br>
> negotiating with the bigger projects on what a successful sponsorship<br>
> agreement looks like is taking longer than everyone would like. We do hold<br>
> a few copyrights though currently.<br>
><br>
><br>
> On Tue, Sep 10, 2013 at 10:49 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>><br>
> wrote:<br>
>><br>
>> I believe you retain your copyright over your changes regardless of the<br>
>> author tags. IANAL so if someone knows better please correct me.<br>
>><br>
>><br>
>> On Tue, Sep 10, 2013 at 1:43 PM, j s oishi <<a href="mailto:jsoishi@gmail.com" target="_blank">jsoishi@gmail.com</a>> wrote:<br>
>>><br>
>>> +1 on removing author tags<br>
>>><br>
>>> What do we do about the copyright? I mean, can we assign copyright to<br>
>>> "the yt collaboration" if the yt collaboration doesn't exist in a legal<br>
>>> sense?<br>
>>><br>
>>> j<br>
>>><br>
>>><br>
>>> On Tue, Sep 10, 2013 at 4:36 PM, Anthony Scopatz <<a href="mailto:scopatz@gmail.com" target="_blank">scopatz@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Hey Nathan,<br>
>>>><br>
>>>> I think that this is generally good move. Though I would encourage an<br>
>>>> authors page on the website which lists everyone who has contributed.<br>
>>>><br>
>>>> Be Well<br>
>>>> Anthony<br>
>>>><br>
>>>><br>
>>>> On Tue, Sep 10, 2013 at 10:31 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> On Tue, Sep 10, 2013 at 4:29 PM, Nathan Goldbaum<br>
>>>>> <<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>> wrote:<br>
>>>>> > Matt,<br>
>>>>> ><br>
>>>>> ><br>
>>>>> > On Tue, Sep 10, 2013 at 1:23 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>><br>
>>>>> > wrote:<br>
>>>>> >><br>
>>>>> >><br>
>>>>> >> I am +1 on removing the author tags. That being said, I consciously<br>
>>>>> >> decided *not* to, for basically two reasons which are somewhat<br>
>>>>> >> related. The first is that I think removing the author tags will<br>
>>>>> >> disproportionately impact individuals who perhaps have contributed<br>
>>>>> >> specific files or analysis modules but have not contributed a large<br>
>>>>> >> quantity of code to the overall base of yt. The second reason is<br>
>>>>> >> really my main one: I don't want to be as strongly associated with<br>
>>>>> >> yt<br>
>>>>> >> as I currently am. Not because I don't have pride in it (I do), but<br>
>>>>> >> because I don't want people who aren't deep in the code development<br>
>>>>> >> to<br>
>>>>> >> believe that I'm the only person contributing, and I do not think<br>
>>>>> >> that<br>
>>>>> >> does favors for *anyone*. (I still receive many emails off-list,<br>
>>>>> >> people say things to me that I have to correct about what yt is, etc<br>
>>>>> >> etc.) It creates an impression of consolidation of responsibility,<br>
>>>>> >> as<br>
>>>>> >> well as undermines the credit that others receive for their<br>
>>>>> >> contributions. Having names (that aren't mine) on source files<br>
>>>>> >> reduces the apparent consolidation. I was leery of making such a<br>
>>>>> >> change, because removing names felt really wrong to me to do on my<br>
>>>>> >> own.<br>
>>>>> >><br>
>>>>> ><br>
>>>>> > I'd argue that the yt = matt turk misconception is made worse by the<br>
>>>>> > author<br>
>>>>> > tags, since your name is on almost every file.<br>
>>>>><br>
>>>>> Then let's get rid of them.<br>
>>>>><br>
>>>>> ><br>
>>>>> >><br>
>>>>> >> So, I'm fine with removing them if everyone else is too. But I'd<br>
>>>>> >> also<br>
>>>>> >> like to trade this for having some type of mechanism for public<br>
>>>>> >> recognition of efforts. (In addition to another paper, which is<br>
>>>>> >> probably still a bit off.) Perhaps something like a core team, or<br>
>>>>> >> list of contributors, on the website? Something that can be pointed<br>
>>>>> >> to, put on a CV, anything.<br>
>>>>> ><br>
>>>>> ><br>
>>>>> > Very much agreed. I'd follow what the IPython project does, a list<br>
>>>>> > of core<br>
>>>>> > contributors on the website and list of *all* contributors for each<br>
>>>>> > release:<br>
>>>>> ><br>
>>>>> ><br>
>>>>> > <a href="http://ipython.org/ipython-doc/stable/about/license_and_copyright.html" target="_blank">http://ipython.org/ipython-doc/stable/about/license_and_copyright.html</a><br>
>>>>> > <a href="http://ipython.org/ipython-doc/stable/whatsnew/github-stats-1.0.html" target="_blank">http://ipython.org/ipython-doc/stable/whatsnew/github-stats-1.0.html</a><br>
>>>>><br>
>>>>> I like this a lot.<br>
>>>>><br>
>>>>> I've mentioned in IRC a few times that I'd like to re-do the homepage.<br>
>>>>> If anyone wants to work on that, I'd be totally game. I think having<br>
>>>>> something based on bootstrap with the "slate" theme might be nice; I<br>
>>>>> started sketching out something the other day. One option would be to<br>
>>>>> move the *entire* homepage to Sphinx and just have a nice template for<br>
>>>>> the front page, similar to what IPython and others do.<br>
>>>>><br>
>>>>> ><br>
>>>>> > Cheers,<br>
>>>>> ><br>
>>>>> > Nathan<br>
>>>>> ><br>
>>>>> > _______________________________________________<br>
>>>>> > yt-dev mailing list<br>
>>>>> > <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>>>> > <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>> ><br>
>>>>> _______________________________________________<br>
>>>>> yt-dev mailing list<br>
>>>>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> yt-dev mailing list<br>
>>>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> yt-dev mailing list<br>
>>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> yt-dev mailing list<br>
>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> yt-dev mailing list<br>
> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>