Skip to content

unify pytorch policies#121

Open
h-vetinari wants to merge 1 commit into
conda-forge:mainfrom
h-vetinari:pytorch
Open

unify pytorch policies#121
h-vetinari wants to merge 1 commit into
conda-forge:mainfrom
h-vetinari:pytorch

Conversation

@h-vetinari
Copy link
Copy Markdown
Member

@h-vetinari h-vetinari commented Nov 7, 2025

Alternative to #119; I don't think it makes sense to have different policies per resource; any single commit pushed (by someone with the respective rights, i.e. a feedstock maintainer) must be able to trigger runs on all relevant resources.

It is more important IMO that this works cohesively than reusing the "global" access list from https://github.com/Quansight/open-gpu-server/main/access/conda-forge-users.json, or than blindly applying the process from https://github.com/conda-forge/admin-requests/blob/main/examples/example-open-gpu-server.yml for adding resources (which currently is simply unsuited for dealing with multiple resources per feedstock).

Closes #119

CC @jaimergp @mgorny

Copy link
Copy Markdown
Contributor

@mgorny mgorny left a comment

Choose a reason for hiding this comment

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

WFM

@jaimergp
Copy link
Copy Markdown
Member

jaimergp commented Nov 7, 2025

I don't agree, some resources require special terms (like the TOS approval in open-gpu-server). That was the point of having different policies to begin with.

@mgorny
Copy link
Copy Markdown
Contributor

mgorny commented Nov 7, 2025

@jaimergp, should we go with #119 instead? Or do you have another preference?

@h-vetinari h-vetinari changed the title unify pytorch policies; add cirun-macos-m4-large unify pytorch policies Dec 11, 2025
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.

3 participants