Migrate all MyFaces projects to Git

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

Migrate all MyFaces projects to Git

Dennis Kieselhorst
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Thomas Andraschko-4
+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Bernd Bohmann
From my side a big

+1

I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.

Regards

Bernd

Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Grant Smith-4
+1 

Couldn't agree more.

Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.

On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
From my side a big

+1

I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.

Regards

Bernd

Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Leonardo Uribe
+1

Change the release process is a pain, but I agree there are some benefits moving to git.

But when I see here:

https://github.com/apache/myfaces

It says:

mirrored from git://git.apache.org/myfaces.git

But I have never checked where that file is or how to change it.

Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.

regards,

Leonardo Uribe


Virus-free. www.avast.com

2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
+1 

Couldn't agree more.

Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.

On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
From my side a big

+1

I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.

Regards

Bernd

Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Bernd Bohmann-3
Hello

I think the changes will be not so complicated. The deltaspike pom looks nice :-) 
If someone talks about git-flow process i'm out.

Regards

Bernd

On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
+1

Change the release process is a pain, but I agree there are some benefits moving to git.

But when I see here:

https://github.com/apache/myfaces

It says:

mirrored from git://git.apache.org/myfaces.git

But I have never checked where that file is or how to change it.

Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.

regards,

Leonardo Uribe


Virus-free. www.avast.com

2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
+1 

Couldn't agree more.

Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.

On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
From my side a big

+1

I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.

Regards

Bernd

Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Kito Mann
+1

Wha's wrong with GitFlow?

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <[hidden email]> wrote:
Hello

I think the changes will be not so complicated. The deltaspike pom looks nice :-) 
If someone talks about git-flow process i'm out.

Regards

Bernd

On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
+1

Change the release process is a pain, but I agree there are some benefits moving to git.

But when I see here:

https://github.com/apache/myfaces

It says:

mirrored from git://git.apache.org/myfaces.git

But I have never checked where that file is or how to change it.

Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.

regards,

Leonardo Uribe


Virus-free. www.avast.com

2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
+1 

Couldn't agree more.

Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.

On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
From my side a big

+1

I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.

Regards

Bernd

Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis





Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Bernd Bohmann-3
Until now, nobody could explain me the real technical improvement of GitFlow. 
We are talking about using git and not GitFlow. Git does not require GitFlow 

At Apache we are only using process as much as needed and not as possible!
And my personal advice is:
Start with a model as simple as possible.

Regards

Bernd

 


 


On Wed, Apr 19, 2017 at 12:57 PM, Kito Mann <[hidden email]> wrote:
+1

Wha's wrong with GitFlow?

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
<a href="tel:(203)%20998-0403" value="+12039980403" target="_blank">+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <[hidden email]> wrote:
Hello

I think the changes will be not so complicated. The deltaspike pom looks nice :-) 
If someone talks about git-flow process i'm out.

Regards

Bernd

On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
+1

Change the release process is a pain, but I agree there are some benefits moving to git.

But when I see here:

https://github.com/apache/myfaces

It says:

mirrored from git://git.apache.org/myfaces.git

But I have never checked where that file is or how to change it.

Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.

regards,

Leonardo Uribe


Virus-free. www.avast.com

2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
+1 

Couldn't agree more.

Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.

On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
From my side a big

+1

I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.

Regards

Bernd

Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis






Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Kito Mann
Hello Bernd,

I like GitFlow for coordinating with multiple developers. However, if everyone is sending pull requests anyway, it's not quite as useful. It makes sense when you have multiple developers that are committing to a "develop" branch and provides guidelines for working with master for new releases and hot fixes.

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Wed, Apr 19, 2017 at 8:38 AM, Bernd Bohmann <[hidden email]> wrote:
Until now, nobody could explain me the real technical improvement of GitFlow. 
We are talking about using git and not GitFlow. Git does not require GitFlow 

At Apache we are only using process as much as needed and not as possible!
And my personal advice is:
Start with a model as simple as possible.

Regards

Bernd

 


 


On Wed, Apr 19, 2017 at 12:57 PM, Kito Mann <[hidden email]> wrote:
+1

Wha's wrong with GitFlow?

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
<a href="tel:(203)%20998-0403" value="+12039980403" target="_blank">+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <[hidden email]> wrote:
Hello

I think the changes will be not so complicated. The deltaspike pom looks nice :-) 
If someone talks about git-flow process i'm out.

Regards

Bernd

On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
+1

Change the release process is a pain, but I agree there are some benefits moving to git.

But when I see here:

https://github.com/apache/myfaces

It says:

mirrored from git://git.apache.org/myfaces.git

But I have never checked where that file is or how to change it.

Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.

regards,

Leonardo Uribe


Virus-free. www.avast.com

2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
+1 

Couldn't agree more.

Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.

On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
From my side a big

+1

I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.

Regards

Bernd

Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis







Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Gerhard Petracek-2
hi @ all,

just fyi:
[1] works very well for ds since the beginning.

regards,
gerhard




2017-04-19 14:45 GMT+02:00 Kito Mann <[hidden email]>:
Hello Bernd,

I like GitFlow for coordinating with multiple developers. However, if everyone is sending pull requests anyway, it's not quite as useful. It makes sense when you have multiple developers that are committing to a "develop" branch and provides guidelines for working with master for new releases and hot fixes.

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
<a href="tel:(203)%20998-0403" value="+12039980403" target="_blank">+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Wed, Apr 19, 2017 at 8:38 AM, Bernd Bohmann <[hidden email]> wrote:
Until now, nobody could explain me the real technical improvement of GitFlow. 
We are talking about using git and not GitFlow. Git does not require GitFlow 

At Apache we are only using process as much as needed and not as possible!
And my personal advice is:
Start with a model as simple as possible.

Regards

Bernd

 


 


On Wed, Apr 19, 2017 at 12:57 PM, Kito Mann <[hidden email]> wrote:
+1

Wha's wrong with GitFlow?

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
<a href="tel:(203)%20998-0403" value="+12039980403" target="_blank">+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <[hidden email]> wrote:
Hello

I think the changes will be not so complicated. The deltaspike pom looks nice :-) 
If someone talks about git-flow process i'm out.

Regards

Bernd

On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
+1

Change the release process is a pain, but I agree there are some benefits moving to git.

But when I see here:

https://github.com/apache/myfaces

It says:

mirrored from git://git.apache.org/myfaces.git

But I have never checked where that file is or how to change it.

Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.

regards,

Leonardo Uribe


Virus-free. www.avast.com

2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
+1 

Couldn't agree more.

Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.

On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
From my side a big

+1

I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.

Regards

Bernd

Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
Hi,

have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun contributing there than attaching patches to JIRA issues.

We could start with Trinidad and Tobago to avoid conflicts with the 2.3
release.

Cheers
Dennis








Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Mark Struberg
In reply to this post by Kito Mann
gitflow is pure pita ;)
It basically only works for companies where you have a single manager who decides what goes in and what not.

But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but is just a fancy name for a development process with an explicit build-branch and a build-master.

+0 on moving to GIT.
SVN works good enough imo, but GIT ofc also would work.

LIeGrue,
strub

> Am 19.04.2017 um 12:57 schrieb Kito Mann <[hidden email]>:
>
> +1
>
> Wha's wrong with GitFlow?
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> +1 203-998-0403
>
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
> On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <[hidden email]> wrote:
> Hello
>
> I think the changes will be not so complicated. The deltaspike pom looks nice :-)
> If someone talks about git-flow process i'm out.
>
> Regards
>
> Bernd
>
> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
> +1
>
> Change the release process is a pain, but I agree there are some benefits moving to git.
>
> But when I see here:
>
> https://github.com/apache/myfaces
>
> It says:
>
> mirrored from git://git.apache.org/myfaces.git
>
> But I have never checked where that file is or how to change it.
>
> Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.
>
> regards,
>
> Leonardo Uribe
>
>
> Virus-free. www.avast.com
>
> 2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
> +1
>
> Couldn't agree more.
>
> Grant Smith - V.P. Information Technology
> Marathon Computer Systems, LLC.
>
> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
> From my side a big
>
> +1
>
> I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.
>
> Regards
>
> Bernd
>
> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
> +0
> I usually just work on MF core and there it doesn't make much difference.
>
> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
> Hi,
>
> have you ever thought of migrating to Git? I see more and more Apache
> projects moving. In the past SVN or Git didn't make any difference to me
> but now I'm thinking that as an Open Source project you need to be
> present on GitHub to get Pull Requests from the community. It's much
> more fun contributing there than attaching patches to JIRA issues.
>
> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> release.
>
> Cheers
> Dennis
>
>
>
>
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Bernd Bohmann-3
Thanks Mark

gitflow is not solving any technical problem. It's just more complicated and it's looks good from a high level perspective.

Regards

Bernd 

On Thu, Apr 20, 2017 at 2:02 PM, Mark Struberg <[hidden email]> wrote:
gitflow is pure pita ;)
It basically only works for companies where you have a single manager who decides what goes in and what not.

But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but is just a fancy name for a development process with an explicit build-branch and a build-master.

+0 on moving to GIT.
SVN works good enough imo, but GIT ofc also would work.

LIeGrue,
strub

> Am 19.04.2017 um 12:57 schrieb Kito Mann <[hidden email]>:
>
> +1
>
> Wha's wrong with GitFlow?
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> <a href="tel:%2B1%20203-998-0403" value="+12039980403">+1 203-998-0403
>
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
> On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <[hidden email]> wrote:
> Hello
>
> I think the changes will be not so complicated. The deltaspike pom looks nice :-)
> If someone talks about git-flow process i'm out.
>
> Regards
>
> Bernd
>
> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
> +1
>
> Change the release process is a pain, but I agree there are some benefits moving to git.
>
> But when I see here:
>
> https://github.com/apache/myfaces
>
> It says:
>
> mirrored from git://git.apache.org/myfaces.git
>
> But I have never checked where that file is or how to change it.
>
> Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.
>
> regards,
>
> Leonardo Uribe
>
>
>       Virus-free. www.avast.com
>
> 2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
> +1
>
> Couldn't agree more.
>
> Grant Smith - V.P. Information Technology
> Marathon Computer Systems, LLC.
>
> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
> From my side a big
>
> +1
>
> I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.
>
> Regards
>
> Bernd
>
> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
> +0
> I usually just work on MF core and there it doesn't make much difference.
>
> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
> Hi,
>
> have you ever thought of migrating to Git? I see more and more Apache
> projects moving. In the past SVN or Git didn't make any difference to me
> but now I'm thinking that as an Open Source project you need to be
> present on GitHub to get Pull Requests from the community. It's much
> more fun contributing there than attaching patches to JIRA issues.
>
> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> release.
>
> Cheers
> Dennis
>
>
>
>
>


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Bill Lucy
I prefer working with GIT, and agree with the points already made in this thread about its benefits.  I'm not sure how much pain a meaningful transition will cause - from that perspective, starting with the components is a great idea.

+1

Regards,
Bill

On Thu, Apr 20, 2017 at 8:24 AM, Bernd Bohmann <[hidden email]> wrote:
Thanks Mark

gitflow is not solving any technical problem. It's just more complicated and it's looks good from a high level perspective.

Regards

Bernd 

On Thu, Apr 20, 2017 at 2:02 PM, Mark Struberg <[hidden email]> wrote:
gitflow is pure pita ;)
It basically only works for companies where you have a single manager who decides what goes in and what not.

But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but is just a fancy name for a development process with an explicit build-branch and a build-master.

+0 on moving to GIT.
SVN works good enough imo, but GIT ofc also would work.

LIeGrue,
strub

> Am 19.04.2017 um 12:57 schrieb Kito Mann <[hidden email]>:
>
> +1
>
> Wha's wrong with GitFlow?
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> <a href="tel:%2B1%20203-998-0403" value="+12039980403" target="_blank">+1 203-998-0403
>
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
> On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <[hidden email]> wrote:
> Hello
>
> I think the changes will be not so complicated. The deltaspike pom looks nice :-)
> If someone talks about git-flow process i'm out.
>
> Regards
>
> Bernd
>
> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
> +1
>
> Change the release process is a pain, but I agree there are some benefits moving to git.
>
> But when I see here:
>
> https://github.com/apache/myfaces
>
> It says:
>
> mirrored from git://git.apache.org/myfaces.git
>
> But I have never checked where that file is or how to change it.
>
> Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.
>
> regards,
>
> Leonardo Uribe
>
>
>       Virus-free. www.avast.com
>
> 2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
> +1
>
> Couldn't agree more.
>
> Grant Smith - V.P. Information Technology
> Marathon Computer Systems, LLC.
>
> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
> From my side a big
>
> +1
>
> I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.
>
> Regards
>
> Bernd
>
> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
> +0
> I usually just work on MF core and there it doesn't make much difference.
>
> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
> Hi,
>
> have you ever thought of migrating to Git? I see more and more Apache
> projects moving. In the past SVN or Git didn't make any difference to me
> but now I'm thinking that as an Open Source project you need to be
> present on GitHub to get Pull Requests from the community. It's much
> more fun contributing there than attaching patches to JIRA issues.
>
> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> release.
>
> Cheers
> Dennis
>
>
>
>
>



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Kito Mann
In reply to this post by Mark Struberg
Ah, this may be why it's worked for me -- smaller projects with defined release cycles.

Anyway, I never meant to imply that git == git flow. We will need some sort of process, though, and the DeltaSpike one seems like a good place to start.

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg <[hidden email]> wrote:
gitflow is pure pita ;)
It basically only works for companies where you have a single manager who decides what goes in and what not.

But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but is just a fancy name for a development process with an explicit build-branch and a build-master.

+0 on moving to GIT.
SVN works good enough imo, but GIT ofc also would work.

LIeGrue,
strub

> Am 19.04.2017 um 12:57 schrieb Kito Mann <[hidden email]>:
>
> +1
>
> Wha's wrong with GitFlow?
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> <a href="tel:%2B1%20203-998-0403" value="+12039980403">+1 203-998-0403
>
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
> On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <[hidden email]> wrote:
> Hello
>
> I think the changes will be not so complicated. The deltaspike pom looks nice :-)
> If someone talks about git-flow process i'm out.
>
> Regards
>
> Bernd
>
> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
> +1
>
> Change the release process is a pain, but I agree there are some benefits moving to git.
>
> But when I see here:
>
> https://github.com/apache/myfaces
>
> It says:
>
> mirrored from git://git.apache.org/myfaces.git
>
> But I have never checked where that file is or how to change it.
>
> Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.
>
> regards,
>
> Leonardo Uribe
>
>
>       Virus-free. www.avast.com
>
> 2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
> +1
>
> Couldn't agree more.
>
> Grant Smith - V.P. Information Technology
> Marathon Computer Systems, LLC.
>
> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
> From my side a big
>
> +1
>
> I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.
>
> Regards
>
> Bernd
>
> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
> +0
> I usually just work on MF core and there it doesn't make much difference.
>
> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
> Hi,
>
> have you ever thought of migrating to Git? I see more and more Apache
> projects moving. In the past SVN or Git didn't make any difference to me
> but now I'm thinking that as an Open Source project you need to be
> present on GitHub to get Pull Requests from the community. It's much
> more fun contributing there than attaching patches to JIRA issues.
>
> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> release.
>
> Cheers
> Dennis
>
>
>
>
>


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Bernd Bohmann-3
Ok

we have some agreement about moving to git.
Now we should define some time line.
Any suggestions from the active subprojects?

Something like 
'I would like to move to git after blah blah release'
'I would like to move now'
'I would like to move in 2 weeks'
or whatever

I can support the migration to git.

Regards 

Bernd


 

On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann <[hidden email]> wrote:
Ah, this may be why it's worked for me -- smaller projects with defined release cycles.

Anyway, I never meant to imply that git == git flow. We will need some sort of process, though, and the DeltaSpike one seems like a good place to start.

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
<a href="tel:(203)%20998-0403" value="+12039980403" target="_blank">+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg <[hidden email]> wrote:
gitflow is pure pita ;)
It basically only works for companies where you have a single manager who decides what goes in and what not.

But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but is just a fancy name for a development process with an explicit build-branch and a build-master.

+0 on moving to GIT.
SVN works good enough imo, but GIT ofc also would work.

LIeGrue,
strub

> Am 19.04.2017 um 12:57 schrieb Kito Mann <[hidden email]>:
>
> +1
>
> Wha's wrong with GitFlow?
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> <a href="tel:%2B1%20203-998-0403" value="+12039980403" target="_blank">+1 203-998-0403
>
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
> On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <[hidden email]> wrote:
> Hello
>
> I think the changes will be not so complicated. The deltaspike pom looks nice :-)
> If someone talks about git-flow process i'm out.
>
> Regards
>
> Bernd
>
> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[hidden email]> wrote:
> +1
>
> Change the release process is a pain, but I agree there are some benefits moving to git.
>
> But when I see here:
>
> https://github.com/apache/myfaces
>
> It says:
>
> mirrored from git://git.apache.org/myfaces.git
>
> But I have never checked where that file is or how to change it.
>
> Looking in deltaspike, the svn repo only has the site (for the CMS) and the source code lives on git. If that so, we still need the svn, so I agree it is a good idea to move only some subprojects to git.
>
> regards,
>
> Leonardo Uribe
>
>
>       Virus-free. www.avast.com
>
> 2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]>:
> +1
>
> Couldn't agree more.
>
> Grant Smith - V.P. Information Technology
> Marathon Computer Systems, LLC.
>
> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <[hidden email]> wrote:
> From my side a big
>
> +1
>
> I'm still happy with subversion but for others the collaboration is easier and the project visibility a little bit better.
>
> Regards
>
> Bernd
>
> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <[hidden email]>:
> +0
> I usually just work on MF core and there it doesn't make much difference.
>
> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]>:
> Hi,
>
> have you ever thought of migrating to Git? I see more and more Apache
> projects moving. In the past SVN or Git didn't make any difference to me
> but now I'm thinking that as an Open Source project you need to be
> present on GitHub to get Pull Requests from the community. It's much
> more fun contributing there than attaching patches to JIRA issues.
>
> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> release.
>
> Cheers
> Dennis
>
>
>
>
>



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Udo Schnurpfeil-4
Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:

> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>  
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io <http://knowesis.io> -
>     fresh Web Components info
>     +1 203-998-0403 <tel:(203)%20998-0403>
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     <http://bit.ly/2kr0fWI>
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann <[hidden email]
>         <mailto:[hidden email]>>:
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>         <http://knowesis.io> - fresh Web Components info
>         > +1 203-998-0403 <tel:%2B1%20203-998-0403>
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>         <[hidden email]
>         <mailto:[hidden email]>> wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         <[hidden email] <mailto:[hidden email]>> wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/myfaces
>         <https://github.com/apache/myfaces>
>         >
>         > It says:
>         >
>         > mirrored from git://git.apache.org/myfaces.git
>         <http://git.apache.org/myfaces.git>
>         >
>         > But I have never checked where that file is or how to change it.
>         >
>         > Looking in deltaspike, the svn repo only has the site (for the
>         CMS) and the source code lives on git. If that so, we still need
>         the svn, so I agree it is a good idea to move only some
>         subprojects to git.
>         >
>         > regards,
>         >
>         > Leonardo Uribe
>         >
>         >
>         >       Virus-free. www.avast.com <http://www.avast.com>
>         >
>         > 2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]
>         <mailto:[hidden email]>>:
>         > +1
>         >
>         > Couldn't agree more.
>         >
>         > Grant Smith - V.P. Information Technology
>         > Marathon Computer Systems, LLC.
>         >
>         > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann
>         <[hidden email] <mailto:[hidden email]>>
>         wrote:
>         > From my side a big
>         >
>         > +1
>         >
>         > I'm still happy with subversion but for others the
>         collaboration is easier and the project visibility a little bit
>         better.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > Am 13.04.2017 09:41 schrieb "Thomas Andraschko"
>         <[hidden email] <mailto:[hidden email]>>:
>         > +0
>         > I usually just work on MF core and there it doesn't make much
>         difference.
>         >
>         > 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]
>         <mailto:[hidden email]>>:
>         > Hi,
>         >
>         > have you ever thought of migrating to Git? I see more and more
>         Apache
>         > projects moving. In the past SVN or Git didn't make any
>         difference to me
>         > but now I'm thinking that as an Open Source project you need to be
>         > present on GitHub to get Pull Requests from the community.
>         It's much
>         > more fun contributing there than attaching patches to JIRA issues.
>         >
>         > We could start with Trinidad and Tobago to avoid conflicts
>         with the 2.3
>         > release.
>         >
>         > Cheers
>         > Dennis
>         >
>         >
>         >
>         >
>         >
>
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Bernd Bohmann-3
for Trinidad as well

On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil <[hidden email]> wrote:
Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io <http://knowesis.io> -
>     fresh Web Components info
>     <a href="tel:%2B1%20203-998-0403" value="+12039980403">+1 203-998-0403 <tel:(203)%20998-0403>
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     <http://bit.ly/2kr0fWI>
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann <[hidden email]
>         <mailto:[hidden email]>>:
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>         <http://knowesis.io> - fresh Web Components info
>         > <a href="tel:%2B1%20203-998-0403" value="+12039980403">+1 203-998-0403 <tel:%2B1%20203-998-0403>
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>         <[hidden email]
>         <mailto:[hidden email]>> wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         <[hidden email] <mailto:[hidden email]>> wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/myfaces
>         <https://github.com/apache/myfaces>
>         >
>         > It says:
>         >
>         > mirrored from git://git.apache.org/myfaces.git
>         <http://git.apache.org/myfaces.git>
>         >
>         > But I have never checked where that file is or how to change it.
>         >
>         > Looking in deltaspike, the svn repo only has the site (for the
>         CMS) and the source code lives on git. If that so, we still need
>         the svn, so I agree it is a good idea to move only some
>         subprojects to git.
>         >
>         > regards,
>         >
>         > Leonardo Uribe
>         >
>         >
>         >       Virus-free. www.avast.com <http://www.avast.com>
>         >
>         > 2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]
>         <mailto:[hidden email]>>:
>         > +1
>         >
>         > Couldn't agree more.
>         >
>         > Grant Smith - V.P. Information Technology
>         > Marathon Computer Systems, LLC.
>         >
>         > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann
>         <[hidden email] <mailto:[hidden email]>>
>         wrote:
>         > From my side a big
>         >
>         > +1
>         >
>         > I'm still happy with subversion but for others the
>         collaboration is easier and the project visibility a little bit
>         better.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > Am 13.04.2017 09:41 schrieb "Thomas Andraschko"
>         <[hidden email] <mailto:[hidden email]>>:
>         > +0
>         > I usually just work on MF core and there it doesn't make much
>         difference.
>         >
>         > 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]
>         <mailto:[hidden email]>>:
>         > Hi,
>         >
>         > have you ever thought of migrating to Git? I see more and more
>         Apache
>         > projects moving. In the past SVN or Git didn't make any
>         difference to me
>         > but now I'm thinking that as an Open Source project you need to be
>         > present on GitHub to get Pull Requests from the community.
>         It's much
>         > more fun contributing there than attaching patches to JIRA issues.
>         >
>         > We could start with Trinidad and Tobago to avoid conflicts
>         with the 2.3
>         > release.
>         >
>         > Cheers
>         > Dennis
>         >
>         >
>         >
>         >
>         >
>
>
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Dora Rajappan
Is it github.com where you are going to migrate myfaces to?


On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann <[hidden email]> wrote:


for Trinidad as well

On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil <[hidden email]> wrote:
Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io <http://knowesis.io> -
>     fresh Web Components info
>     +1 203-998-0403 <tel:(203)%20998-0403>
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     <http://bit.ly/2kr0fWI>
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann <[hidden email]
>         <mailto:[hidden email]>> :
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>         <http://knowesis.io> - fresh Web Components info
>         > +1 203-998-0403 <tel:%2B1%20203-998-0403>
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>         <[hidden email]
>         <mailto:[hidden email]>> wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         <[hidden email] <mailto:[hidden email]>> wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/ myfaces
>         <https://github.com/apache/ myfaces>
>         >
>         > It says:
>         >
>         > mirrored from git://git.apache.org/myfaces. git
>         <http://git.apache.org/ myfaces.git>
>         >
>         > But I have never checked where that file is or how to change it.
>         >
>         > Looking in deltaspike, the svn repo only has the site (for the
>         CMS) and the source code lives on git. If that so, we still need
>         the svn, so I agree it is a good idea to move only some
>         subprojects to git.
>         >
>         > regards,
>         >
>         > Leonardo Uribe
>         >
>         >
>         >       Virus-free. www.avast.com <http://www.avast.com>
>         >
>         > 2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]
>         <mailto:[hidden email]>> :
>         > +1
>         >
>         > Couldn't agree more.
>         >
>         > Grant Smith - V.P. Information Technology
>         > Marathon Computer Systems, LLC.
>         >
>         > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann
>         <[hidden email] <mailto:[hidden email]>>
>         wrote:
>         > From my side a big
>         >
>         > +1
>         >
>         > I'm still happy with subversion but for others the
>         collaboration is easier and the project visibility a little bit
>         better.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > Am 13.04.2017 09:41 schrieb "Thomas Andraschko"
>         <[hidden email] <mailto:[hidden email]>>:
>         > +0
>         > I usually just work on MF core and there it doesn't make much
>         difference.
>         >
>         > 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]
>         <mailto:[hidden email]>>:
>         > Hi,
>         >
>         > have you ever thought of migrating to Git? I see more and more
>         Apache
>         > projects moving. In the past SVN or Git didn't make any
>         difference to me
>         > but now I'm thinking that as an Open Source project you need to be
>         > present on GitHub to get Pull Requests from the community.
>         It's much
>         > more fun contributing there than attaching patches to JIRA issues.
>         >
>         > We could start with Trinidad and Tobago to avoid conflicts
>         with the 2.3
>         > release.
>         >
>         > Cheers
>         > Dennis
>         >
>         >
>         >
>         >
>         >
>
>
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Bernd Bohmann-3
Hello Dora

this is not possible for apache projects


and


but there are readonly mirrors at https://github.com/apache

Regards

Bernd

On Thu, Jul 27, 2017 at 4:10 PM, Dora Rajappan <[hidden email]> wrote:
Is it github.com where you are going to migrate myfaces to?


On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann <[hidden email]> wrote:


for Trinidad as well

On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil <[hidden email]> wrote:
Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io <http://knowesis.io> -
>     fresh Web Components info
>     +1 203-998-0403 <tel:(203)%20998-0403>
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     <http://bit.ly/2kr0fWI>
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann <[hidden email]
>         <mailto:[hidden email]>> :
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>         <http://knowesis.io> - fresh Web Components info
>         > +1 203-998-0403 <tel:%2B1%20203-998-0403>
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>         <[hidden email]
>         <mailto:[hidden email]>> wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         <[hidden email] <mailto:[hidden email]>> wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/ myfaces
>         <https://github.com/apache/ myfaces>
>         >
>         > It says:
>         >
>         > mirrored from git://git.apache.org/myfaces. git
>         <http://git.apache.org/ myfaces.git>
>         >
>         > But I have never checked where that file is or how to change it.
>         >
>         > Looking in deltaspike, the svn repo only has the site (for the
>         CMS) and the source code lives on git. If that so, we still need
>         the svn, so I agree it is a good idea to move only some
>         subprojects to git.
>         >
>         > regards,
>         >
>         > Leonardo Uribe
>         >
>         >
>         >       Virus-free. www.avast.com <http://www.avast.com>
>         >
>         > 2017-04-17 11:40 GMT-05:00 Grant Smith <[hidden email]
>         <mailto:[hidden email]>> :
>         > +1
>         >
>         > Couldn't agree more.
>         >
>         > Grant Smith - V.P. Information Technology
>         > Marathon Computer Systems, LLC.
>         >
>         > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann
>         <[hidden email] <mailto:[hidden email]>>
>         wrote:
>         > From my side a big
>         >
>         > +1
>         >
>         > I'm still happy with subversion but for others the
>         collaboration is easier and the project visibility a little bit
>         better.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > Am 13.04.2017 09:41 schrieb "Thomas Andraschko"
>         <[hidden email] <mailto:[hidden email]>>:
>         > +0
>         > I usually just work on MF core and there it doesn't make much
>         difference.
>         >
>         > 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[hidden email]
>         <mailto:[hidden email]>>:
>         > Hi,
>         >
>         > have you ever thought of migrating to Git? I see more and more
>         Apache
>         > projects moving. In the past SVN or Git didn't make any
>         difference to me
>         > but now I'm thinking that as an Open Source project you need to be
>         > present on GitHub to get Pull Requests from the community.
>         It's much
>         > more fun contributing there than attaching patches to JIRA issues.
>         >
>         > We could start with Trinidad and Tobago to avoid conflicts
>         with the 2.3
>         > release.
>         >
>         > Cheers
>         > Dennis
>         >
>         >
>         >
>         >
>         >
>
>
>


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrate all MyFaces projects to Git

Dennis Kieselhorst-2
In reply to this post by Bernd Bohmann-3
In the meantime infra launched Gitbox with even better GitHub
integration, so in my view we should use that from the beginning:
http://gitbox.apache.org
12
Loading...