Comments (12)
Not a maintainer here, but I think the license text here comes directly from the relevant upstream's official license files, usually completely unchanged (and I've filed at least one PR to close a discrepancy between upstream's file and the file here; #20).
from licenses.
Got it. Maybe then the placeholder location should be annotated in another
file? I believe a saw some files that already contain metadata information.
On Apr 26, 2016 4:12 PM, "Tianon Gravi" [email protected] wrote:
Not a maintainer here, but I think the license text here comes directly
from the relevant upstream's official license files, usually completely
unchanged (and I've filed at least one PR to close a discrepancy between
upstream's file and the file here; #20
#20).—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#31 (comment)
from licenses.
Yeah! So, I love this idea, but I love the idea of taking out the templates
for source headers and letting folks write out source headers.
The question is, what is the best language agnostic choice?
Let's split this out into text/templates - I have a flight tonight, I might
PoC this!
On Apr 26, 2016 4:03 PM, "mspiegel" [email protected] wrote:
Great project! Is there any interest in either standardizing or maybe some
meta data annotation the placeholders that are present in the full text of
several of the licenses? Some of the licenses use square brackets, some use
angle brackets, some use an underscore, etc. Identifying the placeholders
is one way to automatically infer the license from the full text. Or maybe
there is another approach that I am missing.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#31
from licenses.
I was thinking about taking a stab at this. @paultag is that ok with you?
from licenses.
Go for it! All yours!
On Apr 26, 2016 7:55 PM, "mspiegel" [email protected] wrote:
I was thinking about taking a stab at this. @paultag
https://github.com/paultag is that ok with you?—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#31 (comment)
from licenses.
Thanks! Safe travels.
from licenses.
I have a question to give me some additional background about this project: why not leverage the SPDX tools? There seems to be a lot of potential with that group. Granted a lot of the work remains to be done. Specifically http://schd.ws/hosted_files/collabsummit2016/49/Unpected%20Journey%20License%20Matching%20-%202016%20Collab%20Presentation%20-V3.pdf,
http://wiki.spdx.org/view/Legal_Team/Template_proposal, and
https://github.com/myndzi/license-list/tree/xml-test/src.
I'm going to do some more reading into the SPDX tools.
from licenses.
Seems like a fun serialization target, maybe file a PR (or another repo) to
do the transformation into XML
On Apr 26, 2016 9:42 PM, "Michael Spiegel" [email protected] wrote:
I have a question to give me some additional background about this
project: why not leverage the SPDX tools? There seems to be a lot of
potential with that group. Granted a lot of the work remains to be done.
Specifically
http://schd.ws/hosted_files/collabsummit2016/49/Unpected%20Journey%20License%20Matching%20-%202016%20Collab%20Presentation%20-V3.pdf
,
http://wiki.spdx.org/view/Legal_Team/Template_proposal, and
https://github.com/myndzi/license-list/tree/xml-test/src.I'm going to do some more reading into the SPDX tools.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#31 (comment)
from licenses.
@mspiegel Anything worth noting that you've learned? As far as I can tell, they're mostly using XML as a template language, which I'm tempted not to do, seems like a ton of complexity. Honestly, just using a Go template, and allowing multiple "output" formats in other popular template frameworks (such as Jinja) seems fine for now.
Want to take a crack at a PoC with 3-4 licenses up against here and the API?
from licenses.
I think I'm missing some context: I see some overlap between the efforts of the open source initiative and the SPDX community. The SPDX machine readable license effort is currently evolving it is not yet complete. What I like about the effort is that there seems to be a community of people involved, and some of them work on products that test for license compliance. From the discussion on the wikis and the mailing list the people with background experience seem willing to share that experience. What I don't like about the SPDX community is that progress on the standard is scattered across a wiki, a mailing list, an internal git repository, and a separate issue tracking system. But I've seen on their roadmap they might be moving everything to GitHub this year. I'm going to try to lend my efforts to the SPDX work, I am seeing that standard being picked up by several communities.
from licenses.
@mspiegel This work is not incompatible - this is simply a canonical aggregation about the status of open source licenses, as defined by the OSI. Crosswalks to SPDX, which are already in the dataset, will allow the existing SPDX work to automatically pull OSI approval status (and other metadata that we might add) into the SPDX work.
That being said, you should spend your time how you want your time to be spent, and I would be thrilled to see more work going into SPDX :) 👍
from licenses.
Hi all! Returning to the project for a restart, I wonder if this issue still has legs and if so how to handle going forward?
from licenses.
Related Issues (20)
- Add is compatibleinterface to API HOT 1
- Compilation issues with python 2.7 HOT 4
- legally-significant MPL formatting lost HOT 3
- Is this still not authoritative? HOT 10
- OPL-2.1 metadata doesn't contain a link to it's page on opensource.org HOT 1
- eCos License version 2.0 and Free Public License 1.0.0 are missing HOT 2
- Why is BSD-4 tagged as osi-approved? HOT 2
- BSD-4 text really is BSD-3
- Record rejected licenses? HOT 9
- Is the repo still maintained? HOT 5
- Missing SPDX identifier data HOT 14
- Question: What are the steps to add a new license already on the OSI website? HOT 5
- Add previous versions of the AFL licenses HOT 8
- Update API and license data to permit versioned data retrieval HOT 1
- Where do "Notes" go?
- Unable to access https://api.opensource.org Origin DNS error 1016 HOT 2
- OPL-2.1 text is OSET Public License version 2.0 (not 2.1)
- Move from validictory to jsonschema
- Motosoto license text is incomplete HOT 8
- New table format missing many SPDX ids HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from licenses.