abandoned feedstocks?

[hmaarrfk]

Your question:

I have a concern that certain feedstocks have not been able to keepup with certain migrations for quite some time.

It feels like we should be able to tag certain repos, maybe simply "archiving them" could help the bots complete migrations so that the global pinning can be updated.

Not to point fingers (I know priorities change) but feedstocks that come to mind are:

• [ ] https://github.com/conda-forge/trilinos-feedstock/pulls
• [ ] https://github.com/conda-forge/pytrilinos-feedstock/pulls
• [x] https://github.com/conda-forge/shogun-cpp-feedstock/pulls
• [x] https://github.com/conda-forge/caffe-feedstock/pulls <-- This one should probably be archived.
• [x] https://github.com/conda-forge/libcugraph-feedstock
• [ ] ~~https://github.com/conda-forge/colored-feedstock~~
• [ ] https://github.com/conda-forge/dioptas-feedstock
• [ ] https://github.com/conda-forge/lxqt-build-tools-feedstock
• [ ] https://github.com/conda-forge/kaolin-feedstock
• [ ] https://github.com/conda-forge/pyne-feedstock/pulls
• [ ] https://github.com/conda-forge/cyclus-feedstock/pulls

Generally, making it clear that they are no-longer maintained may encourage others to maintain the recipes.

Edit: changed a word from "feedstock" to migrations"

[leofang]

I'd also like to tag https://github.com/conda-forge/libcugraph-feedstock.

[HeavyTony2]

I'd tag this one. https://github.com/conda-forge/colored-feedstock The maintaner hasn't even been active on github for 15 months.

[h-vetinari]

https://github.com/conda-forge/dioptas-feedstock & https://github.com/conda-forge/lxqt-build-tools-feedstock have many open version & migration PRs. Last human intervention for both was ~3 years ago.

[h-vetinari]

Looked a bit closer at https://github.com/conda-forge/kaolin-feedstock today, and it looks like the group-account @mxr-conda plus all its members have been almost completely absent from conda-forge for about a year. There's a couple of feedstocks that are maintained (only) by some combination of those accounts, so there's probably several that are affected.

CC @rluria14 @oblute @ndmaxar @JennaLipscomb @d-cunningham, could you let us know about the state of @mxr-conda, even if it's just to say "it's dead Jim"...?

[hmaarrfk]

@HeavyTony2

I'd tag this one. https://github.com/conda-forge/colored-feedstock The maintaner hasn't even been active on github for 15 months.

It seems that there is one user that would like that one. Can you help maintain it?

[jakirkham]

This appears to have no maintainers

https://github.com/conda-forge/pyobjc-framework-metal-feedstock

[hmaarrfk]

@beckermr can you comment as to why you are opposed to archiving these abandonned feedstocks?

Would it be acceptable if we documented the process of unarchiving https://github.com/conda-forge/admin-requests/pull/657#issuecomment-1383220347

[beckermr]

We can simply close migrations sooner. For example, we could make the bot issue a pr to close a migration when there are say five or less packages not migrated (with a carve out for small migrations).

We could also adjust the bot to skip certain feedstocks that have many outstanding prs. We do this for versions.

Archiving feedstocks should be reserved for packages we truly never intend to ship again. These don't meet that threshold IMHO.

[hmaarrfk]

Understood.

[h-vetinari]

https://github.com/conda-forge/multineat-feedstock is dead, together with its upstream