Three weeks ago, I released the Pluto Beta of Planet for the MySQL Community. Since then, a few things changed and I think it is worth doing an update to the Ecosystem. The change I am the most happy about is that Ivan Groenewold started helping with the project (you can find him in the people of the oursqlcommunity.org GitHub organization). So Planet for the MySQL Community is not a one-man
As indicated in a previous post, I am working on Planet [for the] MySQL Community for which I did a RFC on the Requirements. I am happy to announce the beta release of Planet [for the] MySQL Community using the Planet Pluto Free Feed Reader and (Static) Website Generator. If you are in a hurry, you can check it out at https://planet-beta-pluto.oursqlcommunity.org/. This post describes how I
As indicated in a previous post, I am working on a Planet MySQL Community (this name is not final, see below). In this post, I want to present what I think the requirements should be for this new aggregator. This is a Request for Comment (RFC): I do not claim completeness nor perfection, this might (will) evolve, and your remarks are welcome. A tl&dr is available in the Summary of Requirements
Oups, my previous post had a forbidden word and did not show-up on Planet MySQL, so retry...
As written in a previous post, the state of Planet MySQL is unhealthy ! I am still aggregated there for now as, before leaving what was the best news-feed for the MySQL Community, we need a replacement. This post aims at starting a discussion on this replacement.
Update 2020-05-12: I wrote a follow-up
Also, the state of bugs.mysql.com: unhealthy (last paragraph below, but this would be too long a title).
I have been complaining for some time about Planet MySQL filtering content that I think it should not. Shlomi made a courageous decision on this and explained it in his recent post (Pulling his blog out of Planet MySQL aggregator, over community concerns). I am thinking of doing the same.