[RESULT] [VOTE] Migrate Commons Weaver to Git

Hello, With 4 binding +1 votes and no -1 votes, this vote has passed. Thanks, Matt On Thu, Apr 19, 2018 at 2:33 PM, Romain Manni-Bucau wrote: > +1 > > Le 19 avr. 2018 20:17, "Pascal Schumacher" a > écrit : > > > +1 > > > > Am 19.04.2018 um

Re: Discuss [VOTE] Migrate Commons Weaver to Git

On 22 April 2018 at 17:58, Matt Sicker 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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

On Sun, Apr 22, 2018 at 10:34 AM, Matt Benson 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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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 wrote: > On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger < > oliver.he...@oliver-heger.de > > wrote: > > > > > > > Am 21.04.2018 um 22:31 schrieb Matt

Re: Discuss [VOTE] Migrate Commons Weaver to Git

On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger 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. > >

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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 wrote: > On Sat, Apr 21, 2018,

Re: Discuss [VOTE] Migrate Commons Weaver to Git

On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins wrote: > > > > On Apr 21, 2018, at 10:20 AM, Oliver Heger > wrote: > > > > > > > > Am 20.04.2018 um 19:08 schrieb Matt Sicker: > >> Wow, us "legacy" projects really need to keep up to date with these >

Re: Discuss [VOTE] Migrate Commons Weaver to Git

> On Apr 21, 2018, at 10:20 AM, Oliver Heger > 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 >>

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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 wrote: > As Emmanuel

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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 wrote: > Gitbox is

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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" a écrit : > Le 20/04/2018 à 00:12, sebb a écrit : > > I suggest asking Infra whether they are both going to be

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

I suggest asking Infra whether they are both going to be supported longer term. On 19 April 2018 at 23:01, Matt Benson 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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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 wrote: > On 19 April 2018 at 22:09, Matt Benson

Re: Discuss [VOTE] Migrate Commons Weaver to Git

On 19 April 2018 at 22:09, Matt Benson 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

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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 wrote: > That’s actually a good question. The two options are still available. While > I think it would be

Re: Discuss [VOTE] Migrate Commons Weaver to Git

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 wrote: >

Discuss [VOTE] Migrate Commons Weaver to Git

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 wrote: > > Hello, > After having received some support from a "feeler" email, I would like to > propose the formal vote to migrate this Commons component

Re: [VOTE] Migrate Commons Weaver to Git

+1 Le 19 avr. 2018 20:17, "Pascal Schumacher" 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

Re: [VOTE] Migrate Commons Weaver to Git

+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

Re: [VOTE] Migrate Commons Weaver to Git

+1 (binding) Gary On Thu, Apr 19, 2018 at 9:46 AM, Matt Benson 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

Re: [VOTE] Migrate Commons Weaver to Git

> On Apr 19, 2018, at 11:46 AM, Matt Benson 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,

Re: [VOTE] Migrate Commons Weaver to Git

+1 (non-binding) On 19 April 2018 at 10:47, Matt Benson wrote: > On Thu, Apr 19, 2018 at 10:46 AM, Matt Benson wrote: > > > Hello, > > After having received some support from a "feeler" email, I would like to > > propose the formal vote to migrate this

Re: [VOTE] Migrate Commons Weaver to Git

On Thu, Apr 19, 2018 at 10:46 AM, Matt Benson 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

[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