move to git.

[Jacopo Cappellato-5]

On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]> wrote:

> It is no use, setting up an implementation plan when there is still a possibility people will reject it.

Ok, if this was your goal then it seems you got your answer: most people are inclined to Git (or will not object to it) but don't feel like it is actionable enough for a vote now: defining an implementation plan, so that people can understand how the actual every day work of the OFBiz community (committers, contributors and users) with Git will be, would definitely help.

Jacopo

[hans_bakker]

Then you better change your vote? At it is now, we cannot even create an
implementation proposal.
Hans

On 06/05/15 13:22, Jacopo Cappellato wrote:
> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]> wrote:
>
>> It is no use, setting up an implementation plan when there is still a possibility people will reject it.
> Ok, if this was your goal then it seems you got your answer: most people are inclined to Git (or will not object to it) but don't feel like it is actionable enough for a vote now: defining an implementation plan, so that people can understand how the actual every day work of the OFBiz community (committers, contributors and users) with Git will be, would definitely help.
>
> Jacopo

[Jacopo Cappellato-5]

My vote is clearly stated: propose a Git workflow that is inline with the ASF policies and that is good for the OFBiz project and I will vote positively.

Jacopo

On May 6, 2015, at 8:29 AM, Hans Bakker <[hidden email]> wrote:

> Then you better change your vote? At it is now, we cannot even create an implementation proposal.
> Hans
>
> On 06/05/15 13:22, Jacopo Cappellato wrote:
>> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]> wrote:
>>
>>> It is no use, setting up an implementation plan when there is still a possibility people will reject it.
>> Ok, if this was your goal then it seems you got your answer: most people are inclined to Git (or will not object to it) but don't feel like it is actionable enough for a vote now: defining an implementation plan, so that people can understand how the actual every day work of the OFBiz community (committers, contributors and users) with Git will be, would definitely help.
>>
>> Jacopo
>

[taher]

Hi Jacopo,

I am a bit of a noob on ASF policies. Is it possible to guide us on
resources to read to be able to draft any kind of proposal? Can you also
define what is an implementation plan? Is it like a document, a migration
process, a commit workflow, infrastructure or what exactly?

Taher Alkhateeb

On Wed, May 6, 2015 at 9:35 AM, Jacopo Cappellato <
[hidden email]> wrote:

> My vote is clearly stated: propose a Git workflow that is inline with the
> ASF policies and that is good for the OFBiz project and I will vote
> positively.
>
> Jacopo
>
> On May 6, 2015, at 8:29 AM, Hans Bakker <[hidden email]>
> wrote:
>
> > Then you better change your vote? At it is now, we cannot even create an
> implementation proposal.
> > Hans
> >
> > On 06/05/15 13:22, Jacopo Cappellato wrote:
> >> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]>
> wrote:
> >>
> >>> It is no use, setting up an implementation plan when there is still a
> possibility people will reject it.
> >> Ok, if this was your goal then it seems you got your answer: most
> people are inclined to Git (or will not object to it) but don't feel like
> it is actionable enough for a vote now: defining an implementation plan, so
> that people can understand how the actual every day work of the OFBiz
> community (committers, contributors and users) with Git will be, would
> definitely help.
> >>
> >> Jacopo
> >
>
>

[hans_bakker]

the workflow can be simple as is described in:
http://www.apache.org/dev/git.html

we could use this as the MVP (minimum viable product) so mimic basically
how people use SVN and then slowly take advantage of the possibilities
of GIT.

Regards,
Hans

On 06/05/15 13:35, Jacopo Cappellato wrote:

> My vote is clearly stated: propose a Git workflow that is inline with the ASF policies and that is good for the OFBiz project and I will vote positively.
>
> Jacopo
>
> On May 6, 2015, at 8:29 AM, Hans Bakker <[hidden email]> wrote:
>
>> Then you better change your vote? At it is now, we cannot even create an implementation proposal.
>> Hans
>>
>> On 06/05/15 13:22, Jacopo Cappellato wrote:
>>> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]> wrote:
>>>
>>>> It is no use, setting up an implementation plan when there is still a possibility people will reject it.
>>> Ok, if this was your goal then it seems you got your answer: most people are inclined to Git (or will not object to it) but don't feel like it is actionable enough for a vote now: defining an implementation plan, so that people can understand how the actual every day work of the OFBiz community (committers, contributors and users) with Git will be, would definitely help.
>>>
>>> Jacopo

[Jacopo Cappellato-5]

On May 6, 2015, at 8:46 AM, Hans Bakker <[hidden email]> wrote:

> the workflow can be simple as is described in:
> http://www.apache.org/dev/git.html
>
> we could use this as the MVP (minimum viable product) so mimic basically how people use SVN and then slowly take advantage of the possibilities of GIT.
>
> Regards,
> Hans

Hans,

I think you didn't spend enough time studying this material.
The document you are referencing is what we already have: the workflow and infrastructure described are already in place:
1) a writable svn repo
2) a read only mirror in git: git://git.apache.org/ofbiz.git
3) Jira to submit patches

Jacopo

>
> On 06/05/15 13:35, Jacopo Cappellato wrote:
>> My vote is clearly stated: propose a Git workflow that is inline with the ASF policies and that is good for the OFBiz project and I will vote positively.
>>
>> Jacopo
>>
>> On May 6, 2015, at 8:29 AM, Hans Bakker <[hidden email]> wrote:
>>
>>> Then you better change your vote? At it is now, we cannot even create an implementation proposal.
>>> Hans
>>>
>>> On 06/05/15 13:22, Jacopo Cappellato wrote:
>>>> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]> wrote:
>>>>
>>>>> It is no use, setting up an implementation plan when there is still a possibility people will reject it.
>>>> Ok, if this was your goal then it seems you got your answer: most people are inclined to Git (or will not object to it) but don't feel like it is actionable enough for a vote now: defining an implementation plan, so that people can understand how the actual every day work of the OFBiz community (committers, contributors and users) with Git will be, would definitely help.
>>>>
>>>> Jacopo
>

[hans_bakker]

When attached to a jira issue, then after approval (or no objection)
merging the patch into the master branch by a committer so difficult?

I am sorry, i do not see a problem here....

Regards,
Hans


On 06/05/15 13:53, Jacopo Cappellato wrote:

> On May 6, 2015, at 8:46 AM, Hans Bakker <[hidden email]> wrote:
>
>> the workflow can be simple as is described in:
>> http://www.apache.org/dev/git.html
>>
>> we could use this as the MVP (minimum viable product) so mimic basically how people use SVN and then slowly take advantage of the possibilities of GIT.
>>
>> Regards,
>> Hans
> Hans,
>
> I think you didn't spend enough time studying this material.
> The document you are referencing is what we already have: the workflow and infrastructure described are already in place:
> 1) a writable svn repo
> 2) a read only mirror in git: git://git.apache.org/ofbiz.git
> 3) Jira to submit patches
>
> Jacopo
>
>> On 06/05/15 13:35, Jacopo Cappellato wrote:
>>> My vote is clearly stated: propose a Git workflow that is inline with the ASF policies and that is good for the OFBiz project and I will vote positively.
>>>
>>> Jacopo
>>>
>>> On May 6, 2015, at 8:29 AM, Hans Bakker <[hidden email]> wrote:
>>>
>>>> Then you better change your vote? At it is now, we cannot even create an implementation proposal.
>>>> Hans
>>>>
>>>> On 06/05/15 13:22, Jacopo Cappellato wrote:
>>>>> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]> wrote:
>>>>>
>>>>>> It is no use, setting up an implementation plan when there is still a possibility people will reject it.
>>>>> Ok, if this was your goal then it seems you got your answer: most people are inclined to Git (or will not object to it) but don't feel like it is actionable enough for a vote now: defining an implementation plan, so that people can understand how the actual every day work of the OFBiz community (committers, contributors and users) with Git will be, would definitely help.
>>>>>
>>>>> Jacopo

[Jacopo Cappellato-5]

On May 6, 2015, at 8:43 AM, Taher Alkhateeb <[hidden email]> wrote:

> Hi Jacopo,
>
> I am a bit of a noob on ASF policies. Is it possible to guide us on
> resources to read to be able to draft any kind of proposal?

Hi Taher,

please read my previous messages on this subject because they contain some of the information you are looking for.
A good document to start with could be this:
http://www.apache.org/dev/writable-git
and also the documents referred to it.
Then also a review of the workflow adopted by other ASF project that switched to git may help to get some good ideas for OFBiz; the projects are the following:
https://git-wip-us.apache.org/repos/asf
By visiting their websites/wikis/mail archives we could gather useful information about their experience and lessons learned; what the ASF allows and what not.

> Can you also
> define what is an implementation plan? Is it like a document, a migration
> process, a commit workflow, infrastructure or what exactly?

I wouldn't use the term "implementation plan" that was introduced by Hans: what I am asking for is essentially a description of the commit workflow proposed for OFBiz. Then we could compare it to what we have now and discuss its pros and cons.

Jacopo

>
> Taher Alkhateeb
>
> On Wed, May 6, 2015 at 9:35 AM, Jacopo Cappellato <
> [hidden email]> wrote:
>
>> My vote is clearly stated: propose a Git workflow that is inline with the
>> ASF policies and that is good for the OFBiz project and I will vote
>> positively.
>>
>> Jacopo
>>
>> On May 6, 2015, at 8:29 AM, Hans Bakker <[hidden email]>
>> wrote:
>>
>>> Then you better change your vote? At it is now, we cannot even create an
>> implementation proposal.
>>> Hans
>>>
>>> On 06/05/15 13:22, Jacopo Cappellato wrote:
>>>> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]>
>> wrote:
>>>>
>>>>> It is no use, setting up an implementation plan when there is still a
>> possibility people will reject it.
>>>> Ok, if this was your goal then it seems you got your answer: most
>> people are inclined to Git (or will not object to it) but don't feel like
>> it is actionable enough for a vote now: defining an implementation plan, so
>> that people can understand how the actual every day work of the OFBiz
>> community (committers, contributors and users) with Git will be, would
>> definitely help.
>>>>
>>>> Jacopo
>>>
>>
>>

[Jacopo Cappellato-5]

On May 6, 2015, at 8:56 AM, Hans Bakker <[hidden email]> wrote:

> When attached to a jira issue, then after approval (or no objection) merging the patch into the master branch by a committer so difficult?

Did you read the document that you are asking us to refer to as your proposal for the firs Git MVP? The document describes a different workflow because it uses a read only Git repo: no merging on master branch will be possible.

Jacopo

>
> I am sorry, i do not see a problem here....
>
> Regards,
> Hans
>
>
> On 06/05/15 13:53, Jacopo Cappellato wrote:
>> On May 6, 2015, at 8:46 AM, Hans Bakker <[hidden email]> wrote:
>>
>>> the workflow can be simple as is described in:
>>> http://www.apache.org/dev/git.html
>>>
>>> we could use this as the MVP (minimum viable product) so mimic basically how people use SVN and then slowly take advantage of the possibilities of GIT.
>>>
>>> Regards,
>>> Hans
>> Hans,
>>
>> I think you didn't spend enough time studying this material.
>> The document you are referencing is what we already have: the workflow and infrastructure described are already in place:
>> 1) a writable svn repo
>> 2) a read only mirror in git: git://git.apache.org/ofbiz.git
>> 3) Jira to submit patches
>>
>> Jacopo
>>
>>> On 06/05/15 13:35, Jacopo Cappellato wrote:
>>>> My vote is clearly stated: propose a Git workflow that is inline with the ASF policies and that is good for the OFBiz project and I will vote positively.
>>>>
>>>> Jacopo
>>>>
>>>> On May 6, 2015, at 8:29 AM, Hans Bakker <[hidden email]> wrote:
>>>>
>>>>> Then you better change your vote? At it is now, we cannot even create an implementation proposal.
>>>>> Hans
>>>>>
>>>>> On 06/05/15 13:22, Jacopo Cappellato wrote:
>>>>>> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]> wrote:
>>>>>>
>>>>>>> It is no use, setting up an implementation plan when there is still a possibility people will reject it.
>>>>>> Ok, if this was your goal then it seems you got your answer: most people are inclined to Git (or will not object to it) but don't feel like it is actionable enough for a vote now: defining an implementation plan, so that people can understand how the actual every day work of the OFBiz community (committers, contributors and users) with Git will be, would definitely help.
>>>>>>
>>>>>> Jacopo
>

[hans_bakker]

Ok let first wait for the vote result seeing your comment at the -1 .

However then still we need a vote again after the proposal... if you
make it a -0.9 then when the proposal is agreed, no need for a vote.

for people who would like to help, there are plenty of GIT workflow
proposals in other Apache projects.

Regards,
Hans

On 06/05/15 14:05, Jacopo Cappellato wrote:

> On May 6, 2015, at 8:56 AM, Hans Bakker <[hidden email]> wrote:
>
>> When attached to a jira issue, then after approval (or no objection) merging the patch into the master branch by a committer so difficult?
> Did you read the document that you are asking us to refer to as your proposal for the firs Git MVP? The document describes a different workflow because it uses a read only Git repo: no merging on master branch will be possible.
>
> Jacopo
>
>> I am sorry, i do not see a problem here....
>>
>> Regards,
>> Hans
>>
>>
>> On 06/05/15 13:53, Jacopo Cappellato wrote:
>>> On May 6, 2015, at 8:46 AM, Hans Bakker <[hidden email]> wrote:
>>>
>>>> the workflow can be simple as is described in:
>>>> http://www.apache.org/dev/git.html
>>>>
>>>> we could use this as the MVP (minimum viable product) so mimic basically how people use SVN and then slowly take advantage of the possibilities of GIT.
>>>>
>>>> Regards,
>>>> Hans
>>> Hans,
>>>
>>> I think you didn't spend enough time studying this material.
>>> The document you are referencing is what we already have: the workflow and infrastructure described are already in place:
>>> 1) a writable svn repo
>>> 2) a read only mirror in git: git://git.apache.org/ofbiz.git
>>> 3) Jira to submit patches
>>>
>>> Jacopo
>>>
>>>> On 06/05/15 13:35, Jacopo Cappellato wrote:
>>>>> My vote is clearly stated: propose a Git workflow that is inline with the ASF policies and that is good for the OFBiz project and I will vote positively.
>>>>>
>>>>> Jacopo
>>>>>
>>>>> On May 6, 2015, at 8:29 AM, Hans Bakker <[hidden email]> wrote:
>>>>>
>>>>>> Then you better change your vote? At it is now, we cannot even create an implementation proposal.
>>>>>> Hans
>>>>>>
>>>>>> On 06/05/15 13:22, Jacopo Cappellato wrote:
>>>>>>> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]> wrote:
>>>>>>>
>>>>>>>> It is no use, setting up an implementation plan when there is still a possibility people will reject it.
>>>>>>> Ok, if this was your goal then it seems you got your answer: most people are inclined to Git (or will not object to it) but don't feel like it is actionable enough for a vote now: defining an implementation plan, so that people can understand how the actual every day work of the OFBiz community (committers, contributors and users) with Git will be, would definitely help.
>>>>>>>
>>>>>>> Jacopo

[Jacopo Cappellato-5]

On May 6, 2015, at 9:10 AM, Hans Bakker <[hidden email]> wrote:

> However then still we need a vote again after the proposal... if you make it a -0.9 then when the proposal is agreed, no need for a vote.

are you really considering the idea of doing such an important change for the community without a clear and strong indication from it (at least a few +1 votes from his committers)?

Jacopo

[Pierre Smits]

Consensus is always needed.

Best regards,

Pierre

Op woensdag 6 mei 2015 heeft Hans Bakker <[hidden email]>
het volgende geschreven:

> Ok let first wait for the vote result seeing your comment at the -1 .
>
> However then still we need a vote again after the proposal... if you make
> it a -0.9 then when the proposal is agreed, no need for a vote.
>
> for people who would like to help, there are plenty of GIT workflow
> proposals in other Apache projects.
>
> Regards,
> Hans
>
> On 06/05/15 14:05, Jacopo Cappellato wrote:
>
>> On May 6, 2015, at 8:56 AM, Hans Bakker <[hidden email]>
>> wrote:
>>
>>  When attached to a jira issue, then after approval (or no objection)
>>> merging the patch into the master branch by a committer so difficult?
>>>
>> Did you read the document that you are asking us to refer to as your
>> proposal for the firs Git MVP? The document describes a different workflow
>> because it uses a read only Git repo: no merging on master branch will be
>> possible.
>>
>> Jacopo
>>
>>  I am sorry, i do not see a problem here....
>>>
>>> Regards,
>>> Hans
>>>
>>>
>>> On 06/05/15 13:53, Jacopo Cappellato wrote:
>>>
>>>> On May 6, 2015, at 8:46 AM, Hans Bakker <[hidden email]>
>>>> wrote:
>>>>
>>>>  the workflow can be simple as is described in:
>>>>> http://www.apache.org/dev/git.html
>>>>>
>>>>> we could use this as the MVP (minimum viable product) so mimic
>>>>> basically how people use SVN and then slowly take advantage of the
>>>>> possibilities of GIT.
>>>>>
>>>>> Regards,
>>>>> Hans
>>>>>
>>>> Hans,
>>>>
>>>> I think you didn't spend enough time studying this material.
>>>> The document you are referencing is what we already have: the workflow
>>>> and infrastructure described are already in place:
>>>> 1) a writable svn repo
>>>> 2) a read only mirror in git: git://git.apache.org/ofbiz.git
>>>> 3) Jira to submit patches
>>>>
>>>> Jacopo
>>>>
>>>>  On 06/05/15 13:35, Jacopo Cappellato wrote:
>>>>>
>>>>>> My vote is clearly stated: propose a Git workflow that is inline with
>>>>>> the ASF policies and that is good for the OFBiz project and I will vote
>>>>>> positively.
>>>>>>
>>>>>> Jacopo
>>>>>>
>>>>>> On May 6, 2015, at 8:29 AM, Hans Bakker <
>>>>>> [hidden email]> wrote:
>>>>>>
>>>>>>  Then you better change your vote? At it is now, we cannot even
>>>>>>> create an implementation proposal.
>>>>>>> Hans
>>>>>>>
>>>>>>> On 06/05/15 13:22, Jacopo Cappellato wrote:
>>>>>>>
>>>>>>>> On May 6, 2015, at 3:34 AM, Hans Bakker <[hidden email]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>  It is no use, setting up an implementation plan when there is
>>>>>>>>> still a possibility people will reject it.
>>>>>>>>>
>>>>>>>> Ok, if this was your goal then it seems you got your answer: most
>>>>>>>> people are inclined to Git (or will not object to it) but don't feel like
>>>>>>>> it is actionable enough for a vote now: defining an implementation plan, so
>>>>>>>> that people can understand how the actual every day work of the OFBiz
>>>>>>>> community (committers, contributors and users) with Git will be, would
>>>>>>>> definitely help.
>>>>>>>>
>>>>>>>> Jacopo
>>>>>>>>
>>>>>>>
>

--
Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

[hans_bakker]

After creating a proper plan sure, now formally you have blocked
progress with your veto.

Hans

On 06/05/15 14:16, Jacopo Cappellato wrote:
> On May 6, 2015, at 9:10 AM, Hans Bakker <[hidden email]> wrote:
>
>> However then still we need a vote again after the proposal... if you make it a -0.9 then when the proposal is agreed, no need for a vote.
> are you really considering the idea of doing such an important change for the community without a clear and strong indication from it (at least a few +1 votes from his committers)?
>
> Jacopo

[Jacopo Cappellato-5]

On May 6, 2015, at 9:54 AM, Hans Bakker <[hidden email]> wrote:

> After creating a proper plan sure, now formally you have blocked progress with your veto.

The veto is only on commit changes, this vote is not for a commit change so my -1 doesn't count as a veto.

Jacopo

[Christian Geisert]

C'mon Hans

The vote was about "should we convert the master SVN repository of
Apache OFBIz to a GIT version?"

Nobody stops you from creating a proper plan.

Christian

Am 06.05.2015 09:54, schrieb Hans Bakker:

> After creating a proper plan sure, now formally you have blocked
> progress with your veto.
>
> Hans
>
> On 06/05/15 14:16, Jacopo Cappellato wrote:
>> On May 6, 2015, at 9:10 AM, Hans Bakker
>> <[hidden email]> wrote:
>>
>>> However then still we need a vote again after the proposal... if you
>>> make it a -0.9 then when the proposal is agreed, no need for a vote.
>> are you really considering the idea of doing such an important change
>> for the community without a clear and strong indication from it (at
>> least a few +1 votes from his committers)?
>>
>> Jacopo
>
>

[Hans Bakker]

Thank you for the interst and 126 messages on this subject.

Looks like we do not want to go with the technological developments yet.

Thank you all for your time.

The result of the vote if we should move to git:

Binding:
Jacques -0.9
Nicolas -0.9
Jacopo -1
Adam +0
Scott +0
Nicolas +0

Non Binding:
Adrian +0
Taher Alkhateeb: +1
Christian Carlow +1
Pierre +0
michael.brohl +0
Christian +0
Gil portenseigne +0
Nicolas +0.9

On 05/05/15 10:01, Hans Bakker wrote:

> As the discussions seem to end, can i propose a vote?
>
> The question : should we convert the master SVN repository of Apache
> OFBIz to a GIT version?
> The possible answers are according the apache voting guidelines at:
> https://www.apache.org/foundation/voting.html
>
>  *
>
>    +1: 'Yes lets do it'
>
>  * +0: 'I don't feel strongly about it, but I'm okay with this.'
>  *
>
>    -0.5: 'I don't like this idea, but I can't find any rational
>    justification for my feelings.'
>
>  *
>
>    ++1: 'Wow! I like this! Let's /do/ it!'
>
>  *
>
>    -0.9: 'I /really/ don't like this, but I'm not going to stand in the
>    way if everyone else wants to go ahead with it.'
>
>  *
>
>    +0.9: 'This is a cool idea and i like it, but I don't have time/the
>    skills necessary to help out.'
>
>  * -1 'I do not want this.'
>
>
> Votes will be possible for one week from today.
>
> Regards,
> Hans
>
> On 20/04/15 11:38, Hans Bakker wrote:
>> As discussed at apachecon in Austin, i propose to switch from svn to
>> git for the ofbiz repository. The main reason being that all major
>> contributors are using git and contributions are cumbersome, further,
>> git allows for better branching and merging.
>>
>> Regards,
>> Hans
>

[Christian Carlow-OFBizzer]

Are git patches acceptable or should they be provided as svn instead?
Command line supports git to svn formatting but I haven't found a way to
do so in eclipse yet.  If git isn't an acceptable format I'll make an
effort to convert all the patches I've provided for the past couple of
weeks.

On Tue, 2015-05-12 at 08:19 +0700, Hans Bakker wrote:

> Thank you for the interst and 126 messages on this subject.
>
> Looks like we do not want to go with the technological developments yet.
>
> Thank you all for your time.
>
> The result of the vote if we should move to git:
>
> Binding:
> Jacques -0.9
> Nicolas -0.9
> Jacopo -1
> Adam +0
> Scott +0
> Nicolas +0
>
> Non Binding:
> Adrian +0
> Taher Alkhateeb: +1
> Christian Carlow +1
> Pierre +0
> michael.brohl +0
> Christian +0
> Gil portenseigne +0
> Nicolas +0.9
>
> On 05/05/15 10:01, Hans Bakker wrote:
> > As the discussions seem to end, can i propose a vote?
> >
> > The question : should we convert the master SVN repository of Apache
> > OFBIz to a GIT version?
> > The possible answers are according the apache voting guidelines at:
> > https://www.apache.org/foundation/voting.html
> >
> >  *
> >
> >    +1: 'Yes lets do it'
> >
> >  * +0: 'I don't feel strongly about it, but I'm okay with this.'
> >  *
> >
> >    -0.5: 'I don't like this idea, but I can't find any rational
> >    justification for my feelings.'
> >
> >  *
> >
> >    ++1: 'Wow! I like this! Let's /do/ it!'
> >
> >  *
> >
> >    -0.9: 'I /really/ don't like this, but I'm not going to stand in the
> >    way if everyone else wants to go ahead with it.'
> >
> >  *
> >
> >    +0.9: 'This is a cool idea and i like it, but I don't have time/the
> >    skills necessary to help out.'
> >
> >  * -1 'I do not want this.'
> >
> >
> > Votes will be possible for one week from today.
> >
> > Regards,
> > Hans
> >
> > On 20/04/15 11:38, Hans Bakker wrote:
> >> As discussed at apachecon in Austin, i propose to switch from svn to
> >> git for the ofbiz repository. The main reason being that all major
> >> contributors are using git and contributions are cumbersome, further,
> >> git allows for better branching and merging.
> >>
> >> Regards,
> >> Hans
> >

[Nicolas Malin-2]

Le 12/05/2015 03:19, Hans Bakker a écrit :
>
> Nicolas -0.9
:) I voted -0 Hans not -0.9 it's not the same ;)

[Jacques Le Roux]

I guess it's a matter of feeling, I did not even vote and got a -0.9 :)

Jacques

Le 12/05/2015 08:59, Nicolas Malin a écrit :
> Le 12/05/2015 03:19, Hans Bakker a écrit :
>>
>> Nicolas -0.9
> :) I voted -0 Hans not -0.9 it's not the same ;)
>

[Michael Brohl-3]

Thanks Hans for taking the effort, but...

- I see a Nicolas 3 times? I know of Julien Nicolas and Nicolas Mailin...
- Martin Becker's vote is missing (ok, he introduced a new value, maybe
it does not count)

The last votes were a little bit confusing and are at least hard to
follow. Maybe we should change the process a little bit, e.g.

- only give a vote as direct answer to the vote call, in the first line
of the answer
- open a corresponding vote discussion thread where all the explanations
and discussions take place

Regards,

Michael Brohl
ecomify GmbH
www.ecomify.de

Am 12.05.15 um 03:19 schrieb Hans Bakker:

> Thank you for the interst and 126 messages on this subject.
>
> Looks like we do not want to go with the technological developments yet.
>
> Thank you all for your time.
>
> The result of the vote if we should move to git:
>
> Binding:
> Jacques -0.9
> Nicolas -0.9
> Jacopo -1
> Adam +0
> Scott +0
> Nicolas +0
>
> Non Binding:
> Adrian +0
> Taher Alkhateeb: +1
> Christian Carlow +1
> Pierre +0
> michael.brohl +0
> Christian +0
> Gil portenseigne +0
> Nicolas +0.9
>
> On 05/05/15 10:01, Hans Bakker wrote:
>> As the discussions seem to end, can i propose a vote?
>>
>> The question : should we convert the master SVN repository of Apache
>> OFBIz to a GIT version?
>> The possible answers are according the apache voting guidelines at:
>> https://www.apache.org/foundation/voting.html
>>
>>  *
>>
>>    +1: 'Yes lets do it'
>>
>>  * +0: 'I don't feel strongly about it, but I'm okay with this.'
>>  *
>>
>>    -0.5: 'I don't like this idea, but I can't find any rational
>>    justification for my feelings.'
>>
>>  *
>>
>>    ++1: 'Wow! I like this! Let's /do/ it!'
>>
>>  *
>>
>>    -0.9: 'I /really/ don't like this, but I'm not going to stand in the
>>    way if everyone else wants to go ahead with it.'
>>
>>  *
>>
>>    +0.9: 'This is a cool idea and i like it, but I don't have time/the
>>    skills necessary to help out.'
>>
>>  * -1 'I do not want this.'
>>
>>
>> Votes will be possible for one week from today.
>>
>> Regards,
>> Hans
>>
>> On 20/04/15 11:38, Hans Bakker wrote:
>>> As discussed at apachecon in Austin, i propose to switch from svn to
>>> git for the ofbiz repository. The main reason being that all major
>>> contributors are using git and contributions are cumbersome,
>>> further, git allows for better branching and merging.
>>>
>>> Regards,
>>> Hans
>>