Modify open-source code and redistribute it.
Allow recipients to distinguish the original code from the changes.
Which action is generally appropriate?
Keep original notices and record modifications and dates as required so recipients can understand the applicable license.
Detailed explanation
Correct. Preserving notices and documenting changes supports transparency and license compliance.
Correct. Preserving notices and documenting changes supports transparency and license compliance.
Incorrect. Removing the original notice and claiming sole authorship can violate the license.
Incorrect. Removing the original notice and claiming sole authorship can violate the license.
Incorrect. License files and notices may need to accompany the distribution.
Incorrect. License files and notices may need to accompany the distribution.
Incorrect. Failing to record or disclose changes reduces transparency.
Incorrect. Failing to record or disclose changes reduces transparency.
Try it yourself
An example you can run in a temporary verification environment.
printf '%s\n' 'preserve notices and document modifications'Expected result
preserve notices and document modificationsKey points
- Copyright notice
- Change record
- License file
Notes
- Environment: OSS再配布時の一般的な確認
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.