[sword-devel] DVCS (was Re: Project "Free Scriptures" started)

[Chris Burrell]

If you were after a tool to foster collaboration/tracking of patches, etc.
then Atlassian's Crucible is possibly the best one on the market for that.
You can then review commits or patches, branches, etc. People can upload
patches which you can then view against the source code.

It has a VERY and friendly interface, and does integrate with JIRA if you
want it to. It's very easy to use. You can also browse, view previous
revisions, compare any two things, etc.

It basically allows you to do what DM, Martin and I have been using GitHub
to do but is (D)VCS agnostic.

You could ask Atlassian for their On-Demand version if you didn't want to
spend the effort of setting things up initially in a stand-alone way. (STEP
has been using the On-Demand suite and been very pleased with it). Both
On-demand and standalone installs are available for free with an open
source license.

Chris



On 27 February 2014 19:32, Troy A. Griffitts <scribe at crosswire.org> wrote:

>  Look guys,  if you only read and consider any of my emails in their
> entirely, make it this one.
>
> 1) I don't hate DVCS.
> 2) I believe git is the dominant opensource DVCS (nb: 'D') winner and
> choice.
> 3) I have never said we WON'T switch to git at some time.
> 4) I have never said that SVN is superior to git.
> 5) I don't want anything to be 'closed' or 'hidden'.
> ____________________________________
>
> The reason things aren't switching right now:
>
> 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).
>
> 2) If we switched the main repository to use git, this would effectively
> change one thing:
>
> git svn clone https://crosswire.org/svn/sword -s (plus: git svn rebase,
> git svn dcommit) to:
> git clone https://crosswire.org/svn/sword.git
>
> This in itself will not facilitate us working together better or faster or
> prevent 'losing' patches.
> In summary, it is technically possible to already do these things with git
> now and we are not.
>
> 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.
> __________________________
>
> Final thoughts and suggestions:
>
> 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.
>
> 2) I DON'T HATE GIT.
>
> 3) I certainly HEAR the cries for change.
>
> 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.
>
> 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.
>
> 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.
>
> Sincerely (no, really, "Sincerely"),
>
> Troy
>
>
>
>
>
>
>
>
>
>
> On 02/27/2014 12:58 AM, Nic Carter wrote:
>
>
>  On 27 Feb 2014, at 3:44 am, Troy A. Griffitts <scribe at crosswire.org>
> wrote:
>
> 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.
>
>
> 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.
> I have also submitted patches that have been accepted, though! :) [ insert
> comment about HTML parsing :D ]
>
>  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.
>
>  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.)
> :(
>
>
>  Thanks, ybic
>  nic...  :)
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20140227/ad2c3cf1/attachment-0001.html>