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.

Sign up for GitHub

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

Jump to bottom

Fixed broken link in pytensor_announcement.md #99

Merged
merged 1 commit into from
Aug 7, 2024
Merged

Fixed broken link in pytensor_announcement.md #99

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion blog/pytensor_announcement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading