Re: [License-discuss] Guidance for making license information available to users

2017-10-23 Thread Philippe Ombredanne
master/MIT-License.txt [2] https://github.com/ghusse/jQRangeSlider/blob/master/GPL-License.txt [3] https://opensource.stackexchange.com/a/4587/947 [4] https://opensource.stackexchange.com/a/4582/947 [5] https://spdx.org/sites/cpstandard/files/pages/files/using_spdx_license_list_short_identifiers.pdf [6] https://patchwork.kernel.or

Re: [License-discuss] notes on a systematic approach to "popular" licenses

2017-04-09 Thread Philippe Ombredanne
hich represents a significant[sic] number of terabytes. This could become a lesser issue on the fetch side when softwareheritage.org is fully operational. But still. If anyone is interested by this, please contact me! -- Cordially Philippe Ombredanne ___

Re: [License-discuss] notes on a systematic approach to "popular" licenses

2017-04-09 Thread Philippe Ombredanne
acode.com/licenses/ Every OSI licenses (and more) conditions have been carefully tagged as seen here: https://enterprise.dejacode.com/licenses/Demo/apache-2.0/#license-conditions (disclosure: this is a product of my company) -- Cordially Philippe Ombredanne __

Re: [License-discuss] notes on a systematic approach to "popular" licenses

2017-04-09 Thread Philippe Ombredanne
> On Thu, Apr 6, 2017 at 6:19 PM Philippe Ombredanne > wrote: >> >> On Thu, Apr 6, 2017 at 5:21 PM, Luis Villa wrote: >> > On Tue, Jan 10, 2017, 11:07 AM Luis Villa wrote: >> >> >> >> Hey, all- >> >> I promised some board membe

Re: [License-discuss] notes on a systematic approach to "popular" licenses

2017-04-06 Thread Philippe Ombredanne
licenses" list. Here >> goes. [...] > Yet another (inevitably flawed) data set: > https://libraries.io/licenses With the merit that the all the underlying code is FLOSS. Another possible source --always biased-- could be Debian's popcon and so

Re: [License-discuss] License Question

2017-02-16 Thread Philippe Ombredanne
ays and its mailing lists pages are 404. - or if one feels strongly about the topic, public shaming? [1] https://www.gnu.org/licenses/gpl-violation.en.html [2] http://gpl-violations.org -- Cordially Philippe Ombredanne ___ License-discuss m

Re: [License-discuss] US Army Research Laboratory Open Source License proposal

2016-07-23 Thread Philippe Ombredanne
Since US government does not attract copyright > I am unsure if they can attract copyright in other jurisdictions. Maarten, are you suggesting then that the lack of copyright for a U.S. Federal Government work would just then apply elsewhere too and that using an alternative Apache license would not

Re: [License-discuss] US Army Research Laboratory Open Source License proposal

2016-07-23 Thread Philippe Ombredanne
still address your needs? -- Cordially Philippe Ombredanne +1 650 799 0949 | pombreda...@nexb.com DejaCode : What's in your code?! at http://www.dejacode.com nexB Inc. at http://www.nexb.com ___ License-discuss mailing list License-discuss@opens

Re: [License-discuss] Source-attribution licenses and Javascript compatibility

2016-05-31 Thread Philippe Ombredanne
On Fri, May 20, 2016 at 4:06 AM, Andi McClure wrote: > I am working on some projects (a programming language, a game library) for > which I wish to use a "source attribution" license-- for example, the zlib > license, or the 2-clause BSD license if I could somehow delete the second > clause. I wan

Re: [License-discuss] Trove Classifiers

2016-05-08 Thread Philippe Ombredanne
ing. [1] The harder or impossible part would have be to clean up the 1000+ of packages using this faulty classifier But there is really only three of these [2] and all of them look either pretty old or abandoned and none has its packages effectively hosted or distributed on Pypi. [1]

Re: [License-discuss] Open Source License API Soft-launch

2016-05-01 Thread Philippe Ombredanne
gether! > > You can find the Open Source API at: > >https://api.opensource.org/ Very nice. Congrats and thanks! -- Cordially Philippe Ombredanne ___ License-discuss mailing list License-discuss@opensource.org https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss

Re: [License-discuss] Any Free License, an open source license

2015-11-14 Thread Philippe Ombredanne
f the choices? What if the terms conflicts? Must I pick one license among them all? Must I or can I or not pass this choice downstream? To be clear you would need to address all these (and likely many other) related issues.... So this may not be such a good idea after all. -- Cordially Philippe

Re: [License-discuss] BSD 3-clause and copyright notices

2015-10-01 Thread Philippe Ombredanne
e less likely anyone will want to contribute anything. I would not touch code with such a weird waiver (even with a very long pole). And If you are lucky enough to ever receive contributions from others, giving credit whether required or not is _always_ the right thi

On the licensing terms of the open source licenses text

2004-07-10 Thread Philippe Ombredanne
ense text? And if I use an existing OSI approved license as a base, would I need to go through the full legal commentary to submit it for approval? (BTW, I know this was debated in the past, but did not find any conclusion on the topic. -- Cheers Philippe philippe ombredanne | nexB - Open IT Asset Man

On the licensing terms of the open source licenses text

2004-07-09 Thread Philippe Ombredanne
ense text? And if I use an existing OSI approved license as a base, would I need to go through the full legal commentary to submit it for approval? (BTW, I know this was debated in the past, but did not find any conclusion on the topic. -- Cheers Philippe philippe ombredanne | nexB - Open IT Asset Man