WordPress council
Recent developments around #44 (closed) #45 (closed) #46 (closed) #47 show that the maintenance of the WordPress environments has fallen behind, especially due to #40 (closed).
We are plenty, and shared maintenance can help relieve the administrators of the overall infrastructure a little. Plus we can engage and empower us through skill sharing, and learn more about the internals of WordPress, and ways to migrate away when needed.
Would you see a chance that we can liberate the WordPress maintenance from the central maintenance cycle, and find an independent council to coordinate around improvements and error mitigation?
@AnandaVimal @franziska @leohnever @gandhiano @captainplanet @LankaGAIA @saritamoreira @robert.orzanna @yova @acorbi