[VOTE] Migrate Commons Weaver to Git

classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[VOTE] Migrate Commons Weaver to Git

Matt Benson-3
Hello,
After having received some support from a "feeler" email, I would like to
propose the formal vote to migrate this Commons component to Git for
version control. This vote will be open for at least 72 hours, or until
April 22, 2018 @ 16:00 UTC.

Thanks,
Matt
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate Commons Weaver to Git

Matt Benson-3
On Thu, Apr 19, 2018 at 10:46 AM, Matt Benson <[hidden email]> wrote:

> Hello,
> After having received some support from a "feeler" email, I would like to
> propose the formal vote to migrate this Commons component to Git for
> version control. This vote will be open for at least 72 hours, or until
> April 22, 2018 @ 16:00 UTC.
>
>
My own +1

Matt



> Thanks,
> Matt
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate Commons Weaver to Git

Matt Sicker
+1 (non-binding)

On 19 April 2018 at 10:47, Matt Benson <[hidden email]> wrote:

> On Thu, Apr 19, 2018 at 10:46 AM, Matt Benson <[hidden email]> wrote:
>
> > Hello,
> > After having received some support from a "feeler" email, I would like to
> > propose the formal vote to migrate this Commons component to Git for
> > version control. This vote will be open for at least 72 hours, or until
> > April 22, 2018 @ 16:00 UTC.
> >
> >
> My own +1
>
> Matt
>
>
>
> > Thanks,
> > Matt
> >
>



--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate Commons Weaver to Git

Rob Tompkins
In reply to this post by Matt Benson-3


> On Apr 19, 2018, at 11:46 AM, Matt Benson <[hidden email]> wrote:
>
> Hello,
> After having received some support from a "feeler" email, I would like to
> propose the formal vote to migrate this Commons component to Git for
> version control. This vote will be open for at least 72 hours, or until
> April 22, 2018 @ 16:00 UTC.
>

+1

> Thanks,
> Matt

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate Commons Weaver to Git

garydgregory
In reply to this post by Matt Benson-3
+1 (binding)

Gary


On Thu, Apr 19, 2018 at 9:46 AM, Matt Benson <[hidden email]> wrote:

> Hello,
> After having received some support from a "feeler" email, I would like to
> propose the formal vote to migrate this Commons component to Git for
> version control. This vote will be open for at least 72 hours, or until
> April 22, 2018 @ 16:00 UTC.
>
> Thanks,
> Matt
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate Commons Weaver to Git

Pascal Schumacher
In reply to this post by Matt Benson-3
+1

Am 19.04.2018 um 17:46 schrieb Matt Benson:
> Hello,
> After having received some support from a "feeler" email, I would like to
> propose the formal vote to migrate this Commons component to Git for
> version control. This vote will be open for at least 72 hours, or until
> April 22, 2018 @ 16:00 UTC.
>
> Thanks,
> Matt
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate Commons Weaver to Git

Romain Manni-Bucau
+1

Le 19 avr. 2018 20:17, "Pascal Schumacher" <[hidden email]> a
écrit :

> +1
>
> Am 19.04.2018 um 17:46 schrieb Matt Benson:
>
>> Hello,
>> After having received some support from a "feeler" email, I would like to
>> propose the formal vote to migrate this Commons component to Git for
>> version control. This vote will be open for at least 72 hours, or until
>> April 22, 2018 @ 16:00 UTC.
>>
>> Thanks,
>> Matt
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Discuss [VOTE] Migrate Commons Weaver to Git

Ralph Goers
In reply to this post by Matt Benson-3
Is this vote for Git or Gitbox or is there any difference these days?

Ralph

> On Apr 19, 2018, at 8:46 AM, Matt Benson <[hidden email]> wrote:
>
> Hello,
> After having received some support from a "feeler" email, I would like to
> propose the formal vote to migrate this Commons component to Git for
> version control. This vote will be open for at least 72 hours, or until
> April 22, 2018 @ 16:00 UTC.
>
> Thanks,
> Matt



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Matt Sicker
That’s actually a good question. The two options are still available. While
I think it would be pretty cool if all of Commons was on GitBox for
convenience, I’m pretty sure all the new repos have still been git-wip

On Thu, Apr 19, 2018 at 15:15, Ralph Goers <[hidden email]>
wrote:

> Is this vote for Git or Gitbox or is there any difference these days?
>
> Ralph
>
> > On Apr 19, 2018, at 8:46 AM, Matt Benson <[hidden email]> wrote:
> >
> > Hello,
> > After having received some support from a "feeler" email, I would like to
> > propose the formal vote to migrate this Commons component to Git for
> > version control. This vote will be open for at least 72 hours, or until
> > April 22, 2018 @ 16:00 UTC.
> >
> > Thanks,
> > Matt
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> --
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Matt Benson-3
I'm not clear on how the options differ and haven't found much that seems
helpful in several minutes of web searching.

Matt

On Thu, Apr 19, 2018 at 3:52 PM, Matt Sicker <[hidden email]> wrote:

> That’s actually a good question. The two options are still available. While
> I think it would be pretty cool if all of Commons was on GitBox for
> convenience, I’m pretty sure all the new repos have still been git-wip
>
> On Thu, Apr 19, 2018 at 15:15, Ralph Goers <[hidden email]>
> wrote:
>
> > Is this vote for Git or Gitbox or is there any difference these days?
> >
> > Ralph
> >
> > > On Apr 19, 2018, at 8:46 AM, Matt Benson <[hidden email]> wrote:
> > >
> > > Hello,
> > > After having received some support from a "feeler" email, I would like
> to
> > > propose the formal vote to migrate this Commons component to Git for
> > > version control. This vote will be open for at least 72 hours, or until
> > > April 22, 2018 @ 16:00 UTC.
> > >
> > > Thanks,
> > > Matt
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> > --
> Matt Sicker <[hidden email]>
>
Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

sebb-2-2
On 19 April 2018 at 22:09, Matt Benson <[hidden email]> wrote:
> I'm not clear on how the options differ and haven't found much that seems
> helpful in several minutes of web searching.

https://git.apache.org has some info, but I suspect it is getting out of date.
For example, the create a repo link leads to https://infra.apache.org/git.html
which says:
NOTE: This form is for the legacy git-wip service. New podlings should
NOT use this form for repositories. Please refer to the GitBox service
instead.

There's also some info here:
https://reference.apache.org/pmc/github

> Matt
>
> On Thu, Apr 19, 2018 at 3:52 PM, Matt Sicker <[hidden email]> wrote:
>
>> That’s actually a good question. The two options are still available. While
>> I think it would be pretty cool if all of Commons was on GitBox for
>> convenience, I’m pretty sure all the new repos have still been git-wip
>>
>> On Thu, Apr 19, 2018 at 15:15, Ralph Goers <[hidden email]>
>> wrote:
>>
>> > Is this vote for Git or Gitbox or is there any difference these days?
>> >
>> > Ralph
>> >
>> > > On Apr 19, 2018, at 8:46 AM, Matt Benson <[hidden email]> wrote:
>> > >
>> > > Hello,
>> > > After having received some support from a "feeler" email, I would like
>> to
>> > > propose the formal vote to migrate this Commons component to Git for
>> > > version control. This vote will be open for at least 72 hours, or until
>> > > April 22, 2018 @ 16:00 UTC.
>> > >
>> > > Thanks,
>> > > Matt
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
>> >
>> > --
>> Matt Sicker <[hidden email]>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Matt Benson-3
Thanks for these, Seb. Not sure I really consider myself fully edified yet,
but I know how to go to Infra HipChat when I have time for a thorough
explanation. :)

Matt

On Thu, Apr 19, 2018 at 4:16 PM, sebb <[hidden email]> wrote:

> On 19 April 2018 at 22:09, Matt Benson <[hidden email]> wrote:
> > I'm not clear on how the options differ and haven't found much that seems
> > helpful in several minutes of web searching.
>
> https://git.apache.org has some info, but I suspect it is getting out of
> date.
> For example, the create a repo link leads to https://infra.apache.org/git.
> html
> which says:
> NOTE: This form is for the legacy git-wip service. New podlings should
> NOT use this form for repositories. Please refer to the GitBox service
> instead.
>
> There's also some info here:
> https://reference.apache.org/pmc/github
>
> > Matt
> >
> > On Thu, Apr 19, 2018 at 3:52 PM, Matt Sicker <[hidden email]> wrote:
> >
> >> That’s actually a good question. The two options are still available.
> While
> >> I think it would be pretty cool if all of Commons was on GitBox for
> >> convenience, I’m pretty sure all the new repos have still been git-wip
> >>
> >> On Thu, Apr 19, 2018 at 15:15, Ralph Goers <[hidden email]>
> >> wrote:
> >>
> >> > Is this vote for Git or Gitbox or is there any difference these days?
> >> >
> >> > Ralph
> >> >
> >> > > On Apr 19, 2018, at 8:46 AM, Matt Benson <[hidden email]>
> wrote:
> >> > >
> >> > > Hello,
> >> > > After having received some support from a "feeler" email, I would
> like
> >> to
> >> > > propose the formal vote to migrate this Commons component to Git for
> >> > > version control. This vote will be open for at least 72 hours, or
> until
> >> > > April 22, 2018 @ 16:00 UTC.
> >> > >
> >> > > Thanks,
> >> > > Matt
> >> >
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: [hidden email]
> >> > For additional commands, e-mail: [hidden email]
> >> >
> >> > --
> >> Matt Sicker <[hidden email]>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Matt Sicker
The simple difference is that GitBox repositories are primarily used via
GitHub (you can enable issues, pull requests, etc.) while the other Git
style are primarily used via apache.org (Jira, patches, GitHub read-only
mirror, allows PRs, etc.).

On 19 April 2018 at 16:23, Matt Benson <[hidden email]> wrote:

> Thanks for these, Seb. Not sure I really consider myself fully edified yet,
> but I know how to go to Infra HipChat when I have time for a thorough
> explanation. :)
>
> Matt
>
> On Thu, Apr 19, 2018 at 4:16 PM, sebb <[hidden email]> wrote:
>
> > On 19 April 2018 at 22:09, Matt Benson <[hidden email]> wrote:
> > > I'm not clear on how the options differ and haven't found much that
> seems
> > > helpful in several minutes of web searching.
> >
> > https://git.apache.org has some info, but I suspect it is getting out of
> > date.
> > For example, the create a repo link leads to
> https://infra.apache.org/git.
> > html
> > which says:
> > NOTE: This form is for the legacy git-wip service. New podlings should
> > NOT use this form for repositories. Please refer to the GitBox service
> > instead.
> >
> > There's also some info here:
> > https://reference.apache.org/pmc/github
> >
> > > Matt
> > >
> > > On Thu, Apr 19, 2018 at 3:52 PM, Matt Sicker <[hidden email]> wrote:
> > >
> > >> That’s actually a good question. The two options are still available.
> > While
> > >> I think it would be pretty cool if all of Commons was on GitBox for
> > >> convenience, I’m pretty sure all the new repos have still been git-wip
> > >>
> > >> On Thu, Apr 19, 2018 at 15:15, Ralph Goers <
> [hidden email]>
> > >> wrote:
> > >>
> > >> > Is this vote for Git or Gitbox or is there any difference these
> days?
> > >> >
> > >> > Ralph
> > >> >
> > >> > > On Apr 19, 2018, at 8:46 AM, Matt Benson <[hidden email]>
> > wrote:
> > >> > >
> > >> > > Hello,
> > >> > > After having received some support from a "feeler" email, I would
> > like
> > >> to
> > >> > > propose the formal vote to migrate this Commons component to Git
> for
> > >> > > version control. This vote will be open for at least 72 hours, or
> > until
> > >> > > April 22, 2018 @ 16:00 UTC.
> > >> > >
> > >> > > Thanks,
> > >> > > Matt
> > >> >
> > >> >
> > >> >
> > >> > ------------------------------------------------------------
> ---------
> > >> > To unsubscribe, e-mail: [hidden email]
> > >> > For additional commands, e-mail: [hidden email]
> > >> >
> > >> > --
> > >> Matt Sicker <[hidden email]>
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>



--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Matt Benson-2
I don't know that I have a preference for any one component, but I do agree
that it might be a positive move across Commons to aim for homogeneity in
this regard for future migrations. If someone wants to start a vote on
*that*, I'd be glad to wait for its outcome before pulling the trigger on
[weaver].

Matt

On Thu, Apr 19, 2018 at 4:46 PM, Matt Sicker <[hidden email]> wrote:

> The simple difference is that GitBox repositories are primarily used via
> GitHub (you can enable issues, pull requests, etc.) while the other Git
> style are primarily used via apache.org (Jira, patches, GitHub read-only
> mirror, allows PRs, etc.).
>
> On 19 April 2018 at 16:23, Matt Benson <[hidden email]> wrote:
>
> > Thanks for these, Seb. Not sure I really consider myself fully edified
> yet,
> > but I know how to go to Infra HipChat when I have time for a thorough
> > explanation. :)
> >
> > Matt
> >
> > On Thu, Apr 19, 2018 at 4:16 PM, sebb <[hidden email]> wrote:
> >
> > > On 19 April 2018 at 22:09, Matt Benson <[hidden email]> wrote:
> > > > I'm not clear on how the options differ and haven't found much that
> > seems
> > > > helpful in several minutes of web searching.
> > >
> > > https://git.apache.org has some info, but I suspect it is getting out
> of
> > > date.
> > > For example, the create a repo link leads to
> > https://infra.apache.org/git.
> > > html
> > > which says:
> > > NOTE: This form is for the legacy git-wip service. New podlings should
> > > NOT use this form for repositories. Please refer to the GitBox service
> > > instead.
> > >
> > > There's also some info here:
> > > https://reference.apache.org/pmc/github
> > >
> > > > Matt
> > > >
> > > > On Thu, Apr 19, 2018 at 3:52 PM, Matt Sicker <[hidden email]>
> wrote:
> > > >
> > > >> That’s actually a good question. The two options are still
> available.
> > > While
> > > >> I think it would be pretty cool if all of Commons was on GitBox for
> > > >> convenience, I’m pretty sure all the new repos have still been
> git-wip
> > > >>
> > > >> On Thu, Apr 19, 2018 at 15:15, Ralph Goers <
> > [hidden email]>
> > > >> wrote:
> > > >>
> > > >> > Is this vote for Git or Gitbox or is there any difference these
> > days?
> > > >> >
> > > >> > Ralph
> > > >> >
> > > >> > > On Apr 19, 2018, at 8:46 AM, Matt Benson <[hidden email]>
> > > wrote:
> > > >> > >
> > > >> > > Hello,
> > > >> > > After having received some support from a "feeler" email, I
> would
> > > like
> > > >> to
> > > >> > > propose the formal vote to migrate this Commons component to Git
> > for
> > > >> > > version control. This vote will be open for at least 72 hours,
> or
> > > until
> > > >> > > April 22, 2018 @ 16:00 UTC.
> > > >> > >
> > > >> > > Thanks,
> > > >> > > Matt
> > > >> >
> > > >> >
> > > >> >
> > > >> > ------------------------------------------------------------
> > ---------
> > > >> > To unsubscribe, e-mail: [hidden email]
> > > >> > For additional commands, e-mail: [hidden email]
> > > >> >
> > > >> > --
> > > >> Matt Sicker <[hidden email]>
> > > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
>
>
>
> --
> Matt Sicker <[hidden email]>
>
Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

sebb-2-2
I suggest asking Infra whether they are both going to be supported longer term.


On 19 April 2018 at 23:01, Matt Benson <[hidden email]> wrote:

> I don't know that I have a preference for any one component, but I do agree
> that it might be a positive move across Commons to aim for homogeneity in
> this regard for future migrations. If someone wants to start a vote on
> *that*, I'd be glad to wait for its outcome before pulling the trigger on
> [weaver].
>
> Matt
>
> On Thu, Apr 19, 2018 at 4:46 PM, Matt Sicker <[hidden email]> wrote:
>
>> The simple difference is that GitBox repositories are primarily used via
>> GitHub (you can enable issues, pull requests, etc.) while the other Git
>> style are primarily used via apache.org (Jira, patches, GitHub read-only
>> mirror, allows PRs, etc.).
>>
>> On 19 April 2018 at 16:23, Matt Benson <[hidden email]> wrote:
>>
>> > Thanks for these, Seb. Not sure I really consider myself fully edified
>> yet,
>> > but I know how to go to Infra HipChat when I have time for a thorough
>> > explanation. :)
>> >
>> > Matt
>> >
>> > On Thu, Apr 19, 2018 at 4:16 PM, sebb <[hidden email]> wrote:
>> >
>> > > On 19 April 2018 at 22:09, Matt Benson <[hidden email]> wrote:
>> > > > I'm not clear on how the options differ and haven't found much that
>> > seems
>> > > > helpful in several minutes of web searching.
>> > >
>> > > https://git.apache.org has some info, but I suspect it is getting out
>> of
>> > > date.
>> > > For example, the create a repo link leads to
>> > https://infra.apache.org/git.
>> > > html
>> > > which says:
>> > > NOTE: This form is for the legacy git-wip service. New podlings should
>> > > NOT use this form for repositories. Please refer to the GitBox service
>> > > instead.
>> > >
>> > > There's also some info here:
>> > > https://reference.apache.org/pmc/github
>> > >
>> > > > Matt
>> > > >
>> > > > On Thu, Apr 19, 2018 at 3:52 PM, Matt Sicker <[hidden email]>
>> wrote:
>> > > >
>> > > >> That’s actually a good question. The two options are still
>> available.
>> > > While
>> > > >> I think it would be pretty cool if all of Commons was on GitBox for
>> > > >> convenience, I’m pretty sure all the new repos have still been
>> git-wip
>> > > >>
>> > > >> On Thu, Apr 19, 2018 at 15:15, Ralph Goers <
>> > [hidden email]>
>> > > >> wrote:
>> > > >>
>> > > >> > Is this vote for Git or Gitbox or is there any difference these
>> > days?
>> > > >> >
>> > > >> > Ralph
>> > > >> >
>> > > >> > > On Apr 19, 2018, at 8:46 AM, Matt Benson <[hidden email]>
>> > > wrote:
>> > > >> > >
>> > > >> > > Hello,
>> > > >> > > After having received some support from a "feeler" email, I
>> would
>> > > like
>> > > >> to
>> > > >> > > propose the formal vote to migrate this Commons component to Git
>> > for
>> > > >> > > version control. This vote will be open for at least 72 hours,
>> or
>> > > until
>> > > >> > > April 22, 2018 @ 16:00 UTC.
>> > > >> > >
>> > > >> > > Thanks,
>> > > >> > > Matt
>> > > >> >
>> > > >> >
>> > > >> >
>> > > >> > ------------------------------------------------------------
>> > ---------
>> > > >> > To unsubscribe, e-mail: [hidden email]
>> > > >> > For additional commands, e-mail: [hidden email]
>> > > >> >
>> > > >> > --
>> > > >> Matt Sicker <[hidden email]>
>> > > >>
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: [hidden email]
>> > > For additional commands, e-mail: [hidden email]
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Matt Sicker <[hidden email]>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Emmanuel Bourg-3
Le 20/04/2018 à 00:12, sebb a écrit :
> I suggest asking Infra whether they are both going to be supported longer term.

FWIW when I migrated JEXL I had no other choice than using Gitbox. I'm
not sure Infra still accepts new git-wip repositories.

Emmanuel Bourg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Romain Manni-Bucau
Gitbox is easier to use with github which makes contribs easier. Otherwise
you dont see much difference as a git user.

Le 20 avr. 2018 00:16, "Emmanuel Bourg" <[hidden email]> a écrit :

> Le 20/04/2018 à 00:12, sebb a écrit :
> > I suggest asking Infra whether they are both going to be supported
> longer term.
>
> FWIW when I migrated JEXL I had no other choice than using Gitbox. I'm
> not sure Infra still accepts new git-wip repositories.
>
> Emmanuel Bourg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Matt Benson-2
As Emmanuel suggested, Daniel Gruno confirmed for me that "git-wip is
slowly being deprecated." So the answer to the question initially posed by
Ralph would seem in fact to be gitbox.

Thanks,
Matt

On Thu, Apr 19, 2018 at 11:57 PM, Romain Manni-Bucau <[hidden email]>
wrote:

> Gitbox is easier to use with github which makes contribs easier. Otherwise
> you dont see much difference as a git user.
>
> Le 20 avr. 2018 00:16, "Emmanuel Bourg" <[hidden email]> a écrit :
>
> > Le 20/04/2018 à 00:12, sebb a écrit :
> > > I suggest asking Infra whether they are both going to be supported
> > longer term.
> >
> > FWIW when I migrated JEXL I had no other choice than using Gitbox. I'm
> > not sure Infra still accepts new git-wip repositories.
> >
> > Emmanuel Bourg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Matt Sicker
Wow, us "legacy" projects really need to keep up to date with these
requirements. GitBox, no CMS (I think we're using svnpubsub everywhere, but
this could also use gitpubsub with an asf-site branch), etc.

On 20 April 2018 at 10:13, Matt Benson <[hidden email]> wrote:

> As Emmanuel suggested, Daniel Gruno confirmed for me that "git-wip is
> slowly being deprecated." So the answer to the question initially posed by
> Ralph would seem in fact to be gitbox.
>
> Thanks,
> Matt
>
> On Thu, Apr 19, 2018 at 11:57 PM, Romain Manni-Bucau <
> [hidden email]>
> wrote:
>
> > Gitbox is easier to use with github which makes contribs easier.
> Otherwise
> > you dont see much difference as a git user.
> >
> > Le 20 avr. 2018 00:16, "Emmanuel Bourg" <[hidden email]> a écrit :
> >
> > > Le 20/04/2018 à 00:12, sebb a écrit :
> > > > I suggest asking Infra whether they are both going to be supported
> > > longer term.
> > >
> > > FWIW when I migrated JEXL I had no other choice than using Gitbox. I'm
> > > not sure Infra still accepts new git-wip repositories.
> > >
> > > Emmanuel Bourg
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
>



--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Oliver Heger-3


Am 20.04.2018 um 19:08 schrieb Matt Sicker:
> Wow, us "legacy" projects really need to keep up to date with these
> requirements. GitBox, no CMS (I think we're using svnpubsub everywhere, but
> this could also use gitpubsub with an asf-site branch), etc.

Would it reduce overhead if we converted multiple components at once?

I would like to move with [configuration] to git, but have hesitated so
far because I do not know the process in detail and what the effort is.

Oliver

>
> On 20 April 2018 at 10:13, Matt Benson <[hidden email]> wrote:
>
>> As Emmanuel suggested, Daniel Gruno confirmed for me that "git-wip is
>> slowly being deprecated." So the answer to the question initially posed by
>> Ralph would seem in fact to be gitbox.
>>
>> Thanks,
>> Matt
>>
>> On Thu, Apr 19, 2018 at 11:57 PM, Romain Manni-Bucau <
>> [hidden email]>
>> wrote:
>>
>>> Gitbox is easier to use with github which makes contribs easier.
>> Otherwise
>>> you dont see much difference as a git user.
>>>
>>> Le 20 avr. 2018 00:16, "Emmanuel Bourg" <[hidden email]> a écrit :
>>>
>>>> Le 20/04/2018 à 00:12, sebb a écrit :
>>>>> I suggest asking Infra whether they are both going to be supported
>>>> longer term.
>>>>
>>>> FWIW when I migrated JEXL I had no other choice than using Gitbox. I'm
>>>> not sure Infra still accepts new git-wip repositories.
>>>>
>>>> Emmanuel Bourg
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

12