Back port relevant blog posts from anaconda.com

[travishathaway]

Description

We currently have a lot of interesting and well written blog posts on Anaconda.com blog. We want to see which ones would be good candidates to port over.

These blog posts should:

• Be relevant to conda, conda-build or other related tools
• Have proper permissions to be transferred over (we should reach out to the authors to get approval)

Tasks

• Create a list of possible blog articles to port over and list them here in a comment.
• Get permission to port these over from the authors.
• Create new pull requests to add these blog articles (one pull request per article).

[vasvi-sood]

@travishathaway I would like to work on this issue

[travishathaway]

Hi @vasvi-sood,

Thanks for volunteering to work on this 😄. The first step is to go through the blog posts relevant on https://anaconda.com/blog . I think it's reasonable to grab everything with the words "conda" in it, but I will let you use your best judgement. I also wouldn't include anything older than three years.

[vasvi-sood]

Ok @travishathaway , I'll start preparing a list now

[vasvi-sood]

These are the blog posts I think could be migrated here. Please review them and let me know what you think.

1. New! CVE Association for Conda-Forge Packages Helps Secure Your Software Supply Chain
2. New Release: Anaconda Distribution 2023.03
3. Four Open-Source Projects and the Anaconda Maintainers Who Love Them
4. Code in the Cloud With Anaconda—for Free!
5. New Year, New You: What Will You Learn Next?
6. 2022: An Anaconda Year in Review
7. Introducing a New Plugin Mechanism for conda
8. Conda Is Fast Now. Like, Really Fast
9. Anaconda and Oracle Bring Secure Open-Source Software to OCI
10. Introducing Data Science Training and Cloud-Hosted Notebooks From Anaconda
11. A Faster Solver for Conda: Libmamba
12. Keeping your Conda Environments Safe and Secure with your Anaconda Nucleus Account

[tnabtaf]

Hi @vasvi-sood,

Thanks for creating this list. I have some suggestions about not reproducing some of them on the conda.org site. This is mainly related to maintaining the distinction between Conda and Anaconda, a message that we constantly struggle with.

Here are my suggestions:

Port to conda.org:

• Introducing a New Plugin Mechanism for conda
• Conda Is Fast Now. Like, Really Fast
• A Faster Solver for Conda: Libmamba

Do not (or so I say!) port to conda.org

• Code in the Cloud With Anaconda—for Free!
• 2022: An Anaconda Year in Review
• Introducing Data Science Training and Cloud-Hosted Notebooks From Anaconda

These don't have enough about conda. I don't believe they belong on conda.org.

After that it gets even more complicated

• New! CVE Association for Conda-Forge Packages Helps Secure Your Software Supply Chain

  • This service is available to Anaconda's paying customers. We don't yet have a policy on how to handle paid features from companies. This feature is useful, but the policy lags behind. Also if we did port it, I would suggest just a short post on conda.org that points to the full post at Anaconda.
  • Recommendation: don't post anything now. Anyone else have opinions?

• Anaconda and Oracle Bring Secure Open-Source Software to OCI

  • Same as previous one. We need clearer policies about paid features.

• New Release: Anaconda Distribution 2023.03

  • I don't have a clear opinion on this one. Anyone?

• Four Open-Source Projects and the Anaconda Maintainers Who Love Them

  • This is fundamentally an Anaconda blog post. I can imagine a short post on conda.org that talks about Jannis's comments and then points to the full blog post.
  • Recommendation: Someone (Vasvi you clearly have not volunteered for this) write a short post that highlights Jannis's part and then points to the full post on Anaconda.

• New Year, New You: What Will You Learn Next?

  • This links to several course at Anaconda. The top two are directly relevant to conda, and they are free to access. However, I don't think the whole post is relevant.
  • Recommendation: Someone write a short post linking to the two relevant courses. We could ask Jess H to do this.

• Keeping your Conda Environments Safe and Secure with your Anaconda Nucleus Account

  • This is a free and valuable service. But I think we just want to summarize it and then link to the full post on Anaconda.
  • Recommendation: Someone write a short post summarizing the original post, and then link to it.

Hope this helps, and I apologize for the long response.

[kenodegard]

I concur with @tnabtaf's thoughts, anything we back port must be entirely conda and should likely avoid any mention of Anaconda.

Personally I would include stuff even older than 3 years. The prior maintenance team left lots of great posts many of which cover info, knowledge, and other tidbits that are poorly documented elsewhere, e.g.:

• https://www.anaconda.com/blog/what-conda-canary
• https://www.anaconda.com/blog/preview-new-features-conda-canary
• https://www.anaconda.com/blog/condas-new-noarch-packages
• https://www.anaconda.com/blog/conda-4-6-release
• https://www.anaconda.com/blog/how-we-made-conda-faster-4-7
• https://www.anaconda.com/blog/using-pip-in-a-conda-environment
• https://www.anaconda.com/blog/moving-conda-environments

[vasvi-sood]

@tnabtaf Thank you for your insightful review. I understand from your comment above that not all the posts that I mentioned, fully capture the essence of conda and its functionality. For the posts that you mentioned that should be ported, I would like to personally reach out to the authors, seeking their permission to port their content to conda.org. Additionally, I would like to write a concise post focusing on Jannis's comment about conda, as featured in the article Four Open-Source Projects and the Anaconda Maintainers Who Love Them.

[tnabtaf]

That sounds great @vasvi-sood. Thanks again for doing this.

[vasvi-sood]

@beeankha can I port the article Introducing a New Plugin Mechanism for conda over to conda.org?