You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Matt Benson <mb...@apache.org> on 2018/04/19 15:46:54 UTC
[VOTE] Migrate Commons Weaver to Git
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
Re: [VOTE] Migrate Commons Weaver to Git
Posted by Matt Sicker <bo...@gmail.com>.
+1 (non-binding)
On 19 April 2018 at 10:47, Matt Benson <mb...@apache.org> wrote:
> On Thu, Apr 19, 2018 at 10:46 AM, Matt Benson <mb...@apache.org> 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 <bo...@gmail.com>
Re: [VOTE] Migrate Commons Weaver to Git
Posted by Matt Benson <mb...@apache.org>.
On Thu, Apr 19, 2018 at 10:46 AM, Matt Benson <mb...@apache.org> 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
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by sebb <se...@gmail.com>.
On 22 April 2018 at 17:58, Matt Sicker <bo...@gmail.com> wrote:
> We can easily convert the existing git repos over to gitbox. The only
> changes we'll need to make here will be updating the SCM URLs (both in
> pom.xml and the current site) to point to the proper subdomain. Existing
> clones from git-wip-us.a.o or elsewhere can be updated by changing the
> remote url (git remote set-url origin <url>).
There are other places where the GIT urls are used.
DOAPs are OK because they are now all under commons/cms-site/trunk/doap in SVN.
But some websites may mention the URLs directly rather than using the
POM defines.
There are various CI bots (Jenkins, Buildbot) that will need to be updated.
> As for subversion repos, we may have to get some updates added to the
> authors.txt for apache. Last time I tried to convert a commons repo, I
> found some usernames of deceased people who were never added to
> authors.txt. That would ensure the cleanest history migration.
>
> The alternative is to just take the github mirror of an svn repo and use
> that as the basis for the new git repo. I don't think that preserves all
> the author history properly, however, due to differences between svn and
> git metadata (hence the authors.txt file).
>
>
> On 22 April 2018 at 11:39, Gary Gregory <ga...@gmail.com> wrote:
>
>> On Sun, Apr 22, 2018 at 10:34 AM, Matt Benson <mb...@apache.org> wrote:
>>
>> > Shall we call a second vote to move all components to gitbox, then?
>> >
>>
>> That would be fine with me. My understanding of such a VOTE is that we
>> would not saddle ourselves with a ton of work ASAP but indicates our intent
>> and future plans. We would likely still migrate components one or a few at
>> a time as volunteers have time.
>>
>> Gary
>>
>>
>> >
>> > Matt
>> >
>> > On Sun, Apr 22, 2018 at 11:31 AM, Gary Gregory <ga...@gmail.com>
>> > wrote:
>> >
>> > > On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger <
>> > > oliver.heger@oliver-heger.de
>> > > > wrote:
>> > >
>> > > >
>> > > >
>> > > > Am 21.04.2018 um 22:31 schrieb Matt Sicker:
>> > > > > I opened an infra ticket [1] to find out our options here. My
>> > preferred
>> > > > > option would be to migrate all of Commons over to gitbox for
>> > > consistency.
>> > > >
>> > > > Many thanks, Matt!
>> > > >
>> > > > I would be +1 for a mass conversion, too. I think, nobody has
>> > objections
>> > > > against Git any more. The reason why some components still use SVN is
>> > > > just inertia.
>> > > >
>> > >
>> > > Moving all to Git will also allow us to review and clean up our release
>> > > procedure documentation.
>> > >
>> > > It just feels like A LOT of busy work because we have so many
>> components.
>> > >
>> > > Gary
>> > >
>> > >
>> > > > Oliver
>> > > >
>> > > > >
>> > > > > [1]: https://issues.apache.org/jira/browse/INFRA-16413
>> > > > >
>> > > > > On 21 April 2018 at 12:23, Matt Benson <mb...@apache.org> wrote:
>> > > > >
>> > > > >> On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins <ch...@gmail.com>
>> > > wrote:
>> > > > >>
>> > > > >>>
>> > > > >>>
>> > > > >>>> On Apr 21, 2018, at 10:20 AM, Oliver Heger <
>> > > > >> oliver.heger@oliver-heger.de>
>> > > > >>> wrote:
>> > > > >>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>>> 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.
>> > > > >>>
>> > > > >>> If we wanted to do a (mildly) mass effort, I would be on board
>> with
>> > > > >>> helping.
>> > > > >>>
>> > > > >>>
>> > > > >> Noble as that is (no sarcasm intended), is there any reason that
>> > > > migrating
>> > > > >> components *en masse* would be easier or otherwise preferable to
>> > doing
>> > > > so
>> > > > >> "piecemeal"?
>> > > > >>
>> > > > >> Matt
>> > > > >>
>> > > > >>
>> > > > >> -Rob
>> > > > >>>
>> > > > >>>>
>> > > > >>>> Oliver
>> > > > >>>>
>> > > > >>>>>
>> > > > >>>>> On 20 April 2018 at 10:13, Matt Benson <gu...@gmail.com>
>> > > 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 <
>> > > > >>>>>> rmannibucau@gmail.com>
>> > > > >>>>>> 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" <eb...@apache.org>
>> 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: dev-unsubscribe@commons.apache.org
>> > > > >>>>>>>> For additional commands, e-mail:
>> dev-help@commons.apache.org
>> > > > >>>>>>>>
>> > > > >>>>>>>>
>> > > > >>>>>>>
>> > > > >>>>>>
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>
>> > > > >>>> ------------------------------------------------------------
>> > > ---------
>> > > > >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > <mailto:
>> > > > >>> dev-unsubscribe@commons.apache.org>
>> > > > >>>> For additional commands, e-mail: dev-help@commons.apache.org
>> > > <mailto:
>> > > > >>> dev-help@commons.apache.org>
>> > > > >>>
>> > > > >>
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > > > ------------------------------------------------------------
>> ---------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > > > For additional commands, e-mail: dev-help@commons.apache.org
>> > > >
>> > > >
>> > >
>> >
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Sicker <bo...@gmail.com>.
We can easily convert the existing git repos over to gitbox. The only
changes we'll need to make here will be updating the SCM URLs (both in
pom.xml and the current site) to point to the proper subdomain. Existing
clones from git-wip-us.a.o or elsewhere can be updated by changing the
remote url (git remote set-url origin <url>).
As for subversion repos, we may have to get some updates added to the
authors.txt for apache. Last time I tried to convert a commons repo, I
found some usernames of deceased people who were never added to
authors.txt. That would ensure the cleanest history migration.
The alternative is to just take the github mirror of an svn repo and use
that as the basis for the new git repo. I don't think that preserves all
the author history properly, however, due to differences between svn and
git metadata (hence the authors.txt file).
On 22 April 2018 at 11:39, Gary Gregory <ga...@gmail.com> wrote:
> On Sun, Apr 22, 2018 at 10:34 AM, Matt Benson <mb...@apache.org> wrote:
>
> > Shall we call a second vote to move all components to gitbox, then?
> >
>
> That would be fine with me. My understanding of such a VOTE is that we
> would not saddle ourselves with a ton of work ASAP but indicates our intent
> and future plans. We would likely still migrate components one or a few at
> a time as volunteers have time.
>
> Gary
>
>
> >
> > Matt
> >
> > On Sun, Apr 22, 2018 at 11:31 AM, Gary Gregory <ga...@gmail.com>
> > wrote:
> >
> > > On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger <
> > > oliver.heger@oliver-heger.de
> > > > wrote:
> > >
> > > >
> > > >
> > > > Am 21.04.2018 um 22:31 schrieb Matt Sicker:
> > > > > I opened an infra ticket [1] to find out our options here. My
> > preferred
> > > > > option would be to migrate all of Commons over to gitbox for
> > > consistency.
> > > >
> > > > Many thanks, Matt!
> > > >
> > > > I would be +1 for a mass conversion, too. I think, nobody has
> > objections
> > > > against Git any more. The reason why some components still use SVN is
> > > > just inertia.
> > > >
> > >
> > > Moving all to Git will also allow us to review and clean up our release
> > > procedure documentation.
> > >
> > > It just feels like A LOT of busy work because we have so many
> components.
> > >
> > > Gary
> > >
> > >
> > > > Oliver
> > > >
> > > > >
> > > > > [1]: https://issues.apache.org/jira/browse/INFRA-16413
> > > > >
> > > > > On 21 April 2018 at 12:23, Matt Benson <mb...@apache.org> wrote:
> > > > >
> > > > >> On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins <ch...@gmail.com>
> > > wrote:
> > > > >>
> > > > >>>
> > > > >>>
> > > > >>>> On Apr 21, 2018, at 10:20 AM, Oliver Heger <
> > > > >> oliver.heger@oliver-heger.de>
> > > > >>> wrote:
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> 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.
> > > > >>>
> > > > >>> If we wanted to do a (mildly) mass effort, I would be on board
> with
> > > > >>> helping.
> > > > >>>
> > > > >>>
> > > > >> Noble as that is (no sarcasm intended), is there any reason that
> > > > migrating
> > > > >> components *en masse* would be easier or otherwise preferable to
> > doing
> > > > so
> > > > >> "piecemeal"?
> > > > >>
> > > > >> Matt
> > > > >>
> > > > >>
> > > > >> -Rob
> > > > >>>
> > > > >>>>
> > > > >>>> Oliver
> > > > >>>>
> > > > >>>>>
> > > > >>>>> On 20 April 2018 at 10:13, Matt Benson <gu...@gmail.com>
> > > 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 <
> > > > >>>>>> rmannibucau@gmail.com>
> > > > >>>>>> 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" <eb...@apache.org>
> 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: dev-unsubscribe@commons.apache.org
> > > > >>>>>>>> For additional commands, e-mail:
> dev-help@commons.apache.org
> > > > >>>>>>>>
> > > > >>>>>>>>
> > > > >>>>>>>
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>> ------------------------------------------------------------
> > > ---------
> > > > >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > <mailto:
> > > > >>> dev-unsubscribe@commons.apache.org>
> > > > >>>> For additional commands, e-mail: dev-help@commons.apache.org
> > > <mailto:
> > > > >>> dev-help@commons.apache.org>
> > > > >>>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > >
> > > >
> > >
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Gary Gregory <ga...@gmail.com>.
On Sun, Apr 22, 2018 at 10:34 AM, Matt Benson <mb...@apache.org> wrote:
> Shall we call a second vote to move all components to gitbox, then?
>
That would be fine with me. My understanding of such a VOTE is that we
would not saddle ourselves with a ton of work ASAP but indicates our intent
and future plans. We would likely still migrate components one or a few at
a time as volunteers have time.
Gary
>
> Matt
>
> On Sun, Apr 22, 2018 at 11:31 AM, Gary Gregory <ga...@gmail.com>
> wrote:
>
> > On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger <
> > oliver.heger@oliver-heger.de
> > > wrote:
> >
> > >
> > >
> > > Am 21.04.2018 um 22:31 schrieb Matt Sicker:
> > > > I opened an infra ticket [1] to find out our options here. My
> preferred
> > > > option would be to migrate all of Commons over to gitbox for
> > consistency.
> > >
> > > Many thanks, Matt!
> > >
> > > I would be +1 for a mass conversion, too. I think, nobody has
> objections
> > > against Git any more. The reason why some components still use SVN is
> > > just inertia.
> > >
> >
> > Moving all to Git will also allow us to review and clean up our release
> > procedure documentation.
> >
> > It just feels like A LOT of busy work because we have so many components.
> >
> > Gary
> >
> >
> > > Oliver
> > >
> > > >
> > > > [1]: https://issues.apache.org/jira/browse/INFRA-16413
> > > >
> > > > On 21 April 2018 at 12:23, Matt Benson <mb...@apache.org> wrote:
> > > >
> > > >> On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins <ch...@gmail.com>
> > wrote:
> > > >>
> > > >>>
> > > >>>
> > > >>>> On Apr 21, 2018, at 10:20 AM, Oliver Heger <
> > > >> oliver.heger@oliver-heger.de>
> > > >>> wrote:
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> 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.
> > > >>>
> > > >>> If we wanted to do a (mildly) mass effort, I would be on board with
> > > >>> helping.
> > > >>>
> > > >>>
> > > >> Noble as that is (no sarcasm intended), is there any reason that
> > > migrating
> > > >> components *en masse* would be easier or otherwise preferable to
> doing
> > > so
> > > >> "piecemeal"?
> > > >>
> > > >> Matt
> > > >>
> > > >>
> > > >> -Rob
> > > >>>
> > > >>>>
> > > >>>> Oliver
> > > >>>>
> > > >>>>>
> > > >>>>> On 20 April 2018 at 10:13, Matt Benson <gu...@gmail.com>
> > 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 <
> > > >>>>>> rmannibucau@gmail.com>
> > > >>>>>> 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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> > > >>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>
> > > >>>> ------------------------------------------------------------
> > ---------
> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> <mailto:
> > > >>> dev-unsubscribe@commons.apache.org>
> > > >>>> For additional commands, e-mail: dev-help@commons.apache.org
> > <mailto:
> > > >>> dev-help@commons.apache.org>
> > > >>>
> > > >>
> > > >
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> >
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Benson <mb...@apache.org>.
Shall we call a second vote to move all components to gitbox, then?
Matt
On Sun, Apr 22, 2018 at 11:31 AM, Gary Gregory <ga...@gmail.com>
wrote:
> On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger <
> oliver.heger@oliver-heger.de
> > wrote:
>
> >
> >
> > Am 21.04.2018 um 22:31 schrieb Matt Sicker:
> > > I opened an infra ticket [1] to find out our options here. My preferred
> > > option would be to migrate all of Commons over to gitbox for
> consistency.
> >
> > Many thanks, Matt!
> >
> > I would be +1 for a mass conversion, too. I think, nobody has objections
> > against Git any more. The reason why some components still use SVN is
> > just inertia.
> >
>
> Moving all to Git will also allow us to review and clean up our release
> procedure documentation.
>
> It just feels like A LOT of busy work because we have so many components.
>
> Gary
>
>
> > Oliver
> >
> > >
> > > [1]: https://issues.apache.org/jira/browse/INFRA-16413
> > >
> > > On 21 April 2018 at 12:23, Matt Benson <mb...@apache.org> wrote:
> > >
> > >> On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins <ch...@gmail.com>
> wrote:
> > >>
> > >>>
> > >>>
> > >>>> On Apr 21, 2018, at 10:20 AM, Oliver Heger <
> > >> oliver.heger@oliver-heger.de>
> > >>> wrote:
> > >>>>
> > >>>>
> > >>>>
> > >>>> 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.
> > >>>
> > >>> If we wanted to do a (mildly) mass effort, I would be on board with
> > >>> helping.
> > >>>
> > >>>
> > >> Noble as that is (no sarcasm intended), is there any reason that
> > migrating
> > >> components *en masse* would be easier or otherwise preferable to doing
> > so
> > >> "piecemeal"?
> > >>
> > >> Matt
> > >>
> > >>
> > >> -Rob
> > >>>
> > >>>>
> > >>>> Oliver
> > >>>>
> > >>>>>
> > >>>>> On 20 April 2018 at 10:13, Matt Benson <gu...@gmail.com>
> 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 <
> > >>>>>> rmannibucau@gmail.com>
> > >>>>>> 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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> > >>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>> ------------------------------------------------------------
> ---------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org <mailto:
> > >>> dev-unsubscribe@commons.apache.org>
> > >>>> For additional commands, e-mail: dev-help@commons.apache.org
> <mailto:
> > >>> dev-help@commons.apache.org>
> > >>>
> > >>
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Gary Gregory <ga...@gmail.com>.
On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger <oliver.heger@oliver-heger.de
> wrote:
>
>
> Am 21.04.2018 um 22:31 schrieb Matt Sicker:
> > I opened an infra ticket [1] to find out our options here. My preferred
> > option would be to migrate all of Commons over to gitbox for consistency.
>
> Many thanks, Matt!
>
> I would be +1 for a mass conversion, too. I think, nobody has objections
> against Git any more. The reason why some components still use SVN is
> just inertia.
>
Moving all to Git will also allow us to review and clean up our release
procedure documentation.
It just feels like A LOT of busy work because we have so many components.
Gary
> Oliver
>
> >
> > [1]: https://issues.apache.org/jira/browse/INFRA-16413
> >
> > On 21 April 2018 at 12:23, Matt Benson <mb...@apache.org> wrote:
> >
> >> On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins <ch...@gmail.com> wrote:
> >>
> >>>
> >>>
> >>>> On Apr 21, 2018, at 10:20 AM, Oliver Heger <
> >> oliver.heger@oliver-heger.de>
> >>> wrote:
> >>>>
> >>>>
> >>>>
> >>>> 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.
> >>>
> >>> If we wanted to do a (mildly) mass effort, I would be on board with
> >>> helping.
> >>>
> >>>
> >> Noble as that is (no sarcasm intended), is there any reason that
> migrating
> >> components *en masse* would be easier or otherwise preferable to doing
> so
> >> "piecemeal"?
> >>
> >> Matt
> >>
> >>
> >> -Rob
> >>>
> >>>>
> >>>> Oliver
> >>>>
> >>>>>
> >>>>> On 20 April 2018 at 10:13, Matt Benson <gu...@gmail.com> 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 <
> >>>>>> rmannibucau@gmail.com>
> >>>>>> 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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> >>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org <mailto:
> >>> dev-unsubscribe@commons.apache.org>
> >>>> For additional commands, e-mail: dev-help@commons.apache.org <mailto:
> >>> dev-help@commons.apache.org>
> >>>
> >>
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Oliver Heger <ol...@oliver-heger.de>.
Am 21.04.2018 um 22:31 schrieb Matt Sicker:
> I opened an infra ticket [1] to find out our options here. My preferred
> option would be to migrate all of Commons over to gitbox for consistency.
Many thanks, Matt!
I would be +1 for a mass conversion, too. I think, nobody has objections
against Git any more. The reason why some components still use SVN is
just inertia.
Oliver
>
> [1]: https://issues.apache.org/jira/browse/INFRA-16413
>
> On 21 April 2018 at 12:23, Matt Benson <mb...@apache.org> wrote:
>
>> On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins <ch...@gmail.com> wrote:
>>
>>>
>>>
>>>> On Apr 21, 2018, at 10:20 AM, Oliver Heger <
>> oliver.heger@oliver-heger.de>
>>> wrote:
>>>>
>>>>
>>>>
>>>> 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.
>>>
>>> If we wanted to do a (mildly) mass effort, I would be on board with
>>> helping.
>>>
>>>
>> Noble as that is (no sarcasm intended), is there any reason that migrating
>> components *en masse* would be easier or otherwise preferable to doing so
>> "piecemeal"?
>>
>> Matt
>>
>>
>> -Rob
>>>
>>>>
>>>> Oliver
>>>>
>>>>>
>>>>> On 20 April 2018 at 10:13, Matt Benson <gu...@gmail.com> 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 <
>>>>>> rmannibucau@gmail.com>
>>>>>> 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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org <mailto:
>>> dev-unsubscribe@commons.apache.org>
>>>> For additional commands, e-mail: dev-help@commons.apache.org <mailto:
>>> dev-help@commons.apache.org>
>>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Sicker <bo...@gmail.com>.
I opened an infra ticket [1] to find out our options here. My preferred
option would be to migrate all of Commons over to gitbox for consistency.
[1]: https://issues.apache.org/jira/browse/INFRA-16413
On 21 April 2018 at 12:23, Matt Benson <mb...@apache.org> wrote:
> On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins <ch...@gmail.com> wrote:
>
> >
> >
> > > On Apr 21, 2018, at 10:20 AM, Oliver Heger <
> oliver.heger@oliver-heger.de>
> > wrote:
> > >
> > >
> > >
> > > 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.
> >
> > If we wanted to do a (mildly) mass effort, I would be on board with
> > helping.
> >
> >
> Noble as that is (no sarcasm intended), is there any reason that migrating
> components *en masse* would be easier or otherwise preferable to doing so
> "piecemeal"?
>
> Matt
>
>
> -Rob
> >
> > >
> > > Oliver
> > >
> > >>
> > >> On 20 April 2018 at 10:13, Matt Benson <gu...@gmail.com> 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 <
> > >>> rmannibucau@gmail.com>
> > >>> 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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> > >>>>> For additional commands, e-mail: dev-help@commons.apache.org
> > >>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org <mailto:
> > dev-unsubscribe@commons.apache.org>
> > > For additional commands, e-mail: dev-help@commons.apache.org <mailto:
> > dev-help@commons.apache.org>
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Benson <mb...@apache.org>.
On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins <ch...@gmail.com> wrote:
>
>
> > On Apr 21, 2018, at 10:20 AM, Oliver Heger <ol...@oliver-heger.de>
> wrote:
> >
> >
> >
> > 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.
>
> If we wanted to do a (mildly) mass effort, I would be on board with
> helping.
>
>
Noble as that is (no sarcasm intended), is there any reason that migrating
components *en masse* would be easier or otherwise preferable to doing so
"piecemeal"?
Matt
-Rob
>
> >
> > Oliver
> >
> >>
> >> On 20 April 2018 at 10:13, Matt Benson <gu...@gmail.com> 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 <
> >>> rmannibucau@gmail.com>
> >>> 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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> >>>>> For additional commands, e-mail: dev-help@commons.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org <mailto:
> dev-unsubscribe@commons.apache.org>
> > For additional commands, e-mail: dev-help@commons.apache.org <mailto:
> dev-help@commons.apache.org>
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Rob Tompkins <ch...@gmail.com>.
> On Apr 21, 2018, at 10:20 AM, Oliver Heger <ol...@oliver-heger.de> wrote:
>
>
>
> 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.
If we wanted to do a (mildly) mass effort, I would be on board with helping.
-Rob
>
> Oliver
>
>>
>> On 20 April 2018 at 10:13, Matt Benson <gu...@gmail.com> 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 <
>>> rmannibucau@gmail.com>
>>> 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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org <ma...@commons.apache.org>
> For additional commands, e-mail: dev-help@commons.apache.org <ma...@commons.apache.org>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Oliver Heger <ol...@oliver-heger.de>.
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 <gu...@gmail.com> 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 <
>> rmannibucau@gmail.com>
>> 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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Sicker <bo...@gmail.com>.
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 <gu...@gmail.com> 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 <
> rmannibucau@gmail.com>
> 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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Benson <gu...@gmail.com>.
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 <rm...@gmail.com>
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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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" <eb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Emmanuel Bourg <eb...@apache.org>.
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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by sebb <se...@gmail.com>.
I suggest asking Infra whether they are both going to be supported longer term.
On 19 April 2018 at 23:01, Matt Benson <gu...@gmail.com> 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 <bo...@gmail.com> 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 <mb...@apache.org> 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 <se...@gmail.com> wrote:
>> >
>> > > On 19 April 2018 at 22:09, Matt Benson <mb...@apache.org> 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 <bo...@gmail.com>
>> 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 <
>> > ralph.goers@dslextreme.com>
>> > > >> 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 <mb...@apache.org>
>> > > 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: dev-unsubscribe@commons.apache.org
>> > > >> > For additional commands, e-mail: dev-help@commons.apache.org
>> > > >> >
>> > > >> > --
>> > > >> Matt Sicker <bo...@gmail.com>
>> > > >>
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > > For additional commands, e-mail: dev-help@commons.apache.org
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Benson <gu...@gmail.com>.
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 <bo...@gmail.com> 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 <mb...@apache.org> 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 <se...@gmail.com> wrote:
> >
> > > On 19 April 2018 at 22:09, Matt Benson <mb...@apache.org> 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 <bo...@gmail.com>
> 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 <
> > ralph.goers@dslextreme.com>
> > > >> 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 <mb...@apache.org>
> > > 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: dev-unsubscribe@commons.apache.org
> > > >> > For additional commands, e-mail: dev-help@commons.apache.org
> > > >> >
> > > >> > --
> > > >> Matt Sicker <bo...@gmail.com>
> > > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> >
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Sicker <bo...@gmail.com>.
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 <mb...@apache.org> 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 <se...@gmail.com> wrote:
>
> > On 19 April 2018 at 22:09, Matt Benson <mb...@apache.org> 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 <bo...@gmail.com> 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 <
> ralph.goers@dslextreme.com>
> > >> 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 <mb...@apache.org>
> > 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: dev-unsubscribe@commons.apache.org
> > >> > For additional commands, e-mail: dev-help@commons.apache.org
> > >> >
> > >> > --
> > >> Matt Sicker <bo...@gmail.com>
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Benson <mb...@apache.org>.
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 <se...@gmail.com> wrote:
> On 19 April 2018 at 22:09, Matt Benson <mb...@apache.org> 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 <bo...@gmail.com> 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 <ra...@dslextreme.com>
> >> 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 <mb...@apache.org>
> 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: dev-unsubscribe@commons.apache.org
> >> > For additional commands, e-mail: dev-help@commons.apache.org
> >> >
> >> > --
> >> Matt Sicker <bo...@gmail.com>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by sebb <se...@gmail.com>.
On 19 April 2018 at 22:09, Matt Benson <mb...@apache.org> 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 <bo...@gmail.com> 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 <ra...@dslextreme.com>
>> 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 <mb...@apache.org> 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: dev-unsubscribe@commons.apache.org
>> > For additional commands, e-mail: dev-help@commons.apache.org
>> >
>> > --
>> Matt Sicker <bo...@gmail.com>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Benson <mb...@apache.org>.
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 <bo...@gmail.com> 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 <ra...@dslextreme.com>
> 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 <mb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> > --
> Matt Sicker <bo...@gmail.com>
>
Re: Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Matt Sicker <bo...@gmail.com>.
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 <ra...@dslextreme.com>
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 <mb...@apache.org> 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: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
> --
Matt Sicker <bo...@gmail.com>
Discuss [VOTE] Migrate Commons Weaver to Git
Posted by Ralph Goers <ra...@dslextreme.com>.
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 <mb...@apache.org> 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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Migrate Commons Weaver to Git
Posted by Gary Gregory <ga...@gmail.com>.
+1 (binding)
Gary
On Thu, Apr 19, 2018 at 9:46 AM, Matt Benson <mb...@apache.org> 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
>
Re: [VOTE] Migrate Commons Weaver to Git
Posted by Rob Tompkins <ch...@gmail.com>.
> On Apr 19, 2018, at 11:46 AM, Matt Benson <mb...@apache.org> 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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Migrate Commons Weaver to Git
Posted by Romain Manni-Bucau <rm...@gmail.com>.
+1
Le 19 avr. 2018 20:17, "Pascal Schumacher" <pa...@gmx.net> 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: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [VOTE] Migrate Commons Weaver to Git
Posted by Pascal Schumacher <pa...@gmx.net>.
+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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org