Nova is doing a retrospective for the Newton release to reflect on what went well and what did not go well, and what, if anything, we can learn and improve. Not specific to the Newton release but the speed of development (features) and technical debt, specifically around having a huge repo with a ton of proposed changes but a relatively small active core team, always comes up. At various times different people have proposed different ideas on how to fix the code review latency issue. Ideas include simply scaling the core reviewer team (not having such a high bar to entry), decomposing the repo (breaking out the virt drivers), and subsystem maintainers (people with +2 in certain areas or features of code, but not +2 on the entire repo). This session is really meant to be a discussion between PTLs and core reviewers on various projects to see what ideas teams have tried and what has worked and what has not worked. For example, Neutron did the stadium to mixed results - but unless you are an active developer on Neutron you maybe do not know the details, so what happened?
References: Nova Newton retrospective etherpad
Session Leader(s): Matt Riedemann (mriedem), Steve Martinelli (stevemar), Doug Hellmann (dhellmann)