matthewmueller/joy

Licensing: Update examples & add License file

Open

#60 opened on Dec 13, 2017

View on GitHub
 (5 comments) (1 reaction) (0 assignees)Go (34 forks)github user discovery
good first issuehelp wanted

Repository metrics

Stars
 (1,317 stars)
PR merge metrics
 (PR metrics pending)

Description

From HN: https://news.ycombinator.com/item?id=15910300

Hey, great work! Just a heads up about licensing. JavaScript code fragments that you use inside the compiler to produce the final output are technically part of the source code, and thus the output is also GPLv3 licensed as a derived work.

That's a known GPL quirk, and other GPL-licensed compilers like GCC use a separate variant of GPL to avoid that collision.

You can see how GNU Bison does it: https://git.savannah.gnu.org/cgit/bison.git/tree/src/parse-g... since they put fragments of Bison code to the final generate source file. That's exactly what Joy does to generate JavaScript, so you should put similar notice to the repository.

Also, LICENCE file is not there.

Contributor guide

Research direction
Review the HN discussion and the GNU Bison documentation on GPL licensing for compiler output. Add a LICENSE file (e.g., GPLv3) and update examples to include the required notice.
Tech stack
go
Domain
toolingbackend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gitbasic understanding of open source licensing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70