Hi Yusaku,
I think testing GitHub pull request model is a good idea. We should
confirm the value of pull-request model before we switch.
I would like to help writing a draft for the contribution guide.
t;> > > >We can look into the already available component names in the JIRA for
>>>> > > >the initial list.
>>>> > > >We should not create fine-grained groups and aim to have at least 3-5
>>>> > > >devs (mor
;devs (more is better) in a single component/area.
>>> > > >
>>> > > >Possible list:
>>> > > >ambari-web
>>> > > >ambari-views
>>> > > >ambari-server
>>> > > >ambari-agent
>>> > &g
ari-server
>> > > >ambari-agent
>> > > >stacks-framework/extensibility
>> > > >stack-definitions (this could break into separate services)
>> > > >blueprints
>> > > >alerts/metrics
>> > > >logsearc
t; > > >stack-definitions (this could break into separate services)
> > > >blueprints
> > > >alerts/metrics
> > > >logsearch
> > > >security/kerberos/ldap
> > > >stack-upgrade/RU/EU
> > > >
> > > >Once the list
y/kerberos/ldap
> > >stack-upgrade/RU/EU
> > >
> > >Once the list is final lets make sure that the available list of
> > >components in the JIRA matches this list.
> > >
> > >This is probably also a good opportunity to see if there are better
> > >alternat
see if there are better
> >alternatives to reviews.apache.org.
> >
> >regards
> >Sumit
> >
> >From: Jayush Luniya
> >Sent: Thursday, June 02, 2016 1:47 PM
> >To: dev@ambari.apache.org
> >Subject: Re: Co
>From: Jayush Luniya
>Sent: Thursday, June 02, 2016 1:47 PM
>To: dev@ambari.apache.org
>Subject: Re: Code Review groups
>
>+1 on this
>
>
>On 6/2/16, 1:44 PM, "Swapan Shridhar" wrote:
>
>>+1. Makes sense.
>>
>>Thanks.
>>
>>
opportunity to see if there are better
alternatives to reviews.apache.org.
regards
Sumit
From: Jayush Luniya
Sent: Thursday, June 02, 2016 1:47 PM
To: dev@ambari.apache.org
Subject: Re: Code Review groups
+1 on this
On 6/2/16, 1:44 PM, "Swapan Shridhar&qu
+1 on this
On 6/2/16, 1:44 PM, "Swapan Shridhar" wrote:
>+1. Makes sense.
>
>Thanks.
>
>Regards,
>Swapan.
>
>
>
>
>
>
>
>
>
>On 6/2/16, 1:27 PM, "Robert Levas" wrote:
>
>>Alejandro, I agree. I just hope we (as a group) can manage the wiki
>>page without letting it get too stale over time.
>>
+1.
Alejandro, do you want to create a starter wiki and let folks sign up for their
areas of expertise?
Yusaku
On 6/2/16, 1:44 PM, "Swapan Shridhar" wrote:
>+1. Makes sense.
>
>Thanks.
>
>Regards,
>Swapan.
>
>
>
>
>
>
>
>
>
>On 6/2/16, 1:27 PM, "Robert Levas" wrote:
>
>>Alejandro, I agree
+1. Makes sense.
Thanks.
Regards,
Swapan.
On 6/2/16, 1:27 PM, "Robert Levas" wrote:
>Alejandro, I agree. I just hope we (as a group) can manage the wiki page
>without letting it get too stale over time.
>
>+1
>
>Rob
>
>
>On 6/2/16, 12:55 PM, "Alejandro Fernandez" wrote:
>
>>Hi comm
Alejandro, I agree. I just hope we (as a group) can manage the wiki page
without letting it get too stale over time.
+1
Rob
On 6/2/16, 12:55 PM, "Alejandro Fernandez" wrote:
>Hi committers and contributors,
>
>I'm sure most of you have ran into this before; whenever I submit a code
>revie
Hi committers and contributors,
I'm sure most of you have ran into this before; whenever I submit a code review
I'm always curious to find out which reviewers I should include that are
knowledgeable in that area.
So I'll typically run git blame to find the last 2-3 people that worked on
those f
14 matches
Mail list logo
