conda-forge.github.io icon indicating copy to clipboard operation
conda-forge.github.io copied to clipboard

Remove Mambaforge download links

Open ethanc8 opened this issue 1 year ago • 11 comments

On the download site, the first download links the user sees are Mambaforge download links. However, Mambaforge is deprecated, so the Mambaforge download links should be removed or made less visible. Additionally, since conda-forge's pypy support is deprecated, the Miniforge-pypy3 download links should also be made less visible. If we keep those download links on the page, we should add a note that they are deprecated. Perhaps they could be hidden under a collapsible element like the download links for older versions are.

ethanc8 avatar Oct 17 '24 15:10 ethanc8

It might be better just to put a copy of the README onto the website.

ethanc8 avatar Oct 17 '24 15:10 ethanc8

hmm a PR to deprioritize them would be good.

I don't even know how you go there.

I can only get to https://conda-forge.org/download/

Nor do i know where the source is.

hmaarrfk avatar Oct 18 '24 13:10 hmaarrfk

I believe the source should be in the gh-pages branch of this repo. The releases webpage is the second search result on Google, Bing, DuckDuckGo, Ecosia, and Brave search engines.

ethanc8 avatar Oct 18 '24 13:10 ethanc8

Yeah.... ok as a first step. i tried to point people to the right direction.

Image

hmaarrfk avatar Oct 18 '24 13:10 hmaarrfk

I meant that the download page hosted at https://conda-forge.org/miniforge/ is the second search result.

ethanc8 avatar Oct 18 '24 13:10 ethanc8

i understand, but i'm just letting you know:

  1. I acknowledge the pain point.
  2. I personally am unsure how to fix this.
  3. I added a step in the right direction.

hmaarrfk avatar Oct 18 '24 13:10 hmaarrfk

I believe this file contains the source for the download page: https://github.com/conda-forge/miniforge/blob/gh-pages/index.html. However, it seems to be generated by a GH Actions workflow.

ethanc8 avatar Oct 18 '24 13:10 ethanc8

I believe it is the "Build docs" action that causes this. This workflow uses the release.py script, so modifying that script and re-running the action should fix this.

ethanc8 avatar Oct 18 '24 14:10 ethanc8

At minimum, we can modify the all-releases.html page to have a link to the README and a note that PyPy3 and Mambaforge installers are deprecated.

ethanc8 avatar Oct 18 '24 14:10 ethanc8

That sounds like a good improvement!

A PR would be appreciate.

We could also pull in maybe the release description?

hmaarrfk avatar Oct 18 '24 14:10 hmaarrfk

I might work on this later, then. I've got quite a lot to do now.

ethanc8 avatar Oct 18 '24 14:10 ethanc8