I consider this proposal as very good regarding the multiple different skills involved in the current releng tree. Functest could leverage on it too as it will incubate requirements and xtesting which could differ on interests and skills.
Switching to a dedicated project will cost at least to rename the git repository (gerrit?). Cédric Le 7 déc. 2017 4:21 PM, "Ryota Mibu" <[email protected]> a écrit : > +1 > > > > Also we need to consider long term transition. Each repo or sub-team would > be getting bigger then could be independent project/repo eventually. So, it > would be nice to find sub-team lead or key person who is responsible in > each repo along with this list modification. Just two cents though. > > > > BR, > > Ryota > > > > *From:* Fatih Degirmenci [mailto:[email protected]] > *Sent:* Friday, December 08, 2017 9:02 AM > *To:* Aric Gardner <[email protected]>; Tim Rozet < > [email protected]>; Morgan Richomme <[email protected]>; Jose > Lausuch <[email protected]>; Mibu Ryota(壬生 亮太) <[email protected]>; > Meimei <[email protected]>; Trevor Bramwell <[email protected]>; > Serena Feng <[email protected]>; Yolanda Robla Mota < > [email protected]>; Markos Chandras <[email protected]>; Luke Hinds < > [email protected]> > *Cc:* [email protected] > *Subject:* [releng] Committer list per Releng repository > > > > Hi Releng Committers, > > > > During OPNFV Plugfest, we had conversations around having committer list > per Releng repository/Gerrit Project. > > > > The reason behind this is that, Releng project currently has 5 different > repositories as listed below. [1] > > > > - releng > > - releng-anteater > > - releng-testresults > > - releng-utils > > - releng-xci > > > > The work that is done in these repositories require different competence > profiles. For example for releng repository, the committers need to have > knowledge in CI, Jenkins, Jenkins Job Builder and so on. > > Apart from the required competence, some developers might not be > interested in certain parts of Releng but interested in others. > > > > Having single committer list across all Releng owned repositories prevents > us from recognizing contributors and promoting them as committers for the > corresponding repositories since they will perhaps never have enough > contributions across all of them. > > Another limitation is that, the current review practices followed by > Releng is not good and we need to improve this. Having right set of > committers per repo and getting patches reviewed by them properly will help > with the quality of work we are doing. > > > > In order to address this limitation and have the ability and the > possibility to recognize and promote developers who made great > contributions to Releng in general in the repositories they worked in, I > propose to create committer list per repo. > > > > Please respond to this mail with +1 and -1 and share questions, comments, > concerns if you have any. > > > > I plan to bring this topic to TSC on December 12th if the vote passes. > > > > [1] https://gerrit.opnfv.org/gerrit/#/admin/projects/?filter=releng > > > > /Fatih > > _______________________________________________ > opnfv-tech-discuss mailing list > [email protected] > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > >
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
