From 2b8a3fd51533aae2fdbc890345e7dbbf1f033dc3 Mon Sep 17 00:00:00 2001
From: Thomas Wiecki <thomas.wiecki@gmail.com>
Date: Sat, 26 Nov 2022 22:37:37 +0100
Subject: [PATCH 1/4] Add PyTensor announcement.

---
 blog/pytensor_announcement.md | 56 +++++++++++++++++++++++++++++++++++
 1 file changed, 56 insertions(+)
 create mode 100644 blog/pytensor_announcement.md

diff --git a/blog/pytensor_announcement.md b/blog/pytensor_announcement.md
new file mode 100644
index 0000000..d3406da
--- /dev/null
+++ b/blog/pytensor_announcement.md
@@ -0,0 +1,56 @@
+(pytensor_announcement)=
+# PyMC is Forking Aesara to PyTensor
+
+:::{post} Nov 28, 2022
+:tags: announcement
+:category: news
+:author: PyMC developers
+:image: 0
+:exclude:
+
+The PyMC team would like to announce that we are forking 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 are 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)).
+
+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. 
+
+Thus, after careful consideration and discussion, both among our developers and between the projects, we have decided that forking the Aesara project is the best choice for PyMC, its community and its developers.
+
+## What does this mean for PyMC?
+
+For now, we still depend on Aesara. As we are working towards a 5.0 release that will depend on PyTensor instead of Aesara there will be a new dependency installed, but the package manager will handle this seamlessly. In case you are using Aesara directly, you will have to adapt some imports but the code will remain the same as the libraries are currently almost identical code-wise. 
+
+The long-term impact will be positive. There are many exciting changes we plan to make that will directly improve the user and developer experience of PyMC.
+
+One example is [**Xarray**](https://xarray.dev/)-like dimension support: `Xarray` adds many useful features to arrays. Most notably, named dimensions and coordinates. This is what allows `coords` and `dims` in PyMC to give names to your dimensions.  Currently, Aesara does not support this, nor are there plans to do so. But there are many benefits to having labeled tensors as well.
+
+In addition, there are some optimizations that are mostly geared towards the computations PyMC is frequently running, so we expect great speed-ups from these additions.
+
+### Community
+
+The PyMC project is community-led, with a [governance structure](https://github.com/pymc-devs/pymc/blob/main/GOVERNANCE.md), code of conduct and other mechanisms in place to ensure a great experience for everyone involved. We strongly believe that a welcoming and inclusive environment is critical for the long-term survival of any open-source project.
+
+You can expect us to uphold these same standards to PyTensor to make it a project people are excited to contribute to.
+
+## Conclusion
+
+As always, we are grateful to the amazing community of users and contributors. We continue to be humbled by the impact this project has had over the years in science, business, and personal learning. We'd like to especially thank the Aesara development team for all their tireless efforts in building this library and working with us.
+
+We are very excited about the future of PyMC and its ecosystem. 
+
+## Connect with PyMC
+
+Connect with PyMC via:
+- Website:  [pymc.io](https://www.pymc.io)
+- Discourse: [discourse.pymc.io](https://discourse.pymc.io)
+- YouTube: [PyMCDevelopers](https://www.youtube.com/c/PyMCDevelopers)
+- Star GH repo:  [pymc-devs/pymc](https://github.com/pymc-devs/pymc)
+- Join Meetup: [pymc-online-meetup](https://www.meetup.com/pymc-online-meetup/)
+- Twitter: [@pymc_devs](https://twitter.com/pymc_devs)
+- LinkedIn: [@pymc](https://www.linkedin.com/company/pymc/)
+
+## Support PyMC
+
+- [Donate to the the PyMC project](https://numfocus.org/donate-to-pymc)

From 0cae7cef0a71920bde0001067fa77e591d228bb8 Mon Sep 17 00:00:00 2001
From: Thomas Wiecki <thomas.wiecki@gmail.com>
Date: Sun, 27 Nov 2022 18:16:04 +0100
Subject: [PATCH 2/4] Fix links. Fix header.

---
 blog/pytensor_announcement.md | 12 +++---------
 1 file changed, 3 insertions(+), 9 deletions(-)

diff --git a/blog/pytensor_announcement.md b/blog/pytensor_announcement.md
index d3406da..f04c2e1 100644
--- a/blog/pytensor_announcement.md
+++ b/blog/pytensor_announcement.md
@@ -8,7 +8,8 @@
 :image: 0
 :exclude:
 
-The PyMC team would like to announce that we are forking the Aesara project.:::
+The PyMC team would like to announce that we are forking 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.
 
@@ -43,14 +44,7 @@ We are very excited about the future of PyMC and its ecosystem.
 ## Connect with PyMC
 
 Connect with PyMC via:
-- Website:  [pymc.io](https://www.pymc.io)
-- Discourse: [discourse.pymc.io](https://discourse.pymc.io)
-- YouTube: [PyMCDevelopers](https://www.youtube.com/c/PyMCDevelopers)
-- Star GH repo:  [pymc-devs/pymc](https://github.com/pymc-devs/pymc)
+- PyTensor repo:  [pymc-devs/pymc](https://github.com/pymc-devs/pytensor)
 - Join Meetup: [pymc-online-meetup](https://www.meetup.com/pymc-online-meetup/)
 - Twitter: [@pymc_devs](https://twitter.com/pymc_devs)
 - LinkedIn: [@pymc](https://www.linkedin.com/company/pymc/)
-
-## Support PyMC
-
-- [Donate to the the PyMC project](https://numfocus.org/donate-to-pymc)

From e53fdc1d1a77ca74638dfad5d30d350e9c4b759b Mon Sep 17 00:00:00 2001
From: Thomas Wiecki <thomas.wiecki@gmail.com>
Date: Sun, 27 Nov 2022 18:16:31 +0100
Subject: [PATCH 3/4] Remove exclude.

---
 blog/pytensor_announcement.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/blog/pytensor_announcement.md b/blog/pytensor_announcement.md
index f04c2e1..c6cedbd 100644
--- a/blog/pytensor_announcement.md
+++ b/blog/pytensor_announcement.md
@@ -6,7 +6,6 @@
 :category: news
 :author: PyMC developers
 :image: 0
-:exclude:
 
 The PyMC team would like to announce that we are forking the Aesara project.
 :::

From 3f8cec8e6155d9eff1b794d62aab74a564b25d26 Mon Sep 17 00:00:00 2001
From: Thomas Wiecki <thomas.wiecki@gmail.com>
Date: Sun, 27 Nov 2022 23:14:20 +0100
Subject: [PATCH 4/4] Add edits from @cluhmann.

---
 blog/pytensor_announcement.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/blog/pytensor_announcement.md b/blog/pytensor_announcement.md
index c6cedbd..18fcb49 100644
--- a/blog/pytensor_announcement.md
+++ b/blog/pytensor_announcement.md
@@ -16,23 +16,23 @@ Since the creation of Aesara, the PyMC and Aesara projects have been greatly int
 
 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. 
 
-Thus, after careful consideration and discussion, both among our developers and between the projects, we have decided that forking the Aesara project is the best choice for PyMC, its community and its developers.
+Thus, after careful consideration and discussion, both among our developers and between the projects, we have decided that forking the Aesara project is the best choice for PyMC, its community, and its developers.
 
 ## What does this mean for PyMC?
 
-For now, we still depend on Aesara. As we are working towards a 5.0 release that will depend on PyTensor instead of Aesara there will be a new dependency installed, but the package manager will handle this seamlessly. In case you are using Aesara directly, you will have to adapt some imports but the code will remain the same as the libraries are currently almost identical code-wise. 
+For now, we still depend on Aesara. As we are working towards a 5.0 release of PyMC that will depend on PyTensor instead of Aesara there will be a new dependency installed, but the package manager will handle this seamlessly. If you are using Aesara directly, you will have to adapt some imports, but the code will remain the same as the libraries are currently almost identical code-wise. 
 
 The long-term impact will be positive. There are many exciting changes we plan to make that will directly improve the user and developer experience of PyMC.
 
-One example is [**Xarray**](https://xarray.dev/)-like dimension support: `Xarray` adds many useful features to arrays. Most notably, named dimensions and coordinates. This is what allows `coords` and `dims` in PyMC to give names to your dimensions.  Currently, Aesara does not support this, nor are there plans to do so. But there are many benefits to having labeled tensors as well.
+One example is [**Xarray**](https://xarray.dev/)-like dimension support: `Xarray` adds many useful features to arrays. Most notably, named dimensions and coordinates. This is what allows `coords` and `dims` in PyMC to give names to your arrays.  Currently, Aesara does not support this, nor are there plans to do so. But there are many benefits to having labeled tensors as well.
 
-In addition, there are some optimizations that are mostly geared towards the computations PyMC is frequently running, so we expect great speed-ups from these additions.
+In addition, there are optimizations that are mostly geared towards the computations PyMC frequently perform, so we expect great speed-ups from these additions.
 
 ### Community
 
 The PyMC project is community-led, with a [governance structure](https://github.com/pymc-devs/pymc/blob/main/GOVERNANCE.md), code of conduct and other mechanisms in place to ensure a great experience for everyone involved. We strongly believe that a welcoming and inclusive environment is critical for the long-term survival of any open-source project.
 
-You can expect us to uphold these same standards to PyTensor to make it a project people are excited to contribute to.
+You can expect us to apply these same standards to PyTensor to make it a project people are excited to contribute to.
 
 ## Conclusion
 
