Hi Jilayne, For the license to receive adoption it needs to be on the SPDX License List. I am but I small Fish in a large pond.
The ideal outcome is to provide a common template for a simple permissive canonical crypto license to make it simple for users to add crypto wallet addresses as mentioned in the Hacker Noon article. Ideally we can avoid license proliferation here but I need to have a new template accepted for the copyright statement to show the proper way to use it. Will that necessitate the creation of a unique new license text, or can this be done creatively without causing a new license in terms? Regards, Josh On Wed, Jul 12, 2017 at 6:32 AM J Lovejoy <opensou...@jilayne.com> wrote: > Hi Josh, > > As this is the exact same license text as ISC, save for the copyright line > which is not counted as for purposes of matching license texts as per the > SPDX License List Matching Guidelines, there is no need to add this to the > SPDX License List, as the license would be identified as or matched to ISC. > Thus, if one wanted to use an SPDX short identifier to refer to this > license, they would use the short identifier ISC license (which is “ISC”). > The copyright line can be different, the license is still the same. > > I’m not sure if you are familiar with the larger SPDX project, but the > SPDX specification serves the goal to create a standard way to identify the > license, copyright, provenance, and other such information in a software > ‘bill of materials’. This effort was born out of the reality that companies > along the supply chain ask for and exchange this information and by having > a standard way to report this data, redundant work can be reduced. When > the SPDX specification first was getting started, we recognized the need > for a reliable and concise way to refer to common licenses in an SPDX > document (instead of having to repeat the license over and over). This, in > turn would also help prevent those people processing such information from > having to read the same license over and over. And so, the SPDX License > List was born. > > Of course, there is a need for a reliable and concise way to refer to > common licenses in many other instances besides an SPDX document and so the > SPDX License List has seen adoption in a host of other ways. Notably, > developers are using the short identifiers as a concise, reliable, and > machine-readable way to identify the license on a per-file basis (for > example: > https://github.com/ARM-software/arm-trusted-firmware/blob/master/lib/aarch32/cache_helpers.S > ). > This ensures the license goes with the file (even if the license file > doesn’t follow the rest of the code files) which is immensely helpful for > licensers and downstream recipients. Whether you use the standard license > header as is recommended by the license (if there is one) or the SPDX > identifier or the entire license text for shorter licenses - identifying > the license in every file is recommended practice by the FSF*, Apache > Foundation, Eclipse Foundation, etc. Anyway, I mention this because your > articles cites the distraction of long license headers as well as your > unfortunate experience of someone copying your code without retaining your > copyright notice and the license (I’m sorry to hear about this and yes, I > think you should say something to this person - a gentle reminder may often > be enough to correct the error!). > > I’m not sure what else to tell you here. I don’t think any license really > prevents you from replacing your name in the copyright notice with a > bitcoin address. I’m also not sure this change, which is not a change to > the license, will make FOSS licensing sexy, but then again, nothing may > achieve that goal! ;) > > Finally and on a slightly separate note - your assertion that there are > some "20 odd licenses now awaiting review” by the SPDX Legal team is > incorrect. > > > Thanks, > Jilayne > > SPDX Legal Team co-lead > opensou...@jilayne.com > > > On Jul 5, 2017, at 7:04 PM, Josh Habdas <jhab...@gmail.com> wrote: > > I can change something insignificant if it helps, but this seemed better > On Thu, Jul 6, 2017 at 2:03 AM Josh Habdas <jhab...@gmail.com> wrote: > >> It's the exact same, in fact. Save for the copyright line. And here's why >> this new license is important: >> >> >> https://medium.com/@jhabdas/introducing-the-btc-license-28650887eb11?source=linkShare-d4a43ea991d3-1499277791 >> On Thu, Jul 6, 2017 at 1:57 AM Richard Fontana <rfont...@redhat.com> >> wrote: >> >>> This seems to be equivalent to the ISC license from an SPDX point of >>> view (see https://spdx.org/spdx-license-list/matching-guidelines: >>> " Ignore copyright notices. A copyright notice consists of the following >>> elements, for example: "2012 Copyright, John Doe. All rights reserved." or >>> "(c) 2012 John Doe." Templates may or may not include markup for this >>> guideline.") >>> >>> >>> ------------------------------ >>> >>> From: "Josh Habdas" <jhab...@gmail.com> >>> To: spdx-legal@lists.spdx.org >>> Sent: Wednesday, July 5, 2017 12:52:38 AM >>> Subject: New License/Exception Request: BTC License (BTC) >>> >>> For consideration during the next SPDX Legal Team meeting. >>> >>> Full name: BTC License >>> Identifier: BTC >>> URL: https://gist.github.com/jhabdas/9fc645415bf277e3a1f3bc5c04083f01 >>> OSI: Not OSI-submitted nor approved >>> Explanation: Verbatim copy of ISC, with updated copyright line intended >>> to protect individual privacy and facilitate transmission of funds to >>> creators of open source work. Example use within software provided below. >>> >>> Example LICENSE text file . >>> Example license header . >>> Example abbreviated license header . >>> >>> Thank you for your consideration. >>> >>> Regards, >>> Josh Habdas >>> >>> >>> _______________________________________________ >>> Spdx-legal mailing list >>> Spdx-legal@lists.spdx.org >>> https://lists.spdx.org/mailman/listinfo/spdx-legal >>> >> _______________________________________________ > Spdx-legal mailing list > Spdx-legal@lists.spdx.org > https://lists.spdx.org/mailman/listinfo/spdx-legal > > >
_______________________________________________ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
