Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start article about the history of conda-forge #2298

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jaimergp
Copy link
Member

@jaimergp jaimergp commented Sep 14, 2024

PR Checklist:

  • note any issues closed by this PR with closing keywords
  • if you are adding a new page under docs/ or community/, you have added it to the sidebar in the corresponding _sidebar.json file
  • put any other relevant information below

Still work in progress, but I wanted to capture the momentum started by Wolf and Filipe's podcast episode.

Tagging some folks for awareness, visibility, and hopefully a review, comments or even contributions if they are feeling generous 🙏 @ocefpaf @jakirkham @pelson @dholth @bryevdv @msarahan @asmeurer @ilanschnell. Feel free to tag others as well if you feel they can add more context into the early days!

🔍 Preview article link 🔍

Copy link

netlify bot commented Sep 14, 2024

Deploy Preview for conda-forge-previews ready!

Name Link
🔨 Latest commit 333e9fb
🔍 Latest deploy log https://app.netlify.com/sites/conda-forge-previews/deploys/66e59257497df20008d00ef8
😎 Deploy Preview https://deploy-preview-2298--conda-forge-previews.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@ocefpaf
Copy link
Member

ocefpaf commented Sep 16, 2024

Great article @jaimergp! It felt like it ended with cliffhanger and make me want for more. Are you planning on part 2/∞?

@jaimergp
Copy link
Member Author

Are you planning on part 2/∞?

Yes! This is just the beginning, and not ready for publication yet. Was hoping to gather some interest here and get comments from the "old guard" while I cover the very beginnings. Then I'll need a looot of help with the 2016-2021 period, and after that I think I can recollect a few things.

Even basic bullet items with a rough chronology would help so I can research git histories, archive.org, etc.

@beckermr
Copy link
Member

Here are some big events to track / mention. I don't have all of the details:

  • bot creation
  • great compiler migration
  • adding of special ecosystems (cuda, pypi, etc)
  • growth in terms of packages, downloads, etc.
  • rise of non-anaconda tooling (mamba, boa, rattler)
  • addition of major supporters (azure for ci, gpu ci, etc)

@isuruf
Copy link
Member

isuruf commented Sep 17, 2024

There were several bots

  • Linting bot - conda-forge-webservices
  • First bot that sent pinning updates - I don't remember where it was, but can figure it out.
  • Commenting bot (conda-forge-admin, rerender). Also conda-forge-webservices
  • regro bot that superseded the first bot that sent pinning updates. - regro/cf-scripts

Some other things to note

  • Packaging of compiler runtimes to become defaults independent
  • Cross compilation
  • Overwhelm of CI where CI took a couple of days.
  • azure and its donation


conda-forge's origins cannot be explained without understanding the context of Python packaging back in the early 2010s. Back then, the installation of Python packages across operating systems was very challenging, specially on Windows, as it often meant compiling dependencies from source.

Python 2.x was the norm, the community was transitioning from `easy_install` to `pip`, and there wouldn't be an alternative for Python eggs [^eggs] until 2012, when wheels are introduced [^wheels]. To get Python, you'd get the official installers from Python.org, stick to the system provided one in Linux, or resort to ActiveState's or Enthought's distributions in macOS and Windows [^legacy-python-downloads].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Python(x,y) was a popular Windows distribution back then, especially for science users. I recall it and Enthought's basically being the two main options for getting things working on Windows.

Suggested change
Python 2.x was the norm, the community was transitioning from `easy_install` to `pip`, and there wouldn't be an alternative for Python eggs [^eggs] until 2012, when wheels are introduced [^wheels]. To get Python, you'd get the official installers from Python.org, stick to the system provided one in Linux, or resort to ActiveState's or Enthought's distributions in macOS and Windows [^legacy-python-downloads].
Python 2.x was the norm, the community was transitioning from `easy_install` to `pip`, and there wouldn't be an alternative for Python eggs [^eggs] until 2012, when wheels are introduced [^wheels]. To get Python, you'd get the official installers from Python.org, stick to the system provided one in Linux, or resort to options like ActiveState's or Enthought's distributions in macOS and Windows [^legacy-python-downloads].

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added "options like" to not disregard Python(x,y) and others.

@moorepants
Copy link
Contributor

I remember being in a birds of a feather session at SciPy around 2013 or 2014 where the momentum to make conda forge real seemed to solidify and it was very soon after that conference that it took material form.

@asmeurer
Copy link
Member

The content is accurate as far as I can remember (which doesn't necessarily mean much). I would suggest doing a full checkup for grammar, and in particular, being consistent across the post with tense.

@ocefpaf
Copy link
Member

ocefpaf commented Sep 23, 2024

I remember being in a birds of a feather session at SciPy around 2013 or 2014 where the momentum to make conda forge real seemed to solidify and it was very soon after that conference that it took material form.

It was 2015 that the BoF happened and the soft launch on 2016 if I'm not mistaken.

@hmaarrfk
Copy link
Contributor

I would like it if there were a paragraph that mentions the deep collaborative period between Anaconda's default channel and conda-forge. Where we would often trade recipes collaboration was intricately linked.

I really look back fondly at the times where I was learning alot from msarahan, mingwandroid, jcrist, mrocklin (not sure if he worked for Anaconda at the time).

For me, the availability of Qt, Pillow, and OpenCV on windows/osx/linux were what brought me to Anaconda/conda/conda-forge.

@jaimergp jaimergp added the Docs label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

7 participants