[reconditerose]

The beef I have here is that Redis also takes credit for community work. Most of the heavy lifting came from antirez, who created and ran the project up until 2020. (It's worth conceding that Redis did compensate antirez). At that time Redis created an open governing board that took over, with a majority of contributions coming from the community during this time (~25% of contributions came from Redis engineers, ~75% from the community, including ~3% that came from me personally). They own the trademark and the repository, so they can do what they want, but I take issue with the optics that this is really AWS or GCPs or some other vendors fault that Redis decided to blind side it's development community. Redis gave some of us a heads up this was happening, but most people are finding out by a blog post that Redis dissolved the previous open-governance (a fact they barely address in the blog post). We had to drop weeks of work on the floor because we could not longer finish it.

[klabb3]

That’s very interesting context and doesn’t look too good on the “Redis governing board” indeed.

[_msw_]

https://web.archive.org/web/20231030181609/https://redis.io/...

(the page is now a 404)

  The core team has the following remit:
   * Managing the core Redis code and documentation
   * Managing new Redis releases
   * Maintaining a high-level technical direction/roadmap
   * Providing a fast response, including fixes/patches, to address security vulnerabilities and other major issues
   * Project governance decisions and changes
   * Coordination of Redis core with the rest of the Redis ecosystem
   * Managing the membership of the core team

It seems clear to me (speaking only for myself) that the core team didn't have a say in project governance decisions and changes here. :-(

[throwaway290]

If core team's pay depends on it maybe they did have a say... Developers also grow up and start families you know