Core team
The core team’s next focus will be releasing version 1.3.0 with some pending updates and fixes. Release plan and timeline to come soon in a separate thread.
Special thanks to @MattyRob and @1stepforward for helping move our automated code tests from Travis CI to GitHub Actions. These checks help us catch and prevent some kinds of issues that may occur when we make changes to ClassicPress core, and we had to find a new provider since Travis CI no longer offers this service to open-source projects. So far, running these checks directly on GitHub is faster and better-integrated with the rest of our contribution workflow.
Infrastructure team
Still keeping our sites running and looking at potential improvements in that area.
We helped out a bit with the migration of petitions to the forums by putting the old content of petitions.classicpress.net back up as a read-only archive. This allows everyone to see past petitions in the format they were originally posted and discussed, and keeps links to those pages working reasonably instead of returning a 404.
We are also working on adding an API endpoint to serve checksums of the ClassicPress core files. This API endpoint is being deployed on our infrastructure and will be used to fix a bug in ClassicPress core.
The next priority for infrastructure-related work will be doing some cleanup and re-organization of some auxiliary sites, for example related to Classic Commerce and documentation.
If you’re available to help with any of these items then send me a message here on the forums or in Slack.