licensing of generated code
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 35
- Forks
- 14
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
From @hansenms 's email
- The yardl tool is MIT license.
- During code generation, there are some hand crafted files that are copied with the generated code, they are MIT too, we should stick that license on them.
- The yardl specification that the user writes can be whichever license they want. We would recommend MIT.
- The code that is truly generated can have any license that the user wants. We recommend MIT.
- We should add a feature to yardl, that allows you to put a license file in the _package directory, it should be emitted with the generated code. We may have to think about how that is transparent in the generated directory which license applies to what. There could be a mix of licenses in 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 tracing Yardl’s code-generation path and how the _package directory is handled. Define how a user-provided license is emitted with generated code and how mixed licenses remain identifiable, while preserving the stated MIT licensing distinctions for the tool and hand-crafted files. Done means the licensing behavior is implemented and its scope is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100