Thanks Jeff - I have an initial rough draft of basically exactly what you've enumerated above from starting to formally ramp back up last week I'll tidy up and try to get out here Monday.
And thanks everyone for the discussion. This is Hard Stuff; a huge part of the Apache Way (at least on our project ;) ) is Lazy Consensus <https://community.apache.org/committers/lazyConsensus.html> and a lot of "ask for forgiveness, not permission", and it can be really hard to navigate that and can also deform cultures in the case of uneven cross-vendor resourcing. I think as long as we all believe we're all good faith actors, truly believe we all want what's best for the project (even if we don't necessarily all agree on what that is all the time), and internalize that nobody wants to see a monoculture on the project, we'll be fine. On Sat, Jan 11, 2020 at 2:45 PM Jeff Jirsa <jji...@gmail.com> wrote: > Back to the original question in the thread - I think a critical pass > through open issues is warranted - > > What hasn’t been triaged? > What is slated for 4.0 but unassigned ? > What is patch available but needs more engineering ? > What is ready to commit and uncommitted? > > You’ve got the context to understand what’s critical and what justifies > sending to someone as a potentially concerning bug even without a repro, > where a lot of others wouldn’t / don’t. So I’d suggest starting there and > trying to make sure there aren’t any critical bug reports around that > slipped through past triage attempts. > > > > > On Jan 10, 2020, at 8:18 AM, Joshua McKenzie <jmcken...@apache.org> > wrote: > > > > Hey all, > > > > I've recently had some cycles free up I can dedicate to the open-source > > project. My intuition is that I can add the most value right now by > > engaging in some simple project management type work (help get assignees > > and reviewers for things critical path for 4.0, help stimulate and > > facilitate discussions about scope for the upcoming release and > subsequent > > releases, general triage and test board health, etc). > > > > Before I wade into the project and start poking and prodding us all, does > > anyone have any concerns with me stepping (back ;) ) into this role, or > > have any feedback or recommendations before doing so? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
