Create an Notice For Docker Image#75
Open
Jayesh45-master wants to merge 1 commit intoeclipse-lmos:mainfrom
Open
Create an Notice For Docker Image#75Jayesh45-master wants to merge 1 commit intoeclipse-lmos:mainfrom
Jayesh45-master wants to merge 1 commit intoeclipse-lmos:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #36
Title: Create an Notice For Docker Image
Description
This Pull Request introduces a dedicated NOTICE-DOCKER.md file (or notice.md) to provide legal transparency and compliance for our published container images.
As these images are intended for demonstration and development purposes, this notice ensures that downstream users are aware of the licensing boundaries and the provenance of the software contained within the image layers.
Changes
New Documentation: Added a comprehensive Docker Notice file including:
Project Context: Links to source code, DockerHub, and the specific Dockerfile.
License Clarification: Explicitly states that the project license (Apache 2.0) applies to the source code, while the image contains 3rd-party components under separate licenses.
Base Image Attribution: Details for the eclipse-temurin:20-jre-alpine base image and its source.
Usage Notice: Disclaimer regarding the experimental/demo nature of the image.
Why this is required
To comply with open-source distribution best practices, we must provide clear metadata regarding:
Transparency: Allowing users to audit how the image was built.
Legal Safety: Distinguishing between the application license and the system-level licenses (GPL/MIT/etc. found in Alpine/JRE layers).
Security: Providing a starting point for vulnerability scanning and license compliance audits.
Verification Checklist
[x] All URLs in the notice lead to active pages/files.
[x] The Dockerfile link points to the specific version on the main branch.
[x] Markdown formatting is verified and renders correctly.
[x] The notice follows the structure required by [Link to project guidelines if applicable].
Changelog
Add documentation notice for published Docker image
/label skip-changelog