Re: Result: Vote: move to git.
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 ;)
Re: Result: Vote: move to git.
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 ;)
Re: Result: Vote: move to git.
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 smime.p7s Description: S/MIME Cryptographic Signature
Re: Result: Vote: move to git.
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 -0.9 it's not the same ;)
Re: Result: Vote: move to git.
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 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
Result: Vote: move to git.
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
Re: Result: Vote: move to git.
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
Re: Vote: move to git.
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 mailingl...@antwebsystems.com 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 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 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
Re: Vote: move to git.
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 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
Re: Vote: move to git.
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 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
Re: Vote: move to git.
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 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 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 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 mailingl...@antwebsystems.com 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 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 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
Re: Vote: move to git.
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 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 mailingl...@antwebsystems.com 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 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 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
Re: Vote: move to git.
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 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 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 mailingl...@antwebsystems.com 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 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 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
Re: Vote: move to git.
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 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 jacopo.cappell...@hotwaxsystems.com 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 mailingl...@antwebsystems.com 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 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 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
Re: Vote: move to git.
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 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 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 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 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 mailingl...@antwebsystems.com 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 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 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
Re: Vote: move to git.
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 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
Re: Vote: move to git.
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 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 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
Re: Vote: move to git.
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 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 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 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 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 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 mailingl...@antwebsystems.com 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 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 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
Re: Vote: move to git.
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 community without a clear and strong indication from it (at least a few +1 votes from his committers)? Jacopo
Re: Vote: move to git.
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
Re: Vote: move to git.
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 jacopo.cappell...@hotwaxsystems.com 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 mailingl...@antwebsystems.com 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 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 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
Re: Vote: move to git.
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 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 community without a clear and strong indication from it (at least a few +1 votes from his committers)? Jacopo
Re: Vote: move to git.
-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 and not all the way Git could be used are allowed (for example I don't think we will be allowed to accept Pull Requests from GitHub). There are several ASF projects that have switched to Git (https://git-wip-us.apache.org/repos/asf ) but the workflows they have adopted are different from the ones implied by some of the comments in this mailing list; see for example: http://karaf.apache.org/index/community/contributing.html (this is very similar to our current svn-based workflow) http://wiki.apache.org/hadoop/GitAndHadoop (patch based contributions) I have mentioned a few times that until someone will take time to review what others do and what can be done @ASF with Git and come up with a proposal for OFBiz, my vote will be negative because it doesn't make any sense to vote for a tool or the other. Jacopo On May 5, 2015, at 5:01 AM, Hans Bakker h.bak...@antwebsystems.com 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
Re: Vote: move to git.
+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 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
Re: Vote: move to git.
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, I admire Adam, spending so much time on maven when people can still reject it. On 05/05/15 20:06, Jacopo Cappellato wrote: -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 and not all the way Git could be used are allowed (for example I don't think we will be allowed to accept Pull Requests from GitHub). There are several ASF projects that have switched to Git (https://git-wip-us.apache.org/repos/asf ) but the workflows they have adopted are different from the ones implied by some of the comments in this mailing list; see for example: http://karaf.apache.org/index/community/contributing.html (this is very similar to our current svn-based workflow) http://wiki.apache.org/hadoop/GitAndHadoop (patch based contributions) I have mentioned a few times that until someone will take time to review what others do and what can be done @ASF with Git and come up with a proposal for OFBiz, my vote will be negative because it doesn't make any sense to vote for a tool or the other. Jacopo On May 5, 2015, at 5:01 AM, Hans Bakker h.bak...@antwebsystems.com 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
Re: Vote: move to git.
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 more time to figure out what will change. * How does the submit-as-patch workflow change with Jira(still allow for patch, but also allow for fork(clone)/push/merge-request)? * How to deal with empty directories(svn allows them, git does not)? * Do we try to support signed commits? * Should Acked-By, Signed-off-By, etc be adopted as pseudo tags(see the linux-kernel's use of git)? * Use pseudo tags for Jira issues? * What about CLA for all those fork/clone above? * Who are the Lieutenants, and who is the Dictator(the linux kernel way, not a suggestion for us)? * What about line-ending changes? Git has a feature(.gitattributes, .git/info/attributes) that allow for many different flags to be set; what would those values be? These are just off the top of my head. On 05/05/2015 08:06 AM, Jacopo Cappellato wrote: -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 and not all the way Git could be used are allowed (for example I don't think we will be allowed to accept Pull Requests from GitHub). There are several ASF projects that have switched to Git (https://git-wip-us.apache.org/repos/asf ) but the workflows they have adopted are different from the ones implied by some of the comments in this mailing list; see for example: http://karaf.apache.org/index/community/contributing.html (this is very similar to our current svn-based workflow) http://wiki.apache.org/hadoop/GitAndHadoop (patch based contributions) I have mentioned a few times that until someone will take time to review what others do and what can be done @ASF with Git and come up with a proposal for OFBiz, my vote will be negative because it doesn't make any sense to vote for a tool or the other. Jacopo On May 5, 2015, at 5:01 AM, Hans Bakker h.bak...@antwebsystems.com 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
Re: Vote: move to git.
+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: 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
Re: Vote: move to git.
-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 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
Re: Vote: move to 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: 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
Re: Vote: move to git.
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) Christian
Re: Vote: move to git.
+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 projects in mind (Maven, Moqui etc.) I think we should not force it right now. The benefits are not that strong. Regards, Michael Brohl ecomify GmbH www.ecomify.de Am 05.05.15 um 05:01 schrieb Hans Bakker: 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 smime.p7s Description: S/MIME Cryptographic Signature
Re: Vote: move to git.
smime.p7m Description: S/MIME encrypted message
Re: Vote: move to git.
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 Am 05.05.2015 um 06:25 schrieb Adam Heath doo...@brainfood.com: 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 no longer a center. *Someone* has to be pulling/merging all the branches, and who would step up to that plate? Who would want to take on the mantel? I don't think we as a community are ready to require that of someone. Of course, we need to start planning for this eventuality, imho, but we are still a long ways off. ps: I, and others, will continue to use git in our upstream svn interactions, as that seems to work well enough pps: as per Adrian's vote call, there is nothing actionable here. On 05/04/2015 10: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 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
Re: Vote: move to git.
+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 : 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
Vote: move to git.
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
Re: Vote: move to git.
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 no longer a center. *Someone* has to be pulling/merging all the branches, and who would step up to that plate? Who would want to take on the mantel? I don't think we as a community are ready to require that of someone. Of course, we need to start planning for this eventuality, imho, but we are still a long ways off. ps: I, and others, will continue to use git in our upstream svn interactions, as that seems to work well enough pps: as per Adrian's vote call, there is nothing actionable here. On 05/04/2015 10: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 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
