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 ;)
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 ;)
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
That was a translation of your feeling :-)
On 12/05/15 14:51, Jacques Le Roux wrote:
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
Good suggestions, Michael
On 12/05/15 15:06, Michael Brohl wrote:
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
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
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
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:
On May 6, 2015, at 3:34 AM, Hans Bakker h.bak...@antwebsystems.com 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
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 h.bak...@antwebsystems.com wrote:
It is no use, setting up an implementation plan when there is still a
On May 6, 2015, at 8:56 AM, Hans Bakker mailingl...@antwebsystems.com 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
On May 6, 2015, at 8:46 AM, Hans Bakker mailingl...@antwebsystems.com 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
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
On May 6, 2015, at 8:43 AM, Taher Alkhateeb slidingfilame...@gmail.com 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
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
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 mailingl...@antwebsystems.com wrote:
However then still we need a vote again after the proposal... if you make
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 mailingl...@antwebsystems.com wrote:
Then you better change your vote? At it is now, we
Consensus is always needed.
Best regards,
Pierre
Op woensdag 6 mei 2015 heeft Hans Bakker mailingl...@antwebsystems.com
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
On May 6, 2015, at 9:10 AM, Hans Bakker mailingl...@antwebsystems.com 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
On May 6, 2015, at 9:54 AM, Hans Bakker mailingl...@antwebsystems.com 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
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
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
-1
not because I don't like Git or because I don't think it wouldn't be a good fit
for OFBiz; the reason for my negative vote is that in the vote there is no
mention to the workflow the project will adopt; at the ASF there are some
limitations due to Infrastructure and/or license/legal reasons
+0
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 5/4/2015 8:01 PM, 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
Jacopo,
This vote was about IF we choose to go to Git, if the answer is yes,
sure then we need an implementation plan.
It is no use, setting up an implementation plan when there is still a
possibility people will reject it.
Regards,
Hans
PS. We really have to change the way we work here,
That's my point as well. These most recent votes have not had concrete
actions attached to them. Without a concrete plan, any kind of +# vote
is not definitive; a +1 could mean anything in these cases.
I chose +0 instead of -0 or -1, as I do believe git is the right
approach, but we need
+0.9
Julien.
Le 05/05/2015 05:01, Hans Bakker a écrit :
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:
-0 (maybe it's the same that +0 ;) ), I vote +0 when I will use git,
but currently the fthe fear of change :).
Le 05/05/2015 05:01, Hans Bakker a écrit :
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
+0
On 05/05/2015 05: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:
Am 05.05.2015 05:01, schrieb Hans Bakker:
As the discussions seem to end, can i propose a vote?
+0
I personally prefer git anytime over svn, but it seems a few people are
not comfortable with git (yet). I'm using it already with ofbiz locally
(no commit via git yet but will try it soon)
+0
Git is a great tool once you understand the mechanisms and get used to it.
But I also think that it might be too early to make it the main source
control for the project. It takes extra effort for some and the
committers have to handle pull requests and such.
With the other bigger sub
smime.p7m
Description: S/MIME encrypted message
Full ack for Adams remarks.
There should be a +0.5 like „I like this idea, but the realization has to be
well planned for a point in the future where the all over organization fits the
needs for a different contribution process ;-)
So, +0.5 from me.
Martin Becker
ecomify GmbH
www.ecomify.de
+0
I like git and use it primarily but I'm not sure that adoption of git at
the ASF has reached the point where I'm prepared to force it onto the
unwilling.
On 5 May 2015 15:01, Hans Bakker h.bak...@antwebsystems.com wrote:
As the discussions seem to end, can i propose a vote?
The question :
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'
*
This may be the nail in the coffin, at least for now, but +0, needs more
discussion/planning. I've been using git-svn for longer than most with
ofbiz, and would really love it if we were already using git, but it's
just too soon.
Just because git is decentralized, doesn't mean that there is
36 matches
Mail list logo
