Fix name pattern for DockerHub organisations
Compare changes
+ 1
− 1
@@ -558,7 +558,7 @@ For more information, please see {cbiUrl}#docker-hub[CBI/DockerHub] in the Eclip
Content distributed via official Eclipse Foundation channels must be complete enough that a consumer can (with reasonable effort) use it without needing the DockerHub distribution. That is, the DockerHub distribution needs to be considered a convenient way to leverage the content, not the only way. Please make sure that you treat any links or related discussion that you have on an Eclipse Foundation property about images distributed via DockerHub as an unofficial channel.
Subject to the xref:resources-external[rules for the use of external resources], a project team can create and maintain their own organisation on DockerHub. The organisation name must follow the pattern `{forgeMachineName}-<shortname>` (e.g. `{forgeMachineName}-woolsey`) or some variation (e.g. `{forgeMachineName}woolsey`). As indicated in the rules, ownership of the organisation must be shared by a subset of project *committers* and the project must have a documented policy regarding how access to that organisation is managed.
Subject to the xref:resources-external[rules for the use of external resources], a project team can create and maintain their own organisation on DockerHub. The organisation name must follow the pattern `{forgeMachineName}<shortname>` (e.g. `{forgeMachineName}woolsey`). Please note that DockerHub does not support the dash character (`-`) in organisation names. As indicated in the rules, ownership of the organisation must be shared by a subset of project *committers* and the project must have a documented policy regarding how access to that organisation is managed.