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 am curious: Why do you ship spectral_connectivity on a personal conda channel, instead of on conda-forge?
Shipping on conda-forge would have the advantage of re-using the huge community structure, and making your release process for conda more transparent, as well as users not having to declare your personal channel as a source in the environments.
I am happy to consider this move since it would make it easier to install. The reason for not doing it so far was mostly inertia. The package started on my own personal channel and it was easier to release things that way initially.
I am curious: Why do you ship
spectral_connectivity
on a personal conda channel, instead of on conda-forge?Shipping on conda-forge would have the advantage of re-using the huge community structure, and making your release process for conda more transparent, as well as users not having to declare your personal channel as a source in the environments.
xref: openjournals/joss-reviews#4840
The text was updated successfully, but these errors were encountered: