You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Oleg Kalnichevski <ol...@apache.org> on 2017/05/04 14:51:42 UTC
Git repo names; Re: [VOTE][Simple Majority] Migrate project source
repository to Git
On Thu, 2017-05-04 at 15:59 +0200, Michael Osipov wrote:
> While I do say +1 the vote is incomplete:
> You missed to provide the target Git repo names. E.g., you won't name
> httpcomponents/project/ => project right?
>
Does this need to be in the vote? I thought it would only matter when
asking infra to do the actual migration. If it does I can restart the
vote.
> I'd propose the following:
>
> httpcomponents-core
> httpcomponents-client
> httpcomponents-parent
> httpcomponents-stylecheck
> httpcomponents-site
>
I would go with
hc instead of httpcomponents if infra allow it.
> It might also reasonable to reconsider the artifactId of project
> because
> <artifactId>project</artifactId> is quite general. httpcomponents-
> parent
> sounds reasonable to me.
>
By all of means feel free to fix it.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Git repo names; Re: [VOTE][Simple Majority] Migrate project
source repository to Git
Posted by Gary Gregory <ga...@gmail.com>.
On Thu, May 4, 2017 at 9:21 AM, Michael Osipov <mi...@apache.org> wrote:
> Am 2017-05-04 um 16:51 schrieb Oleg Kalnichevski:
>
>> On Thu, 2017-05-04 at 15:59 +0200, Michael Osipov wrote:
>>
>>> While I do say +1 the vote is incomplete:
>>> You missed to provide the target Git repo names. E.g., you won't name
>>> httpcomponents/project/ => project right?
>>>
>>>
>> Does this need to be in the vote? I thought it would only matter when
>> asking infra to do the actual migration. If it does I can restart the
>> vote.
>>
>
> It should be at least mentioned that repo names must be changed. No need
> to revote, let's spin a new discussion when this vote is over.
>
> I'd propose the following:
>>>
>>> httpcomponents-core
>>> httpcomponents-client
>>> httpcomponents-parent
>>> httpcomponents-stylecheck
>>> httpcomponents-site
>>>
>>>
>> I would go with
>>
>> hc instead of httpcomponents if infra allow it.
>>
>
> I prefer compact names too, but repo names have to resemble like project
> names. Consider that people are listing our repos at git.apache.org or
> GitHub and filter for 'http' simpyl because new artifactIds are 'http...',
> though I have no strong preference here. Let the majority decide later.
>
It is a bit odd that "http" would not be in the artifact name.
>
> It might also reasonable to reconsider the artifactId of project
>>> because
>>> <artifactId>project</artifactId> is quite general. httpcomponents-
>>> parent
>>> sounds reasonable to me.
>>>
>>>
>> By all of means feel free to fix it.
>>
>
> Any objects from others here? If there won't be any within a few days,
> I'll go ahead and do it.
>
+1
Gary
>
> Michael
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
JUnit in Action, Second Edition
<https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
Spring Batch in Action
<https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: Git repo names; Re: [VOTE][Simple Majority] Migrate project
source repository to Git
Posted by Michael Osipov <mi...@apache.org>.
Am 2017-05-04 um 16:51 schrieb Oleg Kalnichevski:
> On Thu, 2017-05-04 at 15:59 +0200, Michael Osipov wrote:
>> While I do say +1 the vote is incomplete:
>> You missed to provide the target Git repo names. E.g., you won't name
>> httpcomponents/project/ => project right?
>>
>
> Does this need to be in the vote? I thought it would only matter when
> asking infra to do the actual migration. If it does I can restart the
> vote.
It should be at least mentioned that repo names must be changed. No need
to revote, let's spin a new discussion when this vote is over.
>> I'd propose the following:
>>
>> httpcomponents-core
>> httpcomponents-client
>> httpcomponents-parent
>> httpcomponents-stylecheck
>> httpcomponents-site
>>
>
> I would go with
>
> hc instead of httpcomponents if infra allow it.
I prefer compact names too, but repo names have to resemble like project
names. Consider that people are listing our repos at git.apache.org or
GitHub and filter for 'http' simpyl because new artifactIds are
'http...', though I have no strong preference here. Let the majority
decide later.
>> It might also reasonable to reconsider the artifactId of project
>> because
>> <artifactId>project</artifactId> is quite general. httpcomponents-
>> parent
>> sounds reasonable to me.
>>
>
> By all of means feel free to fix it.
Any objects from others here? If there won't be any within a few days,
I'll go ahead and do it.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org