Skip to content

Commit f072018

Browse files
committed
Merge pull request #36 from riekrh/authoritative_source_3rd
README.md: Add authoritative_source and distribution_scope labels, ad…
2 parents 31974d5 + fc28c6a commit f072018

1 file changed

Lines changed: 25 additions & 0 deletions

File tree

README.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ distribution specific.
1111

1212
If you would like to see additional names and descriptions added please open issues and send pull requests to update this readme.
1313

14+
## Overview
15+
1416
The following types of data are being considered:
1517

1618
1. Labels used to describe how to use the application/image
@@ -40,3 +42,26 @@ The following types of data are being considered:
4042
| vcs_type | The type of version control used by the container source. Generally one of git, hg, svn, bzr, cvs|
4143
| vcs_url | URL of the version control repository|
4244
| vcs_ref | A 'reference' within the version control repository; e.g. a git commit, or a subversion branch|
45+
| authoritative_source | The authoritative location in which the image is published|
46+
| distribution_scope | Intended scope of distribution for image (see below for possible values)|
47+
48+
3. Possible values of distribution_scope field
49+
50+
|Name | Description |
51+
|-------------|-------------|
52+
| private | No public redistribution intended|
53+
| authoritative_source_only | Redistribution only from the source listed in the 'authoritative_source' label|
54+
| restricted | Redistribution only with permission|
55+
| public | No redistribution limits beyond licenses|
56+
57+
58+
## Details on Labels
59+
60+
## authoritative_source
61+
* The authoritative location the image is published by the owner.
62+
* In combination with the 'name' label, this tells a user where to go and look for official updates and current versions of the image, regardless of the local tags.
63+
64+
## distribution_scope
65+
* The intended scope of distribution for the image.
66+
* Allows a user to define the intended scope of distribution. This addresses the end-user case of internal builds vs. public content and the use case of a vendor like Red Hat that provides content streams under subscription agreements - which is different from the license(s) of the image content.
67+
* In combination with the 'authoritative_source' and 'name' labels allows automatic redirect to the authoritative source.

0 commit comments

Comments
 (0)