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

Update README.md with ownership info #570

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

pseudoyim
Copy link
Contributor

No description provided.

[anaconda-pkg-base](https://hub.docker.com/r/continuumio/anaconda-pkg-base/tags?page=1&ordering=last_updated) | Package Automation Team | Container *without* a bootstrapped Anaconda installation with GCC | [![](https://img.shields.io/docker/v/continuumio/anaconda-pkg-base?sort=semver)](https://hub.docker.com/r/continuumio/anaconda-pkg-base) | [![](https://img.shields.io/docker/pulls/continuumio/anaconda-pkg-base)](https://hub.docker.com/r/continuumio/anaconda-pkg-base) | [![](https://img.shields.io/docker/stars/continuumio/anaconda-pkg-base)](https://hub.docker.com/r/continuumio/anaconda-pkg-base)

**Note regarding owners**:
- The `anaconda-pkg-*` images are owned by the Package Automation Team, but decisions about the contents of these Dockerfiles must be reviewed and approved by the Package Build Core Team.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- The `anaconda-pkg-*` images are owned by the Package Automation Team, but decisions about the contents of these Dockerfiles must be reviewed and approved by the Package Build Core Team.
- The `anaconda-pkg-*` images are owned by the Package Automation Team, but decisions about the contents of these Dockerfiles must be reviewed and approved by the Package Build Core Team, alternatively the Package Build Core Team may choose to make modifications themselves with final approval by the Package Automation Team.

(Or some alternative wording to reflect ~ the same)

@marcoesters
Copy link
Contributor

Can you explain why the internal ownership within Anaconda is important to document for this (public) repository?

@dbast
Copy link
Member

dbast commented Oct 16, 2024

agreeing to what @marcoesters says. This is a public repo, lets not document it like that.

A CODEOWNERS file (referencing groups) for specific folders could be of help (as that also auto assigns and notifies the group for PRs)... AND/OR splitting the repo and moving out the package build images to AnacondaRecipes org where they belong to (for better owner clarity) would be of help.

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

Successfully merging this pull request may close these issues.

4 participants