On Thu, May 7, 2015 at 2:54 PM, William Markito <[email protected]> wrote: > Just to complement what I have said about component leaders: > > The important thing about this kind of assignment wouldn't be to have only > a single person to control them, but much more on to help the community to > work with the experts of each area/component and also to assign some > responsibility to this people to review/look at the changes. > > We can always argue both ways, RTC or CTR have their own merits and > benefits, but in the end of the day what we probably want is to make sure > that the code base is stable and the core principles of the project > (performance, for one) are always taken care of.
Well, at this stage what we really need is to make sure that we grow the community. Now, of course, I'm not suggesting that we wreck the stability of the project by doing that, but rather have mentors who can onboard folks on the areas of their expertise. IOW, think of these 'owners' as the first responders to issues that fall into the area of their expertise. We should absolutely compile a list of such experts on our wiki and also make them JIRA owners of particular areas of Geode. The expectations, once again, will be that they will be the known people to ping for feedback, etc not that they would be required to sign-off on every single commit. After all, we're using SCM for a reason: things can be backed out. And if a community backs out your change it sends a pretty strong signal that you may be better off asking for an expert opinion next time. The good news is that we will maintain that list of experts for you. Thanks, Roman.
