Conversation
|
whats the mandate of this team? deploying miniforge for architectures that conda-forge supports but miniconda doesn't? i.e. aarch64? |
According to the text this is for any arch |
Agree. The team (which includes core) can decide what platforms to support. |
@isuruf do you mean that this subteam includes all of core? |
That's what I intended. Let me know if you disagree. |
|
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?
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. |
|
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. |
CJ-Wright
left a comment
There was a problem hiding this comment.
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.
mbargull
left a comment
There was a problem hiding this comment.
SGTM!
And I'll probably add myself to this team in the future (as time allows)!
|
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 |
|
Thanks for putting this in, for the votes and thanks to the miniforge team for their future work! |
|
Can someone please provision the team on github? |
|
Woohoo! |
@conda-forge/core, this needs 50% to pass