Fernando,

I think we should move forward with a decision on this issue. Some things 
under consideration:

* Replace "Project Jupyter Team" by "Jupyter Contributors" in our copyright 
notice in files.
* Move to an exact copy of the BSD license rather than one with subtle 
changes.

Jason has proposed using the version of the BSD license from the OSI:

https://opensource.org/

I think you should make the call so we can move forward with things (or 
not).

If folks have concerns they have not voiced, please do so now :) 

Cheers,

Brian


On Tuesday, July 26, 2016 at 9:38:34 AM UTC-7, Evan Bolyen wrote:
>
> GitHub actually uses the Wikipedia-style template, so whenever you set an 
> automatic LICENSE it uses that (see here 
> <https://github.com/ebolyen/default-bsd-3-clause/blob/master/LICENSE>). 
> The page Fernando linked also states that the 3rd clause was changed, my 
> interpretation being that the "original" BSD-Modified/3-Clause was just the 
> omission of the 4th clause which made it incompatible with GPL. It does 
> look like the 3rd clause has since been revised, but I have no idea what 
> the legal implications are.
>
> -Evan
>
> On Monday, July 25, 2016 at 9:18:51 PM UTC-7, ellisonbg wrote:
>>
>> Thanks! 
>>
>> On Mon, Jul 25, 2016 at 8:16 PM, Jason Grout <[email protected]> 
>> wrote: 
>> > Makes sense. I've put in a PR to JupyterLab with this change so we can 
>> see 
>> > what it looks like: 
>> https://github.com/jupyter/jupyterlab/pull/543/files 
>> > 
>> > I also switched the clauses to use numbering, like on the 
>> opensource.org 
>> > website template. 
>> > 
>> > Jason 
>> > 
>> > 
>> > 
>> > On Mon, Jul 25, 2016 at 11:12 PM Brian Granger <[email protected]> 
>> wrote: 
>> >> 
>> >> On Mon, Jul 25, 2016 at 7:58 PM, Jason Grout <[email protected]> 
>> wrote: 
>> >> > For a specific project, say JupyterLab, should we "JupyterLab 
>> >> > contributors", 
>> >> > to indicate that those individuals who contributed to that specific 
>> >> > project 
>> >> > are the ones that hold copyright? Or should we give the generic 
>> "Project 
>> >> > Jupyter Contributors" 
>> >> 
>> >> Because people tend to move fluidly between different 
>> >> repos/subprojects, I would prefer the generic "Project Jupyter 
>> >> Contributors". Also this more easily covers situations where we 
>> >> re-organize code between repos/subprojects, as tends to happen 
>> >> sometimes... 
>> >> 
>> >> Cheers, 
>> >> 
>> >> Brian 
>> >> 
>> >> > 
>> >> > Also, FYI, the Wikipedia text has the place for 'copyright holders' 
>> as a 
>> >> > templated term, perhaps that's where we got the other text: 
>> >> > 
>> >> > 
>> https://en.wikipedia.org/wiki/BSD_licenses#3-clause_license_.28.22Revised_BSD_License.22.2C_.22New_BSD_License.22.2C_or_.22Modified_BSD_License.22.29
>>  
>> >> > 
>> >> > Thanks, 
>> >> > 
>> >> > Jason 
>> >> > 
>> >> > 
>> >> > 
>> >> > 
>> >> > On Mon, Jul 25, 2016 at 7:50 AM Damián Avila <[email protected]> 
>> >> > wrote: 
>> >> >> 
>> >> >> +1 to use the real BSD. 
>> >> >> 
>> >> >> >But if using the plural "Contributors" text is clearer than the 
>> >> >> > collective "Team", that's fine, too, and changes no meaning. 
>> >> >> 
>> >> >> +1 too. 
>> >> >> 
>> >> >> 
>> >> >> 
>> >> >> 2016-07-25 8:40 GMT-03:00 MinRK <[email protected]>: 
>> >> >>> 
>> >> >>> +1 to the change. Not quite sure how we drifted there, but it may 
>> well 
>> >> >>> have been my doing during the split. We have defined in our 
>> IPython 
>> >> >>> license 
>> >> >>> file "The IPython Development Team is the set of all contributors 
>> to 
>> >> >>> the 
>> >> >>> IPython project," so it is already synonymous with Contributors, 
>> and 
>> >> >>> has 
>> >> >>> never been an entity. But if using the plural "Contributors" text 
>> is 
>> >> >>> clearer 
>> >> >>> than the collective "Team", that's fine, too, and changes no 
>> meaning. 
>> >> >>> 
>> >> >>> -MinRK 
>> >> >>> 
>> >> >>> On Sat, Jul 23, 2016 at 3:44 AM, Fernando Perez <
>> [email protected]> 
>> >> >>> wrote: 
>> >> >>>> 
>> >> >>>> Hi all, 
>> >> >>>> 
>> >> >>>> I recently noticed that there's something funny about the way our 
>> >> >>>> license is worded compared to the BSD template... 
>> >> >>>> 
>> >> >>>> Our licenses say 
>> >> >>>> 
>> >> >>>> "Neither the name of JupyterLab...", "... name of Jupyter...", 
>> etc... 
>> >> >>>> 
>> >> >>>> But the original BSD template reads 
>> >> >>>> (https://opensource.org/licenses/BSD-3-Clause) 
>> >> >>>> 
>> >> >>>> "Neither the name of the copyright holder..." 
>> >> >>>> 
>> >> >>>> and the term "copyright holder" isn't a variable to template 
>> over, 
>> >> >>>> just 
>> >> >>>> the words "copyright holder".  In our case, that is "Project 
>> Jupyter" 
>> >> >>>> in 
>> >> >>>> some licenses, and I'd argue it should read "Project Jupyter 
>> Team" to 
>> >> >>>> indicate that it's the *people*, not the abstract/legal project 
>> >> >>>> entity... 
>> >> >>>> 
>> >> >>>> I didn't realize that our licenses had changed in this way, but 
>> in a 
>> >> >>>> sense we are NOT using BSD!  We've made a subtle but important 
>> >> >>>> change, as 
>> >> >>>> we've basically added a trademark barrier in the third clause 
>> (hence 
>> >> >>>> this 
>> >> >>>> question the person is asking), whereas the original third clause 
>> is 
>> >> >>>> about 
>> >> >>>> *endorsement of promotion*. 
>> >> >>>> 
>> >> >>>> I had never noticed this, but I would argue that our licenses 
>> should: 
>> >> >>>> 
>> >> >>>> 1. All read: 
>> >> >>>> 
>> >> >>>> Copyright... The Project Jupyter Development Team. 
>> >> >>>> 
>> >> >>>> 
>> >> >>>> This would convey the fact that we're talking about the people 
>> who 
>> >> >>>> wrote 
>> >> >>>> the code.  It's our shorthand for the union of all `git shortlog 
>> >> >>>> -sne`... 
>> >> >>>> 
>> >> >>>> 
>> >> >>>> 2. Actually use the real BSD license text, not some subtly 
>> modified 
>> >> >>>> version.  That means that other than filling in the placeholders, 
>> we 
>> >> >>>> leave 
>> >> >>>> the body of text unmodified. 
>> >> >>>> 
>> >> >>>> 
>> >> >>>> What do people think? 
>> >> >>>> 
>> >> >>>> Cheers, 
>> >> >>>> 
>> >> >>>> ps - sorry that I'm sending this and going offline, the 
>> discussion 
>> >> >>>> started on the council list and Jason correctly pointed out that 
>> this 
>> >> >>>> is 
>> >> >>>> really an open topic... Reposting here for reference, hopefully 
>> >> >>>> others can 
>> >> >>>> provide feedback in my absence. 
>> >> >>>> 
>> >> >>>> -- 
>> >> >>>> Fernando Perez (@fperez_org; http://fperez.org) 
>> >> >>>> fperez.net-at-gmail: mailing lists only (I ignore this when 
>> swamped!) 
>> >> >>>> fernando.perez-at-berkeley: contact me here for any direct mail 
>> >> >>>> 
>> >> >>>> -- 
>> >> >>>> You received this message because you are subscribed to the 
>> Google 
>> >> >>>> Groups "Project Jupyter" group. 
>> >> >>>> To unsubscribe from this group and stop receiving emails from it, 
>> >> >>>> send 
>> >> >>>> an email to [email protected]. 
>> >> >>>> To post to this group, send email to [email protected]. 
>> >> >>>> To view this discussion on the web visit 
>> >> >>>> 
>> >> >>>> 
>> https://groups.google.com/d/msgid/jupyter/CAHAreOoQjN%2BA41qoyXy5ZUUjL_kL9g8Xd2RVMdWvJ_eW62wToQ%40mail.gmail.com.
>>  
>>
>> >> >>>> For more options, visit https://groups.google.com/d/optout. 
>> >> >>> 
>> >> >>> 
>> >> >>> -- 
>> >> >>> You received this message because you are subscribed to the Google 
>> >> >>> Groups 
>> >> >>> "Project Jupyter" group. 
>> >> >>> To unsubscribe from this group and stop receiving emails from it, 
>> send 
>> >> >>> an 
>> >> >>> email to [email protected]. 
>> >> >>> To post to this group, send email to [email protected]. 
>> >> >>> To view this discussion on the web visit 
>> >> >>> 
>> >> >>> 
>> https://groups.google.com/d/msgid/jupyter/CAHNn8BUJ0FC4HqTkPM6Cd0L0F6HUQdCOozPNgW3YLP%2Br3fVc-g%40mail.gmail.com.
>>  
>>
>> >> >>> 
>> >> >>> For more options, visit https://groups.google.com/d/optout. 
>> >> >> 
>> >> >> 
>> >> >> 
>> >> >> 
>> >> >> -- 
>> >> >> Damián 
>> >> >> 
>> >> >> -- 
>> >> >> You received this message because you are subscribed to the Google 
>> >> >> Groups 
>> >> >> "Project Jupyter" group. 
>> >> >> To unsubscribe from this group and stop receiving emails from it, 
>> send 
>> >> >> an 
>> >> >> email to [email protected]. 
>> >> >> To post to this group, send email to [email protected]. 
>> >> >> To view this discussion on the web visit 
>> >> >> 
>> >> >> 
>> https://groups.google.com/d/msgid/jupyter/CAH%2BmRR0QUXo6SQ0CKL6FFzM6vBufO5kNZ2r4Bob11kfSjKxLQg%40mail.gmail.com.
>>  
>>
>> >> >> For more options, visit https://groups.google.com/d/optout. 
>> >> > 
>> >> > -- 
>> >> > You received this message because you are subscribed to the Google 
>> >> > Groups 
>> >> > "Project Jupyter" group. 
>> >> > To unsubscribe from this group and stop receiving emails from it, 
>> send 
>> >> > an 
>> >> > email to [email protected]. 
>> >> > To post to this group, send email to [email protected]. 
>> >> > To view this discussion on the web visit 
>> >> > 
>> >> > 
>> https://groups.google.com/d/msgid/jupyter/CAPDWZHwtPrzZwT6%3D11rZxoMr2RbOx%2BOiJXojd%2BXHB90draDNNg%40mail.gmail.com.
>>  
>>
>> >> > 
>> >> > For more options, visit https://groups.google.com/d/optout. 
>> >> 
>> >> 
>> >> 
>> >> -- 
>> >> Brian E. Granger 
>> >> Associate Professor of Physics and Data Science 
>> >> Cal Poly State University, San Luis Obispo 
>> >> @ellisonbg on Twitter and GitHub 
>> >> [email protected] and [email protected] 
>> >> 
>> >> -- 
>> >> You received this message because you are subscribed to the Google 
>> Groups 
>> >> "Project Jupyter" group. 
>> >> To unsubscribe from this group and stop receiving emails from it, send 
>> an 
>> >> email to [email protected]. 
>> >> To post to this group, send email to [email protected]. 
>> >> To view this discussion on the web visit 
>> >> 
>> https://groups.google.com/d/msgid/jupyter/CAH4pYpTQPxATxutAZ8Y00wpe7757%2BV-LDYzkrm2UsWnvubeiuA%40mail.gmail.com.
>>  
>>
>> >> For more options, visit https://groups.google.com/d/optout. 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> Groups 
>> > "Project Jupyter" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an 
>> > email to [email protected]. 
>> > To post to this group, send email to [email protected]. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/jupyter/CAPDWZHxL6C2_iHp%3DHLp9fY%2BvPktXdWoZBPsAvjX4y5oxHrnc%3Dg%40mail.gmail.com.
>>  
>>
>> > 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>
>>
>> -- 
>> Brian E. Granger 
>> Associate Professor of Physics and Data Science 
>> Cal Poly State University, San Luis Obispo 
>> @ellisonbg on Twitter and GitHub 
>> [email protected] and [email protected] 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/2d11d6ff-2e4c-4275-af38-64cc262225f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to