Extra time contributed to the project by an experienced community member in either developer or project management areas would be very helpful in completing 4.0. Thanks for volunteering Josh -- and +1 on thanking Scott for his existing efforts (and Benedict and others who worked to improve the JIRA workflow this release cycle). I agree that having folks driving regular community check ins on progress (or working to keep progress up to date), among other things, would be beneficial. 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).
Jordan On Fri, Jan 10, 2020 at 9:04 AM Joshua McKenzie <jmcken...@apache.org> wrote: > > > > developer time from your employer would probably be more impactful > > Certainly, and there's movement on that side as well but that's > independent from my current purview so I don't feel it appropriate for me > to speak to that. > > the project has already largely agreed on the work that is necessary for > > 4.0, and is executing on it as quickly as resources allow > > This JQL on the release > < > https://issues.apache.org/jira/issues/?jql=project%20%3D%20cassandra%20and%20fixversion%20~%204.0%20and%20resolution%20%3D%20unresolved%20and%20status%20!%3D%20resolved%20and%20(assignee%20is%20empty%20or%20(reviewer%20is%20empty%20and%20reviewers%20is%20empty))%20order%20by%20priority%20desc%2C%20assignee > > > indicates that 49 of the 72 open issues are lacking either an assignee or a > reviewer. I can only speak to my experience on this and other software > projects, but I find a lot of things slip through the cracks by virtue of > not having ownership for various points in their pipeline or stall based on > people not realizing things are on their plate (we had quite a few tickets > marked 4.0 assigned to people no longer active on the project, for > instance). > > I also believe that what qualifies as scope for a release requires constant > vigilance and healthy gentle skepticism from the devil's advocate position > on minimizing scope to help counter-balance our tendencies as engineers to > want to get things into releases, especially when there are longer cycle > times. We've seen it on almost every major release on this project, and > it's healthy and a great sign of people's passion and dedication to this > project and their craft, but without a countering force I personally > believe it leads to lengthened cycle times and isn't a healthy balance for > the project. This is a strong opinion of mine but it's loosely held; I'm > open to other data or experiences that can help shape this perspective. > > One thing I want to clarify - Scott in particular and the community as a > whole has been doing great work both managing this project and driving > things forward; I'm not trying to step into some perceived gap or rescue > something, but rather meet people where they are and add what value I can > and work with the project to help keep momentum high and remove blockers or > stalls from people's workflows. > > Does the above make sense? > > > > On Fri, Jan 10, 2020 at 8:30 AM Benedict Elliott Smith < > bened...@apache.org> > wrote: > > > I personally welcome your increased participation in any role, and more > > focus on project delivery is certainly a great thing. But developer time > > from your employer would probably be more impactful, as the main active > > contributors right now have their own project management infrastructure, > > and are already dedicating what resources they have to 4.0. So it's not > > 100% clear what resources you'll be able to facilitate better deploying. > > > > I think the project has already largely agreed on the work that is > > necessary for 4.0, and is executing on it as quickly as resources allow. > > > > > > On 10/01/2020, 16:18, "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 > > > > >
