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
