Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete Docker-Sponsored Open Source (DSOS) application process #399

Open
6 of 7 tasks
d33bs opened this issue Apr 3, 2024 · 2 comments
Open
6 of 7 tasks

Complete Docker-Sponsored Open Source (DSOS) application process #399

d33bs opened this issue Apr 3, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@d33bs
Copy link
Member

d33bs commented Apr 3, 2024

This issue continues work towards efforts mentioned in #214 to gain Docker-Sponsored Open Source (DSOS) sponsorship based on feedback received from Docker. This work may involve additional updates to how Docker images are configured, how the Docker Hub repository is updated, or related.

Hi Gregory Way,
During our review of your application for Cytomining, we determined that while your project meets most of the program requirements, there is a lack of documentation in one or more of your repositories on Docker Hub. As stated in the Qualification Criteria section of our webpage, we encourage the authors of open-source projects to include documentation that meets the recommended community standards. This means a detailed project description on your Docker Hub repository pages that includes a link to your project source code, licensing information, and a general overview. Projects lacking this information might not receive the Docker Sponsored Open Source badge for their images on Docker Hub. If you would still like to be a part of the Docker-Sponsored Open Source program, we invite you to re-submit an application once you have updated the documentation for your project. If you feel we have made a mistake in our review of your application please feel free to contact us at [email protected]
Thank you!

Originally posted by @gwaybio in #214 (comment)

Adding a list for the suggested content / checks before resubmitting:

Consider the following repository overview best practices.

  • Describe what the image is, the features it offers, and why it should be used. Can include examples of usage or the team behind the project.
  • Explain how to get started with running a container using the image. You can include a minimal example of how to use the image in a Dockerfile.
  • List the key image variants and tags to use them, as well as use cases for the variants.
  • Link to documentation or support sites, communities, or mailing lists for additional resources.
  • Provide contact information for the image maintainers.
  • Include the license for the image and where to find more details if needed.
  • You will need to reapply after those changes to your Docker Hub account are met.
@d33bs d33bs added the enhancement New feature or request label Apr 3, 2024
@d33bs
Copy link
Member Author

d33bs commented Apr 17, 2024

Possibly related, there is also a "Docker Verified Publisher Program" which allows for things like modifying the image for Docker Hub logos, among other things. I wonder if accomplishing this before would influence the approval of the DSOS application? Application for this is here: https://www.docker.com/partners/programs/ , documentation may be found here: https://docs.docker.com/trusted-content/dvp-program/

@d33bs
Copy link
Member Author

d33bs commented Apr 22, 2024

Hi @gwaybio, in the process of filling out the checklist that Docker suggested, I noticed we may need to provide a contact email address to help complete the DSOS re-application ("Provide contact information for the image maintainers."). Would it be appropriate to use [email protected] for this? Or should we use a different email address?

As a follow up here, I ended up using the contributing guidelines and references to GitHub issues to help navigate the contact part of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant