Hi Fatih, this was just a suggestion - mostly to keep Releng in line with what other projects do in OPNFV - the test-projects are probably the closest comparison here. I also don't think that there would not be much of a change: You'd have a Releng working group with several projects (those 5) participating, i.e. the structure would look much like what is done for testing.
Anyway - just do what the contributors and committers feel is best for Releng. Cheers, Frank -----Original Message----- From: Fatih Degirmenci [mailto:fatih.degirme...@ericsson.com] Sent: Montag, 11. Dezember 2017 05:20 To: Frank Brockners (fbrockne) <fbroc...@cisco.com>; Trevor Bramwell <tbramw...@linuxfoundation.org> Cc: Serena Feng <feng.xiao...@zte.com.cn>; opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository Hi Frank, Thanks for the feedback. Splitting Releng is perhaps an option but I personally do not think it will add too much value. I believe support functions such as what Releng aims to provide is best handled as a whole rather than multiple individual projects. This is important in order to ensure the project provides best service to the community and sub teams follow overall direction set by Infra WG in general and Releng Project in particular. With that said, if any Releng committer comes up with a proposal to split Releng, resulting in multiple smaller projects, we can put these 2 proposals to vote and do accordingly. Another thing I would like to highlight is that the proposed setup with subprojects/teams is pretty similar to how OpenStack Infra project works; top level Infra project and multiple sub teams that specialize in certain aspects of the infra. [1] We as project need to work on the details if this proposal is accepted and approved by the TSC. Until this happens, that link can give an idea regarding where we might end up. One last point is, Releng will probably not be the only one with this need. We are just the first one. [1] https://docs.openstack.org/infra/system-config/project.html#teams /Fatih On 2017-12-11, 03:03, "Frank Brockners (fbrockne)" <fbroc...@cisco.com> wrote: 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: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Trevor Bramwell Sent: Sonntag, 10. Dezember 2017 15:34 To: Fatih Degirmenci <fatih.degirme...@ericsson.com> Cc: Serena Feng <feng.xiao...@zte.com.cn>; opnfv-tech-discuss@lists.opnfv.org 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 opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
