[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-dev
Subject:    Re: [DISCUSS] Non Coding Committers
From:       Sharan Foga <sharan () apache ! org>
Date:       2022-02-11 14:15:42
Message-ID: pony-1c11b627-040e-4a4e-9474-4ef0b271621f-dev () cassandra ! apache ! org
[Download RAW message or body]

Hi All

Thanks very much to everyone who took the time to provide feedback and share their \
views on this topic. It seems to me like there is a general consensus around it and \
it's great to hear that the PMC is aware and actively working on it.

A community is an evolving thing and so adapting to change is part of the journey. I \
am really happy to see this open dialogue happening and even though some current \
problems have been highlighted - the focus is on resolving them! 

Happy to be involved and part of this community :-)

Thanks
Sharan

On 2022/02/09 09:12:56 Benjamin Lerer wrote:
> Thanks a lot Sharan, Patrick and Lorina.
> It is a perfectly valid point that the PMC members have recognized for some
> time already and are actively working on.
> 😊
> 
> Le mar. 8 févr. 2022 à 23:07, Lorina Poland <lorina@datastax.com> a écrit :
> 
> > +1 to this conversation, from a Docs wonk. :-)
> > 
> > On Tue, Feb 8, 2022 at 1:40 PM Patrick McFadin <pmcfadin@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 <mck@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.
> > > > 
> > > > 
> 


[prev in list] [next in list] [prev in thread] [next in thread]