diff --git a/updates/2023-06-steering-council-update.md b/updates/2023-06-steering-council-update.md
new file mode 100644
index 0000000..7fcf325
--- /dev/null
+++ b/updates/2023-06-steering-council-update.md
@@ -0,0 +1,34 @@
+## 2023-06-05
+
+- Three Steering Council members were available to meet today, Emily and Pablo were traveling.
+- The SC met with Łukasz, the Developer-in-Residence, and discussed:
+  - The new Deputy Developer-in-Residence job description draft.
+  - EuroPython coming up and Łukasz helping coordinate a core sprint there.
+- Discussed all our [PEP 703 (Making the Global Interpreter Lock Optional in CPython)](https://peps.python.org/pep-0703/) thoughts.
+- Discussed OpenSSL 3.x support backporting needs for older releases.
+- Discussed 3.12 and 3.13 release schedule planning with Thomas (release manager hat).
+- Discussed ongoing 3.12beta1 early findings as projects try it out.
+- Briefly discussed support for core developer mentorship with Deb.
+
+## 2023-06-12
+
+- The Steering Council discussed [PEP 703 (Making the Global Interpreter Lock Optional in CPython)](https://peps.python.org/pep-0703/) extensively, with a focus on establishing a process and criteria for evaluating and deciding on the PEP.
+
+## 2023-06-19
+
+- The Steering Council discussed [PEP 703 (Making the Global Interpreter Lock Optional in CPython)](https://peps.python.org/pep-0703/) and decided to find out if there’s consensus among Core Devs for the idea and the specific PEP, through [a poll on discuss.python.org](https://discuss.python.org/t/poll-feedback-to-the-sc-on-making-cpython-free-threaded-and-pep-703/28540).
+- The SC decided to schedule [office hours](https://discuss.python.org/t/steering-council-office-hours/28881) a half hour before the weekly meeting, as an experiment.
+- The SC approved [Petr’s proposed changes](https://github.com/python/steering-council/issues/196) to [PEP 387 (Backwards Compatibility Policy)](https://peps.python.org/pep-0387/).
+
+## 2023-06-26
+
+- The Steering Council met with Seth Larson, the new Security Developer-in-Residence. One of Seth’s tasks is to improve the process behind the Python Security Response Team (PSRT), and to investigate the PSRT or PSF becoming a MITRE Sub-CNA, so it has authority over the reporting and ranking of CVEs. Seth will be working mostly with the PSRT team, only planning to have email discussions or ad-hoc meetings with the SC for now.
+- The SC met with Łukasz, the Developer-in-Residence, and discussed:
+  - Łukasz handling the macOS installer build as well as the Windows build for 3.12 beta 4.
+  - His keynote at [PyCon Colombia](https://2023.pycon.co/).
+  - A new EdgeDB release that should alleviate CLA bot inefficiencies.
+  - EuroPython, his planned talk, the Core Dev panel, and the sprints there.
+  - The Deputy Developer-in-Residence job opening, which will be posted this week.
+- The SC discussed [json.AttrDict](https://github.com/python/cpython/issues/96145), which was added without review or discussion, with previous proposals having been rejected, and agreed with the [rollback](https://github.com/python/cpython/pull/105948) of it for now, at least until it can be discussed on discuss.python.org and a consensus is reached.
+- The SC briefly discussed other open issues involving Python 3.12, leaving them to the Release Team to handle.
+- The SC officially invited Russel Keith-Magee to the Core Dev Sprint in Brno in October.
diff --git a/updates/2023-07-steering-council-update.md b/updates/2023-07-steering-council-update.md
new file mode 100644
index 0000000..abedf94
--- /dev/null
+++ b/updates/2023-07-steering-council-update.md
@@ -0,0 +1,45 @@
+## 2023-07-03
+
+- The Steering Council checked in on ongoing conduct issues and the steps to handle them.
+- The SC discussed an email that suggested an update to [PEP 12 (Sample reStructuredText PEP Template)](https://peps.python.org/pep-0012/) to formalize including acceptance and rejection rationale to PEPs once they have a decision. The SC thinks this is a good idea and will work on drafting this change.
+- The SC discussed dropping the python-committers mailing list. An email will be sent to gauge interest and usage of the mailing list.
+
+## 2023-07-10
+
+- The Steering Council met with Łukasz, the Developer-in-Residence, and discussed:
+  - The Deputy Developer-in-Residence job, which has been posted and started receiving applications.
+  - The 3.12 final beta release, which has a few important bug fix PRs that are open.
+  - EuroPython, which is happening next week. Łukasz will be giving a talk and running a panel along with sprints
+- The SC continued to discuss support for core developer mentorship with Deb. The distinction between supporting mentorship for new core developers and improving the process of becoming a core developer was raised – we are specifically looking for how to support existing core developers in mentoring contributors. The SC decided to pause the discussion to solidify what we are looking for in this arrangement.
+- The SC discussed [PEP 703 (Making the Global Interpreter Lock Optional in CPython)](https://peps.python.org/pep-0703/).
+  - The [poll results are in](https://www.notion.so/Weekly-Meeting-Notes-1715f30c2d3d4b8699adb5778e83d695?pvs=21) and indicate that 87% of respondents think we should be actively looking to make Python free-threaded and 63% want to accept and support the maintenance cost of PEP 703.
+  - Proceeding with caution, the SC decided to formalize a statement on our intention to accept the PEP, along with requirements and expectations for doing so.
+- The SC discussed two C API changes in 3.12 that did not follow PEP-387 to decide how they should be handled, namely:
+  - Type Object’s tp_dict can now be NULL. This has limited impact and is likely acceptable.
+  - PyLongObject implementation and ob_digits. The SC decided to roll back changes only in 3.12, not main (3.13) for now. Overall, this change is okay.
+- The SC checked in on requiring PR reviews; a [poll has been opened](https://discuss.python.org/t/sc-poll-should-we-require-reviews-to-merge-all-prs/29410).
+
+## 2023-07-17
+
+- The Steering Council checked in on ongoing conduct issues and the steps to handle them.
+- The SC received feedback from the community on the lack of use for the python-committers email list and decided to close it.
+- The SC continued to discuss [PEP 703 (Making the Global Interpreter Lock Optional in CPython)](https://peps.python.org/pep-0703/), with a focus on establishing a hard list of requirements for acceptance to be included in a forthcoming pre-announcement.
+
+## 2023-07-24
+
+- The Steering Council met with Łukasz, the Developer-in-Residence, and discussed:
+  - How Europython went (both the conference and the sprints).
+  - dtrace and how to test the probes so they keep functioning.
+  - Miss Islington needs porting to GitHub Actions before we can switch over to requiring 2FA.
+  - The SC asked the DiR to evaluate how we could require code reviews for feature PRs.
+- The SC discussed support for core developer mentorship, namely the budget around a proposal to do an inventory of the current mentorship program.
+- The SC gave our approval to the Security Developer-in-Residence for their CNA proposal.
+- The SC. discussed updating non-borrowing C APIs to match borrowing ones.
+- The SC continued to discuss [PEP 703 (Making the Global Interpreter Lock Optional in CPython)](https://peps.python.org/pep-0703/).
+
+## 2023-07-31
+
+- The Steering Council confirmed that the python-committers email list has been closed.
+- The SC discussed the state of [PEP 713 (Callable Modules)](https://peps.python.org/pep-0713/) and [PEP 702 (Marking deprecations using the type system)](https://peps.python.org/pep-0702/).
+- The SC continued to discuss the hard requirements around [PEP 703 (Making the Global Interpreter Lock Optional in CPython)](https://peps.python.org/pep-0703/), now that [the pre-acceptance has been pre-announced](https://discuss.python.org/t/a-steering-council-notice-about-pep-703-making-the-global-interpreter-lock-optional-in-cpython/30474).
+- The SC discussed how to handle the interview process for the Deputy Developer-in-Residence position.