# Anaconda license situation at your site?

**URL:** <https://ask.cyberinfrastructure.org/t/anaconda-license-situation-at-your-site/4005>\
**Category:** Discussion Zone\
**Tags:** systems, programming-for-hpc, python, anaconda, conda\
**Created:** [August 14, 2024, 2:00pm UTC](https://ask.cyberinfrastructure.org/t/anaconda-license-situation-at-your-site/4005 "2024-08-14T14:00:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![wwarr](https://ask.cyberinfrastructure.org/letter_avatar_proxy/v4/letter/w/3be4f8/32.png) [@wwarr](https://ask.cyberinfrastructure.org/u/wwarr)\
**Post date:** [August 15, 2024, 8:26pm UTC](https://ask.cyberinfrastructure.org/t/anaconda-license-situation-at-your-site/4005/4 "2024-08-15T20:26:11Z")

</div>

At UAB, we’re making a transition to Miniforge and are planning to document the how and why of the transition. We use Lmod, which helps us out a bit, because at some point we’ll set up our Anaconda module(s) to simply emit a warning and load Miniforge instead.

Obviously, we can’t stop researchers from using the `anaconda` or `r` channels, but we can educate them about the how and why for the transition, and what they’ll need to do to avoid TOS violations.

As far as “forcing” users to avoid the restricted channels, that is a leadership decision and way outside our hands. But if legal action causes us to move in that direction, we’ll be ready with an alternative and training already in place.

---

_[View the full topic](https://ask.cyberinfrastructure.org/t/anaconda-license-situation-at-your-site/4005)._
