From fb1e661ce75330e299afe26aea6351c551c7c2d1 Mon Sep 17 00:00:00 2001 From: Guillaume Tardif Date: Tue, 9 Jan 2024 09:43:40 +0100 Subject: [PATCH] Remove references to extension manual validation process (#18693) * Remove manual validation process Signed-off-by: Guillaume Tardif * Apply suggestions from code review Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> --------- Signed-off-by: Guillaume Tardif Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> --- .../extensions-sdk/extensions/publish.md | 53 ++++--------------- content/desktop/extensions/marketplace.md | 2 +- content/faq/security/general.md | 4 +- 3 files changed, 12 insertions(+), 47 deletions(-) diff --git a/content/desktop/extensions-sdk/extensions/publish.md b/content/desktop/extensions-sdk/extensions/publish.md index 67ac2ea675..048da64a93 100644 --- a/content/desktop/extensions-sdk/extensions/publish.md +++ b/content/desktop/extensions-sdk/extensions/publish.md @@ -7,18 +7,19 @@ keywords: Docker, extensions, publish ## Submit your extension to the marketplace Docker Desktop displays published extensions in the Extensions Marketplace on [Docker Desktop](https://open.docker.com/extensions/marketplace) and [Docker Hub](https://hub.docker.com/search?q=&type=extension). -The Extensions Marketplace is a curated space where developers can discover extensions to improve their developer experience and propose their own extension to be available for all Desktop users. +The Extensions Marketplace is a space where developers can discover extensions to improve their developer experience and propose their own extension to be available for all Desktop users. -Whenever you are [ready to publish](./DISTRIBUTION.md) your extension in the Marketplace, you have two publishing options: - -[Self-publish your extension](https://github.com/docker/extensions-submissions/issues/new?assignees=&labels=&template=1_automatic_review.yaml&title=%5BSubmission%5D%3A+) -[Request that Docker reviews your extension](https://www.docker.com/products/extensions/submissions/) +Whenever you are [ready to publish](./DISTRIBUTION.md) your extension in the Marketplace, you can [self-publish your extension](https://github.com/docker/extensions-submissions/issues/new?assignees=&labels=&template=1_automatic_review.yaml&title=%5BSubmission%5D%3A+) > **Note** > > As the Extension Marketplace continues to add new features for both Extension users and publishers, we expect you > to maintain your extension over time to ensure it stays available in the Marketplace. +> **Important** +> +> The Docker manual review process for extensions is paused at the moment. Submit your extension through the [automated submission process](https://github.com/docker/extensions-submissions/issues/new?assignees=&labels=&template=1_automatic_review.yaml&title=%5BSubmission%5D%3A+) +{ .important } ### Before you submit Before you submit your extension, it must pass the [validation](validate.md) checks. @@ -36,49 +37,15 @@ These guidelines don't replace Docker's terms of service or guarantee approval: - Test your extension on various platforms (Mac, Windows, Linux) - Read the [Terms of Service](https://www.docker.com/legal/extensions_marketplace_developer_agreement/) -### Which publishing option to choose +#### Validation process -When submitting an extension to the extensions submissions [repository](https://github.com/docker/extensions-submissions/issues/new/choose), you have two publishing options. Publish as either: -- A Self-published extension -- A Docker-reviewed extension - -Depending on which option you select, the publishing process will differ. - -#### Process for Self-published extensions - -Self-published extensions are automatically validated. If all the validation checks pass successfully, it is +Submitted extensions go through an automated validation process. If all the validation checks pass successfully, the extension is published on the Marketplace and accessible to all users within a few hours. It is the fastest way to get developers the tools they need and to get feedback from them as you work to -evolve/polish your extension. You can request a review from the Docker Extensions team at any time. +evolve/polish your extension. > **Important** > > Docker Desktop caches the list of extensions available in the Marketplace for 12 hours. If you don't see your -> extension in the Marketplace, you can restart Docker Desktop to force the cache to be refreshed. +> extension in the Marketplace, you can restart Docker Desktop to force the cache to refresh. { .important } - - -#### Process for Docker-reviewed extensions - -Docker-reviewed extensions are manually reviewed by the Docker Extensions team. This process ensures a level of trust -and quality for developers using Docker Extensions and allows extension developers to get feedback. - -Although we strive to have your submission approved as soon as possible, bear in mind this is a manual process to -ensure extensions meet high standards. If your extension is complex, if it doesn't follow the guidelines, or if you -didn't complete the submission form properly, it may take longer to review your extension. - -Once the extension is reviewed, we will do our best to provide adequate and actionable feedback for you so that you can -improve it. If your extension has been rejected, you can communicate directly with us. - -The review process also offers some advantages for extension developers of reviewed and approved extensions: -- The extension appears as **Reviewed** in the Marketplace -- The extension is added to our monthly "Docker Extensions Roundup" blog post -- The same blog post is featured in our monthly newsletter -- The extension is promoted on our social media channels -- You receive weekly reports on your extension's performance - -> **Note** -> -> If it doesn't meet the approval requirements for a reviewed extension, you can still publish it without a review, -> and get your extension in the hands of developers. However, you will not benefit from -> the advantages listed above. \ No newline at end of file diff --git a/content/desktop/extensions/marketplace.md b/content/desktop/extensions/marketplace.md index bc56674add..24bb40bf71 100644 --- a/content/desktop/extensions/marketplace.md +++ b/content/desktop/extensions/marketplace.md @@ -11,7 +11,7 @@ There are two types of extensions available in the Extensions Marketplace: Docker-reviewed extensions are manually reviewed by the Docker Extensions team to ensure an extra level of trust and quality. They appear as **Reviewed** in the Marketplace. -Self-published extensions are autonomously published by extension developers. They appear as **Not reviewed** in the Marketplace. +Self-published extensions are autonomously published by extension developers and go through an automated validation process. They appear as **Not reviewed** in the Marketplace. ## Install an extension diff --git a/content/faq/security/general.md b/content/faq/security/general.md index 6e8bb9c37f..f7ee6ae8ce 100644 --- a/content/faq/security/general.md +++ b/content/faq/security/general.md @@ -76,9 +76,7 @@ File sharing (bind mount from the host filesystem) uses a user-space crafted fil Security vetting for extensions is on our roadmap however this vetting isn't currently done. -At present in the marketplace, there are two types of extensions: reviewed and self-published. Reviewed extensions are used and reviewed against a set of criteria, and if they pass, they're included in the marketplace with a **Reviewed** label. Self-published extensions are automatically placed in the marketplace with a **Not reviewed** label. - -Note that even if an extension is reviewed, it's only reviewed on the first publish. Any updates afterwards aren't reviewed. Extensions aren't covered as part of Docker’s Third-Party Risk Management Program. +Extensions are not covered as part of Docker’s Third-Party Risk Management Program. ### Can I disable private repos in my organization via a setting to make sure nobody is pushing images into Docker Hub?