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

Add miniforge sub team #922

Merged
merged 4 commits into from
Nov 19, 2019
Merged

Add miniforge sub team #922

merged 4 commits into from
Nov 19, 2019

Conversation

isuruf
Copy link
Member

@isuruf isuruf commented Nov 14, 2019

@conda-forge/core, this needs 50% to pass

@hmaarrfk
Copy link
Contributor

whats the mandate of this team? deploying miniforge for architectures that conda-forge supports but miniconda doesn't? i.e. aarch64?

src/orga/subteams.rst Outdated Show resolved Hide resolved
@scopatz
Copy link
Member

scopatz commented Nov 14, 2019

deploying miniforge for architectures that conda-forge supports but miniconda doesn't? i.e. aarch64?

According to the text this is for any arch

@isuruf
Copy link
Member Author

isuruf commented Nov 14, 2019

According to the text this is for any arch

Agree. The team (which includes core) can decide what platforms to support.

src/orga/subteams.rst Outdated Show resolved Hide resolved
@CJ-Wright
Copy link
Member

The team (which includes core)

@isuruf do you mean that this subteam includes all of core?

@isuruf
Copy link
Member Author

isuruf commented Nov 14, 2019

@isuruf do you mean that this subteam includes all of core?

That's what I intended. Let me know if you disagree.

@CJ-Wright
Copy link
Member

I think it would be better if compartmentalized. That way the team is more lean and the voting body is not too large. Would language similar to the auto-tick bot's team work?

For large scale (affecting >20% of packages) this sub-team will inform and discuss with the core team about the upcoming migration prior to starting the migration.

A clause like that would enable the team to make its own decisions on day to day operations and then bring things to core for discussion if warranted.

You could also say that members of core and emeritus have rights as ex officio members where it is custom to abstain.

@hadim
Copy link
Member

hadim commented Nov 17, 2019

The miniforge builder is in a good state now: conda-forge/miniforge#2

Feel free to review/comment.

The release process still needs to be tested.

Copy link
Member

@CJ-Wright CJ-Wright left a comment

Choose a reason for hiding this comment

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

I can put up a PR with the ex officio language if anyone is interested. I think that could be a good general policy, but this PR should not wait for it.

Copy link
Member

@mbargull mbargull left a comment

Choose a reason for hiding this comment

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

SGTM!
And I'll probably add myself to this team in the future (as time allows)!

@hadim
Copy link
Member

hadim commented Nov 18, 2019

I just wanted to let you know that the miniforge PR is done now. All the blocking deps have been released: conda-forge/miniforge#2

@mbargull mbargull merged commit 2cae20a into conda-forge:master Nov 19, 2019
@isuruf isuruf deleted the miniforge branch November 19, 2019 17:54
@mbargull
Copy link
Member

Thanks for putting this in, for the votes and thanks to the miniforge team for their future work!

@CJ-Wright
Copy link
Member

Can someone please provision the team on github?

@isuruf
Copy link
Member Author

isuruf commented Nov 19, 2019

Done. https://github.com/orgs/conda-forge/teams/miniforge

@scopatz
Copy link
Member

scopatz commented Nov 19, 2019

Woohoo!

Copy link

@Atom14011985 Atom14011985 left a comment

Choose a reason for hiding this comment

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

src/orga/subteams.rst

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

Successfully merging this pull request may close these issues.

None yet