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

Merge conda-package-streaming and conda-package-handling teams #1007

Closed
2 tasks done
dholth opened this issue Aug 14, 2024 · 5 comments
Closed
2 tasks done

Merge conda-package-streaming and conda-package-handling teams #1007

dholth opened this issue Aug 14, 2024 · 5 comments
Labels
type::feature request for a new feature or capability

Comments

@dholth
Copy link
Contributor

dholth commented Aug 14, 2024

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

There is a separate conda-package-streaming team, and a separate conda-index team. These do not have enough members.

Merge with the amorphus team managing conda-package-handling?

Why is this needed?

No response

What should happen?

No response

Additional Context

No response

@dholth dholth added the type::feature request for a new feature or capability label Aug 14, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Aug 14, 2024
@jezdez
Copy link
Member

jezdez commented Aug 26, 2024

For the record, the teams are separate for historic reasons, as a reminder, per governance policy:

A Project Team is a sub-team with a dynamic charter, except for a few caveats as detailed here. They exist to maintain a specific project (or possibly set of projects). Each project in conda or conda-incubator should belong to exactly one Project Team.

conda-package-handling is being owned by the legacy conda-core team, which is bound to be deprecated in favor of a more fine-grained set of project teams. See for example the ticket about moving conda/conda into a community project team: conda/conda#13526

conda-package-streaming is maintained by a community project team, and graduated the project in conda/conda-package-streaming#31 to the main conda organization.

My suggestion is basically to:

The following people with access to conda-package-handling have to agree (please check the checkbox if you agree, or comment if you abstain or disagree):

@marcelotrevisani
Copy link
Member

The checkbox is not working for me but I agree.

@jezdez
Copy link
Member

jezdez commented Aug 27, 2024

The checkbox is not working for me but I agree.

Thanks for letting me know

jezdez added a commit to conda/conda-package-handling that referenced this issue Sep 2, 2024
jezdez added a commit to conda/conda-package-streaming that referenced this issue Sep 2, 2024
@jezdez
Copy link
Member

jezdez commented Sep 2, 2024

Quick update:

I've done the above TODOs and added @travishathaway @kenodegard @marcelotrevisani @marcoesters to the conda-package-handling team, now renamed @conda/packaging-tools.

I've also removed from the conda-package-handling repo: @jcrist @mbargull @msarahan @conda/conda-core.

Opened conda/conda-package-handling#263 and conda/conda-package-streaming#103

dholth pushed a commit to conda/conda-package-handling that referenced this issue Sep 3, 2024
dholth pushed a commit to conda/conda-package-streaming that referenced this issue Sep 3, 2024
@jezdez
Copy link
Member

jezdez commented Sep 3, 2024

Closing as done.

@jezdez jezdez closed this as completed Sep 3, 2024
@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🧭 Planning Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::feature request for a new feature or capability
Projects
Archived in project
Development

No branches or pull requests

3 participants