Hi Justin, On the seniority point, I wanted to add a bit more context from our side.
Since the beginning, the Fluss community has worked with contributors regardless of title or seniority. In practice, I believe most people involved have had “Senior Engineer” as their title at most, and we have always focused more on people’s interest, willingness to learn, and actual contributions than on title status. -- we have also guided them and helped them to pick work based on their individual interests, instead of trying to navigate and just "look at good-first-issues" that might be outside of their interest, to help them better engage. We have also actively mentored younger engineers and people who wanted to build new skillsets. This has included contributors who wanted to gain experience in areas like Helm charts, as well as students looking for support to participate in programs such as Google Summer of Code. In those cases, the community helped guide them, discuss ideas, and mentor them through the process of shaping and creating proposals. >From our perspective, Fluss has never been a title-driven community. We have tried to create an environment where people can contribute, learn, and grow, regardless of their formal seniority level. I believe the broader community can also verify this. This is not always easy to achieve, especially because many people contribute a significant amount of time outside of their regular working hours. I genuinely believe Fluss sets a high standard in terms of openness, support, and welcoming contributors, despite how busy everyone has been building the project. At the same time, the amount of product work delivered also speaks for itself. If I understand the concern correctly, part of the question may be about better understanding the contributions of certain PPMC members. I do not want to name individuals here, but there are a few members who, due to their daily workloads, have not always been able to contribute actively on a day-to-day basis. However, they have still made meaningful contributions in other ways: opening important doors for Fluss, promoting the project in the broader community, and making themselves available when something urgent came up. In several cases, when immediate attention was needed, these people genuinely stepped in, made time outside their regular responsibilities, and helped resolve issues. I think those contributions are also important to recognize, even if they are not always reflected in the same way as day-to-day code or documentation contributions. I hope this helps provide more context. Best, Giannis
