You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to start using schemas.conda.org as the canonical location for our specifications. This is prompted by this comment.
We can probably start deploying conda/schemas to schemas.conda.org. These are currently available in conda.github.io/schemas, which forwards to schemas.conda.io. However, I don't know how this is set up. My first thought was that, since this is a ecosystem wide repository, the @conda/steering-council team should have admin access to conda/schemas. But maybe there's a technical reason not to?
Anyhow, my questions:
Can we transition from schemas.conda.io to schemas.conda.org?
Can we the Steering Council obtain admin access to conda/schemas?
Thanks, @conda/infrastructure!
The text was updated successfully, but these errors were encountered:
I'd like to start using schemas.conda.org as the canonical location for our specifications. This is prompted by this comment.
We can probably start deploying
conda/schemas
toschemas.conda.org
. These are currently available in conda.github.io/schemas, which forwards toschemas.conda.io
. However, I don't know how this is set up. My first thought was that, since this is a ecosystem wide repository, the @conda/steering-council team should have admin access toconda/schemas
. But maybe there's a technical reason not to?Anyhow, my questions:
conda/schemas
?Thanks, @conda/infrastructure!
The text was updated successfully, but these errors were encountered: