I was particularly influenced by this mental model of thinking about open
source contributions in the past:
https://d33wubrfki0l68.cloudfront.net/dfb15f354706fa763ff385e5eea61520bcdcf8bb/1b0fc/assets/media/community-engagement-oss-image.png
Related article: https://www.bvp.com/atlas/roadmap-open-s
Thanks Benjamin. Regarding contributors, what you say here makes sense and
we will discuss other ways to highlight, e.g. in the monthly Changelog,
interview them for the site, etc. Same for users. Beyond the case studies
page and Changelog blog, we'll discuss other ways to thank/interact with
them.
>
> Sounds great. By community, do you mean both those who build and/or use C*
> (or just the folks on dev list)? There are a number of ways we can showcase
> this. And is there a general goal of growing the number of contributors
> and/or committers? We worked with Ekaterina last year to get this
Thanks, Benjamin!
> One critical part that we should try to put more forward in 2022 is the
community. On Twitter people are quite responsive to it. We have a great
community and we should make sure that people feel that they belong to it.
Sounds great. By community, do you mean both those who bu
Melissa, Chris, Diogenese,
Thanks a lot for everything you did in 2021 😀
What you propose for 2022 sounds great.
One critical part that we should try to put more forward in 2022 is the
community. On Twitter people are quite responsive to it. We have a great
community and we should make sure that
Chris Thornett, Diogenese Topper and I compiled a recap of the marketing
work we contributed to Cassandra in 2021. We also developed a recommended
approach for 2022. Our aim is to be a resource that advances the
community's interests, so we would greatly appreciate your input here
and/or in the dec
