Outline Why do we want to update conda's configuration?It doesn't handle errors well when things are misconfigured (usually blows up with a big unhelpful stacktrace) It's a custom built solution that's difficult to customize Parameter definition is clunky, relying on class definitions instead of type hints How do we do this? Switching to Pydantic would help simplify the context object We re-write conda.common.configuration to be a lot simpler, focusing primarily on the merging and precedence of configuration variables sources and not on

Summary In order to give better insight to the operations of conda open-source projects, we want to develop a statistics dashboard. This dashboard will be organized along the following four categories: volume, responsiveness, engagement and lifecycle. The data for the dashboard will be drawn from GitHub, namely the issues and pull requests for individual projects. On top of this, we will also use this data to construct a narrative to be published as a blog post around the management of conda as an open-source project and the turn around it has seen in the last three years. Creating a dashboard

The following document is an explanation of how output rendering in conda works. The document contains a detailed explaination of the software design and certain justifications behind these design decisions. The intended audience for this document is someone who wants a thorough understanding of how this system works and is not intended to be a tutorial or how-to article. Please see those for a quicker overview of output rendering and how to begin using it. High level overview Output rendering in conda is a comprised of two different abstractions: reporter and output handlers. Reporter handlers define how the output will

This project will require the following steps: A refactor to replace all the usages of print and sys.stdout.write with a higher level abstraction that will be able to either route to the built in print function or to rich. A settings mechanism that will allow us to turn rich on or off (this will default to off) Implement our first rich enabled layout with the conda info command This refactor will give us a good opportunity to make sure that we are

About the data in Jira We have tickets in the following project: PKG These are created via Slack in #package_requests These issues go through different statuses (e.g. 'in review', 'merged', 'done', etc.) These issues have the following metadata associated with them:urgency type ("New Package", "Package Update", "Other", "Bug Report") package name package version destination (e.g. defaults)

Some third party crates to checkout: rayon thiserror anyhow tokio blessed.rs (website full of stuff 🙌) https://insta.rs/docs/quickstart/ https://docs.rs/id3/latest/id3/ (for reading mp3 file metadata)

For the upcoming knowledge sharing meeting with Jesus and his team, he brought the following questions that should be answered and discussed. How to achieve a good internal consistent structure of commands Choose a CLI argument parsing framework that everyone can agree on. I personally like click but there are several others out there too. Others to consider: