Hey folks, Have we considered making these just 5 separate projects (which basically what they are)? That'd fit the OPNFV structure, gives each project a dedicated repo (which they have already), and a dedicated set of committers plus a PTO...
Frank -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Bramwell Sent: Sonntag, 10. Dezember 2017 15:34 To: Fatih Degirmenci <[email protected]> Cc: Serena Feng <[email protected]>; [email protected] Subject: Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository +1 Giving leaders of subproject the freedom to manage +2 rights on their own repository will be very helpful for ensuring patches are reviewed by those with the correct competencies and merged in a timely manner. Perhaps having a 'mini-info' file in each repository would help track this, intead of expanding the current INFO file. Simple fields such as: parent-project, project-name, creation-date, subproject-lead, committers, and parent-project-approval-link would work. This is merely a suggestion though, and a decision on this shouldn't block us from moving forward. I'm fine with things currently being added the INFO file. Regards, Trevor Bramwell On Fri, Dec 08, 2017 at 12:01:34AM +0000, Fatih Degirmenci wrote: > 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
