From 637142852ad63d42427707b3e01de6397d263dc1 Mon Sep 17 00:00:00 2001 From: David Pattinson Date: Wed, 7 Aug 2024 14:12:55 -0400 Subject: [PATCH] Fixed broken link in pytensor_announcement.md --- blog/pytensor_announcement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/pytensor_announcement.md b/blog/pytensor_announcement.md index 60caf04..1e9dd26 100644 --- a/blog/pytensor_announcement.md +++ b/blog/pytensor_announcement.md @@ -12,7 +12,7 @@ The PyMC team would like to announce that we have forked the Aesara project. This new project is called [PyTensor](https://github.com/pymc-devs/pytensor). PyTensor will allow for new features such as labeled arrays, as well as speed up development and streamline the PyMC codebase and user experience. PyTensor is a community focused project and contributions are welcome. -Since the creation of Aesara, the PyMC and Aesara projects have been greatly intertwined. Aesara internals are critical to PyMC. In that time, however, the governance philosophies and technical goals of PyMC and Aesara diverged. PyMC is a [NumFOCUS sponsored project since 2016](https://numfocus.org/uncategorized/numfocus-announces-new-fiscally-sponsored-project-pymc3). PyMC follows a community model where consensus is formed when making key decisions and moving forward. Aesara is following a model where a select group of core developers drive most development and make key decisions while nurturing outside contributions to core infrastructure or design decisions is not a priority (see [Aesara's contributing guide](https://github.com/aesara-devs/aesara/blob/main/CONTRIBUTING.md) as well as [Rocket Ship to Mars archetype](https://opentechstrategies.com/archetypes-files/open-source-archetypes-v2.pdf#section*.10)). +Since the creation of Aesara, the PyMC and Aesara projects have been greatly intertwined. Aesara internals are critical to PyMC. In that time, however, the governance philosophies and technical goals of PyMC and Aesara diverged. PyMC is a [NumFOCUS sponsored project since 2016](https://numfocus.org/uncategorized/numfocus-announces-new-fiscally-sponsored-project-pymc3). PyMC follows a community model where consensus is formed when making key decisions and moving forward. Aesara is following a model where a select group of core developers drive most development and make key decisions while nurturing outside contributions to core infrastructure or design decisions is not a priority (see [Aesara's contributing guide](https://github.com/aesara-devs/aesara/blob/main/.github/CONTRIBUTING.md) as well as [Rocket Ship to Mars archetype](https://opentechstrategies.com/archetypes-files/open-source-archetypes-v2.pdf#section*.10)). While different development models can be successful for different open source software projects, the model followed by Aesara has proven to be incompatible with the collaborative process norms of the PyMC development team as well as our desire to influence key design decisions of Aesara. We believe the ability to contribute and influence the graph-engine is critical for our ability to innovate and make PyMC the best version it can be.