+1 to this conversation, from a Docs wonk. :-) On Tue, Feb 8, 2022 at 1:40 PM Patrick McFadin <pmcfa...@gmail.com> wrote:
> Sharan has done a good job shining a spotlight on something that has > created a weird bottleneck in the project. Docs and the Cassandra website > are all in-tree, but it takes somebody who probably isn't even working on > those things to commit any changes. Dinesh nailed it. It's silly. I'm sure > the PMC can come up with a reasonable solution that can be done quickly. > There are a lot of us that love this project that contribute in ways that > don't get compiled into a jar file. This is something that needs to be > solved for the sake of project velocity. > > Patrick > > On Sun, Feb 6, 2022 at 10:28 PM Mick Semb Wever <m...@apache.org> wrote: > >> >> Thank you Sharan for sharing. >> >> >>> So here in Apache Cassandra I see there is a whole lot of activity >>> happening around the website, marketing, project promotion, blogs, social >>> media - these activities are all contributions to the project. If there are >>> contributions happening in the project that need a committer to action, >>> then it could make sense to consider having committers that are focussed >>> around the 'non coding' parts. >>> >>> >>> >> >> This is so true for us. We are spending a lot of extra time getting these >> non-code contributions across the finish line. The context switching and >> wait time involved in just one more handover, and often across time zones, >> is hurting. And regardless, totally agree we should be formally recognising >> the ongoing work that goes into these non-coding contributions. >> >>
