I am not sure that this should come as a surprise or a real difference
in the current state.
It is possible for anyone to fork the project.
With git it could be easier to contribute back changes from this fork.
Of course, the code bases could diverge to a point where sharing updates
becomes too complex for both sides.
The real issue is whether there is sufficient dissatisfaction with the
current workflow and product direction for another community of
like-minded committers to build to a size capable of managing a "better"
fork.
Ron
On 21/04/2015 2:21 AM, Pierre Smits wrote:
Quoting:
We are also prepared to be assertive regarding this situation. If the
project
does not move to GIT then Brainfood is willing to participate in a
consortium of
organizations that will peer with each other to share updates to the master
branch for their local OFBiz repository. Such an arrangement will,
effectively,
result in a distributed master repository image.
Thanks Ean for the position of *Brainfood* in this position. It comes
across as 'Do it our way, or else'. You are free to make such statements
and when followed through there will be consequences. For all participating
in this project. One I can see standing out clearly is: no more
participation in/contribution from the employees of Brainfood and from the
other companies in that consortium back into the project.
If that is going to happen, I will say: 'I thank you for all the
contributions you did to the project'. And I will check in my sentiments at
the door. I do hope that if you do you also resign totally from this
project.
I rather have the community comes to its decision based on sound/valid
arguments, not (veiled) threats.
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Tue, Apr 21, 2015 at 2:08 AM, Ean Schuessler <[email protected]> wrote:
----- Original Message -----
From: "Jacques Le Roux" <[email protected]>
Subject: Re: move to git.
Like Adrian and mostly for the same reasons, I don't believe we need Git.
But there is one other major reason which has already been discussed in
the
other common ASF MLs. As Taher exulted, it's possible to create local
branches. So people are able to do a lot of work alone without
exchanging before
committing or submitting. It will certainly not help to have this
possibility.
I disagree. It is useful in many situations for OFBiz developers to create
a
local repository that is not globally shared. Some customers may even
require
such a situation for security or legal reasons.
Remember our recent discussion on the lack or core commits reviews.
With Git you end with commits bursts or big patches and it's then
hard to review and too late to share ideas.
So unlike Adrian, I'm even strongly against it. I will not hesitate to
use a -1
if necessary!
We are also prepared to be assertive regarding this situation. If the
project
does not move to GIT then Brainfood is willing to participate in a
consortium of
organizations that will peer with each other to share updates to the master
branch for their local OFBiz repository. Such an arrangement will,
effectively,
result in a distributed master repository image.
If anyone else is interested in such an arrangement please feel free to
speak
up and we can begin the planning process.
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
