2017-02-09 11:54, O'Driscoll, Tim: > From: dev [mailto:[email protected]] On Behalf Of Thomas Monjalon > > I suggest that the technical board should check whether every new > > proposed features are explained, discussed and approved enough in > > the community. > > I assume you don't mean every new feature, just those that involve > major changes (new libraries, new/modified APIs etc.). Is that correct?
Yes, it is not about drivers. It is more about API. > > If needed, the technical board meeting minutes will give some lights to > > the threads which require more attention. > > Before adding a new library or adding a major API, there should be > > some strong reviews which include discussing the DPDK scope. > > > > Openness of a large community is proven by its active feedbacks. > > +1 > > At the moment, when there's no feedback on an RFC or patch set, there's no > way of knowing whether that means people are happy with it or that nobody has > reviewed it. Using the Tech Board to highlight RFCs/patch sets that require > more review is a good idea. Yes it is my thought: we should have several explicit agreements for important patches.
