Joshua Adelman

Assuming you have a valid reason for removing a feedstock maintainer, I believe you would just open a PR that removed the user from the recipe and from `.github/CODEOWNERS`. The...

There are a number of issues currently: 1. It looks like `river` does not support cython>=3. Pinning it to `cython

I'm currently trying to get `0.21.2` built in the following PR: https://github.com/conda-forge/river-feedstock/pull/28

I'm not sure if there is a better way to solve this, but I just ended up explicitly modeling `A`, and then keeping a non-exporting field to hold the nested...

Looking through https://github.com/conda-forge/opencv-feedstock/issues/293, given it's age and the general conclusion that the maintainers didn't want to add this in that feedstock, is there an issue with moving ahead with a...

Just as a further datapoint, when I use a platform of `osx-64`, pixi solves in under 40 seconds on a pretty old laptop. However, when I set the platform to...

> I'm not going to your shortened URL and downloading something. Just in case @Ahajha's comment doesn't make sense, there was a spammy highly suspect reply from a user that...

`pixi project export` also supports explicit conda specs that don't require a solve and can be installed via micromamba, which is very lightweight. I also started a draft of exporting...

You can package `c3d` either in this PR or another. Using `grayskull`, the recipe would look like: ```yaml {% set name = "c3d" %} {% set version = "0.5.2" %}...