You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OSS artefacts should be accessible to everyone without the need to authenticate or provide credentials.
FURTHER CONSIDERATIONS
For every artefact there are certain aspects to consider, for example Maven artefacts need to be published through an Eclipse Jenkins instance.
Docker images must come with a Notice, which must also be available on DockerHub, etc.
This issue serves as umbrella issue, to track several subtasks:
WHAT
To keep up the conventions of OSS projects we should publish our artefacts to publicly accessible and well-known locations, specifically:
WHY
OSS artefacts should be accessible to everyone without the need to authenticate or provide credentials.
FURTHER CONSIDERATIONS
For every artefact there are certain aspects to consider, for example Maven artefacts need to be published through an Eclipse Jenkins instance.
Docker images must come with a Notice, which must also be available on DockerHub, etc.
This issue serves as umbrella issue, to track several subtasks:
Setup and implement publishing Helm Charts to ArtifactHubThe text was updated successfully, but these errors were encountered: