This sounds sensible, especially since the plugfest should give projects an opportunity to more tangibly understand what is achievable in Euphrates and have a more in-depth understanding of plan.
One request I have made of David and now make of all of you: please make sure to give visibility in the ongoing feasibility of your plans, especially as it related to dependencies. Obviously David is tracking this as well, but sometimes in service to optimism or a desire to not rock the boat, we have projects making overly optimistic expressions of their health. I understand that often we don't have full control of upstream bugs in OPNFV; I understand that sometimes the proverbial sludge does hit the fan last-minute no matter how much planning occurs, but just please remember that none of us is operating in a silo and our pain affect others. In an open and transparent community, one of the most important things any of us can do is stand up and say "this isn't working as I'd hoped, and I need more help and I'm worried this will impact overall deployment stability." I liken this to the Toyota mentality of lean manufacturing -- where continuous integration is key and every single person has the ability to stop the line at any point if things aren't working. At the same time it's the overall plant's health, not your particular work output, that matters the most. So, please please please, as the work streams in which you're involved get blocked or unstable or problematic, please raise your hand so we can solve things together as a community. The earlier the better. Also, please please please don't just drop out silently as a project if you're having trouble with a milestone. As soon as you can see that you don't have the bandwidth or resourcing or understanding to enable success, please come to David with your issues, so we can help you troubleshoot them and see if there's a way forward. It's always fine to drop out of a release if you've got longer horizons or shifting priorities (or for any reason at all -- this is volunteer work after all), but if it's not "voluntary" but rather because you're struggling, we are here to help you. I can't promise that we'll find a solution, but at least let's have the conversation. I feel as though I've iterated this several times (around the community health metrics discussion), but talking about issues and problems is not something to be avoided; it's something to be embraced to keep our community as healthy and productive as it can be. The more visibility you give the team, the more help you can receive. Heather On Tue, Apr 11, 2017 at 5:22 PM, David McBride <dmcbr...@linuxfoundation.org > wrote: > Team, > > As you know, Milestone 1 is the deadline for intent-to-participate, and > for project release plans. On the TSC call this morning, some community > members said that they would like to use the upcoming plugfest to finalized > their release planning for Euphrates. > > Therefore, based on consent of the TSC, MS1 has been moved out 8 days to > May 2, which is the Tuesday following the week of plugfest. No other > milestones are effected. The Euphrates release schedule > <https://wiki.opnfv.org/display/SWREL/Euphrates> has been updated, > accordingly. > > Please let me know if you have questions or comments. > > David > > -- > *David McBride* > Release Manager, OPNFV > Mobile: +1.805.276.8018 > Email/Google Talk: dmcbr...@linuxfoundation.org > Skype: davidjmcbride1 > IRC: dmcbride > > _______________________________________________ > opnfv-project-leads mailing list > opnfv-project-le...@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads > > -- *Heather Kirksey* Director, OPNFV Mobile: +1.512.917.7938 Email/Google Talk: hkirk...@linuxfoundation.org Skype: HeatherReneeKirksey IRC: HKirksey [image: OPNFV_RGB.png]
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
