<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Look guys, if you only read and
consider any of my emails in their entirely, make it this one.<br>
<br>
1) I don't hate DVCS.<br>
2) I believe git is the dominant opensource DVCS (nb: 'D') winner
and choice.<br>
3) I have never said we WON'T switch to git at some time.<br>
4) I have never said that SVN is superior to git.<br>
5) I don't want anything to be 'closed' or 'hidden'.<br>
____________________________________<br>
<br>
The reason things aren't switching right now:<br>
<br>
1) Contrary to popular belief, the project is not stagnant. You
can check the commit logs. I also currently have multiple working
copies on my personal box with code changes I am testing and
improving before I commit. I personally am still more comfortable
in SVN than git-- in both using daily and more importantly
administrating. I make the majority of the commits to the
repository, second probably Chris, then probably DM, and then
likely GHellings after that (sorry if I've gotten the order
wrong). Only one of these people is pushing for changing the
central repository to git (GHellings).<br>
<br>
2) If we switched the main repository to use git, this would
effectively change one thing:<br>
<br>
git svn clone <a class="moz-txt-link-freetext" href="https://crosswire.org/svn/sword">https://crosswire.org/svn/sword</a> -s (plus: git svn
rebase, git svn dcommit) to: <br>
git clone <a class="moz-txt-link-freetext" href="https://crosswire.org/svn/sword.git">https://crosswire.org/svn/sword.git</a><br>
<br>
This in itself will not facilitate us working together better or
faster or prevent 'losing' patches.<br>
In summary, it is technically possible to already do these things
with git now and we are not.<br>
<br>
3) We have a bug tracker with the ability to even integrate bugs
and patches with our VCS right now. We don't. We are not going
to be magically more disciplined if we switch to a distributed
version control system.<br>
__________________________<br>
<br>
Final thoughts and suggestions:<br>
<br>
1) I like the integrated tools around git from projects like
github which I certainly do see the value of facilitating work
together. I would like to investigate a tool suite, like these
provide, which we could host on our servers. Think 'longevity'.
I am not as concerned about the coolest, newest thing as I am
concerned about that toolset still being a dominant force in 10
years.<br>
<br>
2) I DON'T HATE GIT.<br>
<br>
3) I certainly HEAR the cries for change.<br>
<br>
4) We will probably change when I start using git personally for
my own SWORD work because I just can't live without its killer
features.<br>
<br>
5) If there are any outstanding patches which I do not yet know
about, please (*cough*) create a PCR and attach your patch. This
should be reasonably equivalent to a pull request.<br>
<br>
6) Share and work together using git now. Show me how much
progress you've made collaborating together on a new SWORD feature
and how great your experience has been. Convince me that using a
DVCS will change the way we collaborate and you will go a long way
to moving it up on my todo list.<br>
<br>
Sincerely (no, really, "Sincerely"),<br>
<br>
Troy<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 02/27/2014 12:58 AM, Nic Carter wrote:<br>
</div>
<blockquote cite="mid:51EF921A-0876-485A-BFEB-018432E24650@mac.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<br>
<div>
<div>On 27 Feb 2014, at 3:44 am, Troy A. Griffitts <<a
moz-do-not-send="true" href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span style="font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px; float:
none; display: inline !important;">Nic, you make it sound
like I've repeatedly dropped multiple patches you've tried
to submit. I hope I've not been that irresponsible.</span><br
style="font-family: Helvetica; font-size: 12px; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px;">
</blockquote>
</div>
<br>
<div>I have both submitted patches and also emailed asking if I
should submit a patch when I have modified things, and I've had
no response.</div>
<div>I have also submitted patches that have been accepted,
though! :) [ insert comment about HTML parsing :D ]</div>
<div><br>
</div>
<div>I'm happy keeping my own fork, although it does waste some of
my time when I then need to manually merge things when SWORD is
updated.</div>
<div><br>
</div>
<div>My only comment about "irresponsible" is that I wouldn't say
that!!! I would comment that we are all volunteers and there's a
big lack of time and resources. (And here I am largely thinking
of myself right now! One could just as easily comment that I
have been irresponsible in how long it's taken for the latest
version of PS (which is late in the beta cycle) to be officially
released.)</div>
<div>:(</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks, ybic</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>nic...
:)</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br>
</body>
</html>