Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-11 Thread Frank Brockners (fbrockne) 
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 +, 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

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-11 Thread Jose Lausuch 
+1

Jose





> On 08 Dec 2017, at 01:01, 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

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-11 Thread Fatih Degirmenci 
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 +, 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-te

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-10 Thread Frank Brockners (fbrockne) 
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 +, 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

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-10 Thread Trevor Bramwell 
+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 +, 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

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-10 Thread Luke Hinds 
Only caveat I have is that there are no committers (or regular reviewers)
to releng-anteater to get patches landed.

With that in mind though, I don't mind moving the project back to github
(where its easier for anyone to patch) and we keep all the project
exception files in releng (where it would have a high amount of commiters
who can help review what would only be regular expressions).

The above would suit me well, as I would like to get anteater more adopted
upstream as others have shown an interest in implementing the project.


On Fri, Dec 8, 2017 at 9:05 AM, Markos Chandras  wrote:

> +1
>
> On 12/08/2017 12:01 AM, 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
> >
>
>
> --
> markos
>
> SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
> HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
>



-- 
Luke Hinds | NFV Partner Engineering | CTO Office | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-08 Thread Markos Chandras 
+1

On 12/08/2017 12:01 AM, 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
> 


-- 
markos

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-07 Thread Tallgren, Tapio (Nokia - FI/Espoo) 
+1


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Fatih Degirmenci 

Sent: Friday, December 8, 2017 2:01:34 AM
To: Aric Gardner; Tim Rozet; Morgan Richomme; Jose  Lausuch; Ryota; Meimei; 
Trevor Bramwell; Serena Feng; Yolanda Robla Mota; Markos Chandras; Luke Hinds
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [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
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-07 Thread Cedric OLLIVIER 
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"  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:fatih.degirme...@ericsson.com]
> *Sent:* Friday, December 08, 2017 9:02 AM
> *To:* Aric Gardner ; Tim Rozet <
> tro...@redhat.com>; Morgan Richomme ; Jose
> Lausuch ; Mibu Ryota(壬生 亮太) ;
> Meimei ; Trevor Bramwell ;
> Serena Feng ; Yolanda Robla Mota <
> yrobl...@redhat.com>; Markos Chandras ; Luke Hinds <
> lhi...@redhat.com>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *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
> 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

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-07 Thread Aric Gardner 
+1
Good idea, will each repo need an INFO file, or will we track the
committers by sub project in the parent repo?


On Thu, Dec 7, 2017 at 7:01 PM, 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

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-07 Thread Fatih Degirmenci 
Hi Ryota,

Introducing sub-team lead was part of our conversation today and we will work 
on it when/if our proposal gets agreed within Releng project and approved by 
TSC.

/Fatih

From: Ryota 
Date: Thursday, 7 December 2017 at 16:16
To: Fatih Degirmenci , 
"agard...@linuxfoundation.org" , 'Tim Rozet' 
, Morgan Richomme , Jose Lausuch 
, Meimei , Trevor Bramwell 
, Serena Feng , Yolanda 
Mota , Markos Chandras , Luke Hinds 

Cc: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: RE: [releng] Committer list per Releng repository

+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:fatih.degirme...@ericsson.com]
Sent: Friday, December 08, 2017 9:02 AM
To: Aric Gardner ; Tim Rozet ; 
Morgan Richomme ; Jose Lausuch 
; Mibu Ryota(壬生 亮太) ; Meimei 
; Trevor Bramwell ; Serena 
Feng ; Yolanda Robla Mota ; 
Markos Chandras ; Luke Hinds 
Cc: opnfv-tech-discuss@lists.opnfv.org
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
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017-12-07 Thread Ryota Mibu 
+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:fatih.degirme...@ericsson.com]
Sent: Friday, December 08, 2017 9:02 AM
To: Aric Gardner ; Tim Rozet ; 
Morgan Richomme ; Jose Lausuch 
; Mibu Ryota(壬生 亮太) ; Meimei 
; Trevor Bramwell ; Serena 
Feng ; Yolanda Robla Mota ; 
Markos Chandras ; Luke Hinds 
Cc: opnfv-tech-discuss@lists.opnfv.org
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
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss