Just to be clear, I welcome Josh's help with project management. Dinesh
> On Jan 10, 2020, at 12:53 PM, Dinesh Joshi <djo...@apache.org> wrote: > > My 2¢. > > We need more folks reviewing tickets and providing feedback and testing the > submitted patches. There are many low complexity patches out there that are > in need of reviews. Any help in that direction is appreciated. Even if they > aren't familiar with the part of codebase, a first review gives them the > opportunity to learn. Obviously a committer who is familiar with that part of > the codebase can do a second review and commit it. > > Dinesh > >> On Jan 10, 2020, at 11:23 AM, David Capwell <dcapw...@gmail.com> wrote: >> >> I also find that assigning tickets to people when they have no bandwidth to >> implement them is counterproductive. >> >> >> Isn’t this the point of project management; to avoid this issue? >> >> Lets say there are 10 blocking tickets for 4.0, and they are all on you; a >> PM could help by finding others who could help out and make sure that no >> one steps on each other. >> >> At the same time, PMs help give visibility into how much work is left and >> are previous time estimates off (we expect M2 done January, are we close? >> Do we need to punt things to M3? Do we need to load balance to make this >> date?, etc.). >> >> I don't think anything is currently languishing because nobody realises it >> needs to be done, but if you can get things magically moving faster, I will >> of course be thrilled! __ >> >> >> So lets try and see what happens! =D >> >> On Fri, Jan 10, 2020 at 11:12 AM Mick Semb Wever <m...@apache.org> wrote: >> >>> >>> >>>> One thing I'd love to see >>>> again is a regular (every two weeks?) update on progress on the dev list >>>> (similar to what Jeff Jirsa used to send around -- it also included a >>> call >>>> for reviews iirc). >>> >>> >>> Yes, I also miss those fortnightly (or monthly) summaries that Jeff used >>> to do. They were very useful "glue" in the community. I imagine they'd also >>> make writing the board report easier. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >>> For additional commands, e-mail: dev-h...@cassandra.apache.org >>> >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
