From d70b1192d71e7d2ad3822970c4182f12e4185697 Mon Sep 17 00:00:00 2001 From: Norwin Date: Wed, 30 Mar 2022 23:03:15 +0200 Subject: [PATCH 1/4] Improve package registry docs --- docs/content/doc/packages/overview.en-us.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/content/doc/packages/overview.en-us.md b/docs/content/doc/packages/overview.en-us.md index f7809fc8a37b..d5bd67032c50 100644 --- a/docs/content/doc/packages/overview.en-us.md +++ b/docs/content/doc/packages/overview.en-us.md @@ -20,6 +20,24 @@ The Package Registry can be used as a public or private registry for common pack {{< toc >}} +## Repository-Packages +A package always belongs to an owner (a user or organisation), not a repo. +To link an (already uploaded) package to a repository, open the settings page +on that package and choose a repository to link this package to. +The entire package will be linked, not just a single version. + +Linking a package results in showing that package in the repository's package list, +and shows a link to the repository on the package site (as well as a link to the repo issues). + +## Access Restrictions + +| Package owner type | User | Organization | +|--------------------|------|--------------| +| **read** access | public, if user is marked not private, otherwise user only | public, if org is public, otherwise org members only | +| **write** access | owner only | org members with admin or write access to the org | + +N.B.: These access restrictions are [subject to change](https://github.com/go-gitea/gitea/issues/19270), where more finegrained control will be added via a dedicated organization team permission,. + ## Supported package managers The following package managers are currently supported: From 0f288931219c1b8bc4197b675cc6c5ce8b160291 Mon Sep 17 00:00:00 2001 From: Norwin Date: Wed, 30 Mar 2022 23:08:22 +0200 Subject: [PATCH 2/4] move new content down --- docs/content/doc/packages/overview.en-us.md | 36 ++++++++++----------- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/docs/content/doc/packages/overview.en-us.md b/docs/content/doc/packages/overview.en-us.md index d5bd67032c50..1c2e704cf372 100644 --- a/docs/content/doc/packages/overview.en-us.md +++ b/docs/content/doc/packages/overview.en-us.md @@ -20,24 +20,6 @@ The Package Registry can be used as a public or private registry for common pack {{< toc >}} -## Repository-Packages -A package always belongs to an owner (a user or organisation), not a repo. -To link an (already uploaded) package to a repository, open the settings page -on that package and choose a repository to link this package to. -The entire package will be linked, not just a single version. - -Linking a package results in showing that package in the repository's package list, -and shows a link to the repository on the package site (as well as a link to the repo issues). - -## Access Restrictions - -| Package owner type | User | Organization | -|--------------------|------|--------------| -| **read** access | public, if user is marked not private, otherwise user only | public, if org is public, otherwise org members only | -| **write** access | owner only | org members with admin or write access to the org | - -N.B.: These access restrictions are [subject to change](https://github.com/go-gitea/gitea/issues/19270), where more finegrained control will be added via a dedicated organization team permission,. - ## Supported package managers The following package managers are currently supported: @@ -56,6 +38,24 @@ The following package managers are currently supported: **The following paragraphs only apply if Packages are not globally disabled!** +## Repository-Packages +A package always belongs to an owner (a user or organisation), not a repo. +To link an (already uploaded) package to a repository, open the settings page +on that package and choose a repository to link this package to. +The entire package will be linked, not just a single version. + +Linking a package results in showing that package in the repository's package list, +and shows a link to the repository on the package site (as well as a link to the repo issues). + +## Access Restrictions + +| Package owner type | User | Organization | +|--------------------|------|--------------| +| **read** access | public, if user is marked not private, otherwise user only | public, if org is public, otherwise org members only | +| **write** access | owner only | org members with admin or write access to the org | + +N.B.: These access restrictions are [subject to change](https://github.com/go-gitea/gitea/issues/19270), where more finegrained control will be added via a dedicated organization team permission,. + ## View packages You can view the packages of a repository on the repository page. From 4aee82f7f66a1e118317c2aadd7d311487646561 Mon Sep 17 00:00:00 2001 From: Norwin Date: Wed, 30 Mar 2022 23:09:40 +0200 Subject: [PATCH 3/4] add hint re upload a package --- docs/content/doc/packages/overview.en-us.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/content/doc/packages/overview.en-us.md b/docs/content/doc/packages/overview.en-us.md index 1c2e704cf372..3095c347afe1 100644 --- a/docs/content/doc/packages/overview.en-us.md +++ b/docs/content/doc/packages/overview.en-us.md @@ -56,6 +56,10 @@ and shows a link to the repository on the package site (as well as a link to the N.B.: These access restrictions are [subject to change](https://github.com/go-gitea/gitea/issues/19270), where more finegrained control will be added via a dedicated organization team permission,. +## Create or upload a package + +This depends on the type of package. Check out the sub-page for a specific package manager for instructions. + ## View packages You can view the packages of a repository on the repository page. From f3f11571292542d90a281b6fb98bf0448de00804 Mon Sep 17 00:00:00 2001 From: Norwin Date: Thu, 31 Mar 2022 03:13:41 +0200 Subject: [PATCH 4/4] wording, formatting --- docs/content/doc/packages/overview.en-us.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/content/doc/packages/overview.en-us.md b/docs/content/doc/packages/overview.en-us.md index 3095c347afe1..1e4209930f55 100644 --- a/docs/content/doc/packages/overview.en-us.md +++ b/docs/content/doc/packages/overview.en-us.md @@ -39,26 +39,27 @@ The following package managers are currently supported: **The following paragraphs only apply if Packages are not globally disabled!** ## Repository-Packages -A package always belongs to an owner (a user or organisation), not a repo. + +A package always belongs to an owner (a user or organisation), not a repository. To link an (already uploaded) package to a repository, open the settings page on that package and choose a repository to link this package to. The entire package will be linked, not just a single version. Linking a package results in showing that package in the repository's package list, -and shows a link to the repository on the package site (as well as a link to the repo issues). +and shows a link to the repository on the package site (as well as a link to the repository issues). ## Access Restrictions | Package owner type | User | Organization | |--------------------|------|--------------| -| **read** access | public, if user is marked not private, otherwise user only | public, if org is public, otherwise org members only | +| **read** access | public, if user is public too; otherwise for this user only | public, if org is public, otherwise org members only | | **write** access | owner only | org members with admin or write access to the org | -N.B.: These access restrictions are [subject to change](https://github.com/go-gitea/gitea/issues/19270), where more finegrained control will be added via a dedicated organization team permission,. +N.B.: These access restrictions are [subject to change](https://github.com/go-gitea/gitea/issues/19270), where more finegrained control will be added via a dedicated organization team permission. ## Create or upload a package -This depends on the type of package. Check out the sub-page for a specific package manager for instructions. +Depending on the type of package, use the respective package-manager for that. Check out the sub-page of a specific package manager for instructions. ## View packages