<div dir="ltr">I also can't speak for Debian. But it is my understanding that Debian does not rely on OSI for determining if a license is free. They use their own Debian Free Software Guidelines. (Although they are very similar.) Someone at Debian maintains a FAQ on the DFSG [1]<div><br></div><div>Debian also has a Licensing page that is not exactly on point but suggests that you might want to contact the Debian Legal Mailing list. [2]</div><div><br></div><div>Warm regards,</div><div><br></div><div>-Marc</div><div><br></div><div>[1] <a href="https://people.debian.org/~bap/dfsg-faq">https://people.debian.org/~bap/dfsg-faq</a></div><div>[2] <a href="https://www.debian.org/legal/licenses/">https://www.debian.org/legal/licenses/</a></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 16, 2017 at 3:32 PM Tom Callaway <<a href="mailto:tcallawa@redhat.com">tcallawa@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" class="gmail_msg">Can't speak for Debian, but Fedora will happily take software licensed as you describe.</div><div class="gmail_extra gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg">On Mar 16, 2017 3:09 PM, "Karan, Cem F CIV USARMY RDECOM ARL (US)" <<a href="mailto:cem.f.karan.civ@mail.mil" class="gmail_msg" target="_blank">cem.f.karan.civ@mail.mil</a>> wrote:<br type="attribution" class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree that the Government can release it as open source, but as I understand it, not as Open Source. The difference is whether or not the code will be accepted into various journals (Journal of Open Source Software is one). It also affects whether or not various distributions will accept the work (would Debian? I honestly don't know).<br class="gmail_msg">
<br class="gmail_msg">
And I'm not after plain vanilla CC0 code to be called Open Source, I'm after the method I outlined earlier. This side-steps the need to have CC0 put forth by the license steward (I hope!). I know that is splitting hairs, but at this point I'm tearing my hair out over this, and would like to put it to rest before I have to buy a wig.<br class="gmail_msg">
<br class="gmail_msg">
Thanks,<br class="gmail_msg">
Cem Karan<br class="gmail_msg">
<br class="gmail_msg">
> -----Original Message-----<br class="gmail_msg">
> From: License-discuss [mailto:<a href="mailto:license-discuss-bounces@opensource.org" class="gmail_msg" target="_blank">license-discuss-bounces@opensource.org</a>] On Behalf Of Tzeng, Nigel H.<br class="gmail_msg">
> Sent: Thursday, March 16, 2017 2:48 PM<br class="gmail_msg">
> To: <a href="mailto:license-discuss@opensource.org" class="gmail_msg" target="_blank">license-discuss@opensource.org</a><br class="gmail_msg">
> Subject: Re: [License-discuss] [Non-DoD Source] Re: Possible alternative was: Re: U.S. Army Research Laboratory Open Source License (ARL<br class="gmail_msg">
> OSL) Version 0.4.1<br class="gmail_msg">
><br class="gmail_msg">
> All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links<br class="gmail_msg">
> contained within the message prior to copying and pasting the address to a Web browser.<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> ----<br class="gmail_msg">
><br class="gmail_msg">
> Cem,<br class="gmail_msg">
><br class="gmail_msg">
> The USG does not need OSI’s approval to release code as open source under CC0. It has done so already on <a href="http://code.gov" rel="noreferrer" class="gmail_msg" target="_blank">code.gov</a>. This includes the<br class="gmail_msg">
> OPM, NASA, GSA, DOT, DOL, DOC and others. CC0 is compliant with the Federal Source Code Policy for open source release.<br class="gmail_msg">
><br class="gmail_msg">
> It is unlikely that you can push CC0 through license review as you aren’t the license steward. It is up to CC to resubmit CC0 for approval.<br class="gmail_msg">
><br class="gmail_msg">
> Regards,<br class="gmail_msg">
><br class="gmail_msg">
> Nigel<br class="gmail_msg">
><br class="gmail_msg">
> On 3/16/17, 8:56 AM, "License-discuss on behalf of Karan, Cem F CIV USARMY RDECOM ARL (US)" <license-discuss-<br class="gmail_msg">
> <a href="mailto:bounces@opensource.org" class="gmail_msg" target="_blank">bounces@opensource.org</a> on behalf of <a href="mailto:cem.f.karan.civ@mail.mil" class="gmail_msg" target="_blank">cem.f.karan.civ@mail.mil</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> All, I want to keep this alive as I haven't seen a conclusion yet. Earlier I<br class="gmail_msg">
> asked if OSI would accept the US Government (USG) putting its non-copyrighted<br class="gmail_msg">
> works out under CC0 as Open Source **provided** that the USG accepts and<br class="gmail_msg">
> redistributes copyrighted contributions under an OSI-approved license. Is<br class="gmail_msg">
> this acceptable to OSI? Should I move this discussion to the license-review<br class="gmail_msg">
> list?<br class="gmail_msg">
><br class="gmail_msg">
> To recap:<br class="gmail_msg">
><br class="gmail_msg">
> 1) This would only cover USG works that do not have copyright. Works that<br class="gmail_msg">
> have copyright would be eligible to use copyright-based licenses, and to be<br class="gmail_msg">
> OSI-approved as Open Source would need to use an OSI-approved license.<br class="gmail_msg">
><br class="gmail_msg">
> 2) The USG work/project would select an OSI-approved license that it accepted<br class="gmail_msg">
> contributions under. The USG would redistribute the contributions under that<br class="gmail_msg">
> license, but the portions of the work that are not under copyright would be<br class="gmail_msg">
> redistributed under CC0. That means that for some projects (ones that have no<br class="gmail_msg">
> copyrighted material at all initially), the only license that the works would<br class="gmail_msg">
> have would be CC0.<br class="gmail_msg">
><br class="gmail_msg">
> I can't speak to patents or other IP rights that the USG has, I can only<br class="gmail_msg">
> comment on what the Army Research Laboratory (ARL) has done<br class="gmail_msg">
> (Caution-<a href="https://github.com/USArmyResearchLab/ARL-Open-Source-Guidance-and-Instructions" rel="noreferrer" class="gmail_msg" target="_blank">https://github.com/USArmyResearchLab/ARL-Open-Source-Guidance-and-Instructions</a>),<br class="gmail_msg">
> which includes a step to affirmatively waive any patent rights that ARL might<br class="gmail_msg">
> have in the project before distributing it. I am hoping that other agencies<br class="gmail_msg">
> will do something similar, but have no power or authority to say that they<br class="gmail_msg">
> will.<br class="gmail_msg">
><br class="gmail_msg">
> Given all this, is it time to move this to license-review, or otherwise get a<br class="gmail_msg">
> vote? I'd like this solved ASAP.<br class="gmail_msg">
><br class="gmail_msg">
> Thanks,<br class="gmail_msg">
> Cem Karan<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> _______________________________________________<br class="gmail_msg">
> License-discuss mailing list<br class="gmail_msg">
> <a href="mailto:License-discuss@opensource.org" class="gmail_msg" target="_blank">License-discuss@opensource.org</a><br class="gmail_msg">
> Caution-<a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss</a><br class="gmail_msg">
<br class="gmail_msg">_______________________________________________<br class="gmail_msg">
License-discuss mailing list<br class="gmail_msg">
<a href="mailto:License-discuss@opensource.org" class="gmail_msg" target="_blank">License-discuss@opensource.org</a><br class="gmail_msg">
<a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss</a><br class="gmail_msg">
<br class="gmail_msg"></blockquote></div></div>
_______________________________________________<br class="gmail_msg">
License-discuss mailing list<br class="gmail_msg">
<a href="mailto:License-discuss@opensource.org" class="gmail_msg" target="_blank">License-discuss@opensource.org</a><br class="gmail_msg">
<a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss</a><br class="gmail_msg">
</blockquote></div>