matthewmueller / matthewmueller/joy
Licensing: Update examples & add License file
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
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
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository root for its existing licensing information and the examples referenced by the issue, then compare the requested notice with the linked GNU Bison approach. Done means the repository has the requested License file and the examples include an appropriate licensing notice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100