https://github.com/Sirikon/legalfile-proposal

Legalfile - A proposal for defining software legal terms in a structured way
https://github.com/Sirikon/legalfile-proposal

Last synced: 2 months ago
JSON representation

Legalfile - A proposal for defining software legal terms in a structured way

• Host: GitHub
• URL: https://github.com/Sirikon/legalfile-proposal
• Owner: sirikon
• Created: 2018-03-04T02:24:11.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2018-03-05T00:18:28.000Z (almost 7 years ago)
• Last Synced: 2024-08-04T04:03:46.677Z (6 months ago)
• Homepage:
• Size: 1.95 KB
• Stars: 36
• Watchers: 5
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• starred-awesome - legalfile-proposal - Legalfile - A proposal for defining software legal terms in a structured way (Others)

README

        
# Legalfile Proposal #

Legalfile - A proposal for defining software legal terms in a structured way.

First of all, **I'm not a lawyer**, and my knowledge on legal terms is pretty limited. This was motivated by an open-space session in WeCodeFest 2018 and talking with more experienced people, I thought that this could be useful, exposed the idea, and was well received.

![HN](https://news.ycombinator.com/y18.gif) [Link to discussion in HackerNews here.](https://news.ycombinator.com/item?id=16513016)

## Why ##

Today, software licensing is really important, and should be done **well**. But we're used to search for a package that fit our needs and just use it without seeing the software's license, which is a plain text file inside the repository.

What if we could see, automatically, the legal terms of any software, and even see if it fits with our needs?

For example: "Is commercial use forbidden for any of the installed packages?". "What's the list of all the people and projects that should be referenced based on the licenses?".

All this could be done directly making a database of simplified terms for the most known licenses (Something that tldrlegal.com does well), but to enable this level of automation, defining this terms inside a file in our projects could ease the process a lot, and having an open standard for doing this would be even better.

We could even build our own license with some builder, that outputs a `LICENSE.txt` and a `Legalfile`.

## The Legalfile ##

```yaml

license:

    name: MIT # Name of the license, if any.

    can: # Things that the license explicitly allows.

        - commercial-use

        - modify

        - distribute

        - sublicense

        - private-use

    cannot: # Things that the license explicitly forbids.

        - hold-liable

    must: # Requirements to use the software.

        - include-copyright

        - include-license

    warn:

        - "This area could be used to describe some perks of the license that isn't supported yet by a, right now, imaginary standard."

```

Why YAML?




Well-known language, implementations in any language, human-readable and easy to write.

## It's a proposal, so, I'm looking for feedback and discussion on this ##

I think it's an important topic, and that having legal terms in this way in every project could be **so** useful.

Be free to make pull requests, write issues and everything :D

## Duplicated? ##

I searched and talked with some people, no one knew nothing similar to this. I could be wrong, anyway.

If it's duplicated, let me know in an issue :) Thanks!