+1 nb I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.

All agreed with Matt's points. To add to this, Prometheus has its own mailing list, and this will be true of others I suspect. We have had confusion about how mailing lists are supposed to work in

Hi, Yeah, good idea :) I've always missed networking channels for maintainers, I mean "inter-projects". And for the upcoming CloudNativeCon, I think would be great if CNCF could arrange some

+1 to this idea.

+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here. - Lee

+1 from me as well. Thanks Paris!

Big +1 from me. Very excited to see this SIG form as I think this is an area that many projects struggle with. The projects that don't struggle with this have some very overworked maintainers. ;)

Hi TOC and community, I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and

Liz Rice has called a vote on increasing the requirement to join Sandbox to three TOC sponsors (up from two) as we are increasing the size of the TOC from 9 to 11 seats. This goes into effect with the

I've been confused about this and I know others have been as well so I wanted to see If I have it right now and help others know how the CNCF project maintainer mailing lists work. The details: Each

There's isn't a general mailing list that maintainers can use to contact each other. There is a mass distribution list (not on lists.cncf.io) where all content sent to it is moderated. Maintainers are

Thanks for raising this, it’s important for sure. Is this something that could / should fit in the remit of Paris’s proposed SIG Contribex? -- Liz Rice @lizrice | lizrice.com | +44 (0) 780 126

+1 binding (explicitly adding my vote, after calling the vote!) -- Liz Rice @lizrice | lizrice.com | +44 (0) 780 126 1145

While we're talking about this... If anyone needs someone to talk to or figure out how to deal with this stuff... I am happy to listen and share what I've learned. I feel like I have a system (that

This is a no brainer, we will create a mailing list to start: https://github.com/cncf/toc/issues/339 We are also gearing up for our bi-annual maintainer survey next month, so if you have questions or

> Brandon and I hosted two zoom meetings last year where we invited all the maintainers to give us feedback on what the CNCF can do for them. I learned a lot from those meetings including lots of

I like this very much. I have been in this hole and it's highly-nonobvious that this was even happening, or what, initially, to do about it. This could also be part of CloudNativeCons, though I am

Thanks for bringing this up Matt. I agree many open source maintainers feel this way and we need to talk more about sustainable processes and expectations. We do have a maintainers mailing list but I

The maintainer of a popular Rust project quit this morning and took down the project. Buried in the post mortem: If you maintain something that gets popular this is bound to happen. I appreciate that

Haven’t had a chance - I was on holidays myself which is why I didn’t jump back into this and other threads earlier earlier. Fresh thoughts as I return with a clear head. :) I will be in SIG App