Hi Jaak. Of course I would discourage confusing potential developers
with an unofficial fork of the SWORD library on gitorious.
But I'm confused by your comments.
My apologies if I have any outstanding commits in my queue from you
which I haven't committed. Do I?
My complaint against the Bibletime code is that they inefficiently use
the SWORD engine by trying to wrap everything in their own classes which
even I have trouble understanding the intent. SWORD was made to be used
in a frontend, and we make it pretty easy to use. I use it directly in
the frontends and projects I have written and cater it to real frontend
needs. Bibletime, for the long life of the project, has said they want
to maintain this wrapper layer around SWORD such that they can replace
SWORD with an alternate backend in the future. This has never happened,
and I the Bibletime frontend code which has been 'protected' from SWORD
has itself been rewritten many times, as far as I can see from the
mailing list. And though we've tried to encourage collaboration for
years, we have seen next to zero contributions to SWORD from any of the
Bibletime team (no offence to Greg and others who contribute to many
projects and who do contribute to SWORD). I have tried to get
participation, but I usually only get complaints and arrogant calls for
a complete rewrite from developers who don't even understand what's
under the hood.
I personally am old school and haven't acclimated to git. I've used it
for work projects and can get around. There are many things I don't
like, but git proponents seem to love it. I firmly don't believe that
our source control system is the hindrance to contribution. We have a
fairly high bar for contribution because so many projects use our
engine. In my experience, most open source developers don't take code
criticism well and are not willing to submit to an authority when they
are volunteering their time-- which is their prerogative. We don't
allow our code to simply 'churn' because people want change it. We
require a real use case and defence for changes, to protect our frontend
developers from having to change their code, and our interface has
remained fairly stable over the year because of this.
Having said this, I do have a couple submissions (e.g.,
inter-versification mapping framework) which I have not been diligent to
confirm and commit. But unless this is your specific complaint, I'm not
quite sure why the rebellious nature of your email, instead of a
friendly conversation about how to get your developed new feature into
the engine. I'd be happy to work with you on anything you've developed.
Just a generic defence,
Troy
On 12/17/2012 01:13 PM, Jaak Ristioja wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello!
The Mirror
==========
I created a new git mirror of the SVN trunk of Sword at gitorious:
Gitorious web page:
https://gitorious.org/sword-svn-mirrors/trunk
Git URLs:
https://git.gitorious.org/sword-svn-mirrors/trunk.git
git://gitorious.org/sword-svn-mirrors/trunk.git
g...@gitorious.org:sword-svn-mirrors/trunk.git
Why?
====
In short: there's a possibility that there might arise forks.
The BibleTime team has long been contemplating on how to relate to
various issues with Sword and its development, which has somewhat
hindered the development of BibleTime, fixing or working around bugs
dependant on Sword etc. Up to this point, we have discussed
1) writing an alternative backend for BibleTime to replace Sword,
2) writing a better wrapper around Sword which would hide its
deficiencies,
3) a combination of 1) and 2) and allow BibleTime to use multiple
backends,
4) forking Sword as a separate project, and
5) embedding a forked version of Sword SVN in the source code of
BibleTime which would be partly kept up-to-date with the original project.
At this moment we have not yet reached any decision whatsover, but
these discussions have become rather frequent.
Personally, as a developer and the current lead of the BibleTime
project, I'm not satisfied with the code quality of Sword, and find
lacking the documentation of Sword interfaces and file formats. In
addition, as an outsider I have long found it difficult to do anything
about it, partly because of the centralized version control system
used by Sword (SVN), and partly because the lack of explicit
guidelines for new developers (how do I start, get my proposed fixes
and changes applied etc).
I just wanted to clarify what has been under discussion @ BibleTime
during the previous years and what we feel we're experiencing towards
using Sword. I'm not offering any silver bullets, except that for one
thing I urge the Sword project to release a new version of Sword soon.
However, personally, I'd place my bets on recruiting new developers
for the Sword library (and git).
Blessings (and please don't ban me :),
Jaak Ristioja
The BibleTime team
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQgcBAEBAgAGBQJQz3z3AAoJEEqsYmEt1rCONAhAAJK7kbcEr2U0W2pblMxHvsaz
yEwFM3NZr1pe72SZag4JVLpH1wWpWo1xDU4gkQYgD3x5hlKiS+wmXXSCMVxZ6clT
s47mHiyMMaVRCd2LEf6L5wCaBeO45MTcvBEtE1WeVdKuzQ1u1poEJ8XV0hiuU/AH
lJBLbMXFotGlPz7s/ILVqJsyLjyveEQRB9xcL7+MKOd0BgayknYfNRpjBCvb7tCn
dg+LqezOqKDJQD2RAO1cz+dEyt0A6H6wQNYriIqF2hNCT4moAYAPvWfFc3IQrP0G
NYrJpUQIUawAeJHjRHlrq5bT9CbKqvyBGZM4m3T0uRynIWVO3hEi+V4nDkJO6IOk
6ZdwZ1EBRKniGcurKDISol4uNySiOkDrasn5bJP4Re0ekF+oyOwrlC+LyATJDv88
msA0j3OzhcFr/4/+GGaMinNsjEK7w+ANIzyCkiLSHWrs17bR6H1e/U9btyetHdW0
5O/ak4kHfbx88fea03zflAGrvOl2gWEQfEwR/o+08oJpjlw8MkNjDo6iUq6cj6/P
aBi8+B7r+YyPrF7ow1d22/AkjYfFXq/WOoXNFkHi1fYGR4XvahPBUvZGHrLTxGYf
89uzvi3paO5EopSjlb7k+8dmceSNzYFAuXkIqNSiLfWQ7ZzkTirw6BqmXYZdeq5M
yGeGZvzkaYXJNnGA+xKr1TcXuTXfxrQ2fZG/7Ck/V/TXMHUUsLSrchU6Ph39VKj8
8JetRz9gSX3QeuEV8uBCS/pWgRIC7VM+myNlgtH3XfPBPuw65iuO0olkd5u7Doki
u4sqBWU7wMYh7bK2JwLDGN12N9dyyn+XPQZJwj9hvSMi4jlZZqG2QCCPrTsfjdGS
kTreb8aX3xNVKsEvU4tVKEFN1TzW5Gv834EugTMHM3Eb6I385Phr/2KTb8TewDC3
hAbr7Ep4HuAHGiQPJXiIuFwAYDdTsa12gsonghKF60iTlVP0U197VYhr6h48UiW4
9eoyNlToMIJZOCIuXiflhAkbr+YRvHzY0tmADlcQLUUISq7739r9QD9AzZsCPJ3e
bEPGj/cp3CELy7oIR3s0t891MGMZBrIA7ecoCkfzyncFLVQ5Pon5Lo0aXwE7qWdW
ODxtxHSJY8FrFN+hXMTMCX622yENSlN9dyzqgCVs+MdMC6fS7uEI2SZmAyVKJs7S
u86F3KyVwlAYDeHWd/Aci46CKQ4sKoEJDPpBawhlnlQi1mNau0Ls4qF/9IM6YPoP
eOmvKQraCcaLBtvZUoWSrQ/bWSNUn3jGzA/9njucqwBpzTYspie/q0WiKWM2hcp+
+NnL5FwiLPdMGPtjskXrQp7j+OfUOm5pOILpCCjEmlJtCBVF1SdvyNcgTv7JpuQS
QAJm0UCDGjhboD4MG37m9xJs7g0D1/x/aimsjkptkzWQ6u3MvtfSFMx3zGBlCK6A
lJQpU4x7m7PAF/+g4Dm1iFGmvad3aIY1C94+Yp0+QDZbZzZgck/d8JHEb/1peO88
8FqQEygvVqT+kh5TobdEK2r8A/4y6ef9SBBZtCYXnYyach6mRzFIkP9ffRFvpnLg
YGETfXj3zV+ZzBX5KlVq8pbycPcskp1wMOBfQFdpDVXfVUbrlpYoZ3m0jK37EZfx
AyVYmiQaapTpJYhDpKezeD7+lrgV4nYw7I3teK8zh4hOJyOuWBEeRHufh9C9bgWK
3edSXTl1dzf6y0CYXS/zRkeY4On9Go3mFNV9ZVUYn3miTtIAb67Unaz9Y17Uw800
zFku0OQhgj5irenxEHG3pVP/9K5GA1UaIW7RmMDa+/dId764oLUTJo9deegMaSV1
uy9GDyupMkm8ZLmTzvrqNfEa5/6MIXLzJ/H+E/5YnQ45UD+T8s/PmAl5IN0YC9Yd
7lprKAOpO7UbOHHoE45yA/YhFyn04kiGlfe64MPwepdg4GHSTKCnOeESUhyk4sno
Ry/ty/REHQ7LZ8cojcikkVIGekffqnw0dC532jmv7ILlaOBK0i20+/B6BWEGQlkg
9yx+deIX4fYhBkfCZU/8R2y5X1iDTKIcboMqnDJv/4Ki+ndklMrGI1HL4oFwjmF3
aG34V5Bs60gPlJO9CJVb2PEX6r3QmvLctQ85u2ATIh65ennMzc4J6mSQ/Y9WnQvT
gVt3UXD1qLCscujr51wNBZ26CJ2fQ2mKdXtzODBO2rlrVZs4UDZx7IDnRr3ASrTY
c5o2KUDWx7YTA4XwHas9Fk2bFBEJ3Luf21PlztpbVa/9oaFEGO7rzA9h1bP3VMbZ
M1Vy0yxH9f0Ifat2APAzF/YTE2ZUEppkQsnCfyshN9DlOg2wBhkhLUdn6bRyp8W4
MI99+mwloC5bF3iVAaB28DcGpZ15w7aqlPH6zNHhfHNSxQLUw3+Ql4NwuW+e9kUG
YshzqGkYln2D09C8K00Qoye7klRZmXOyj8OmUK6nm4yUcxRHyzfL8zhx1paPWqKR
kK2M56XTLdVrU0/XBsY9yY4ek8GGDUthuAJ9LfWYnQDWa2DQSbSIgFrDN0e1IHSa
e+wWzuO/+AxiBzZcTkkE0buxCRjEUgyqBewoPZE3Ms7vgOlp36QEMsKkJ3kFagM5
17x0S/vLsCT6yRhsndO+q/3UmkPwVol2/NnI1/3lmSHC74HxMuBrNOjLvsjo9Hmb
PIjsrzDcLhQiwSV97bwVxJ1HibtoT8zjBzrqbT+3wZi33mU1zQwNwsamtU4P5IVr
V3Wg+3Le6PzOKsw/Dk08
=9C3L
-----END PGP SIGNATURE-----
_______________________________________________
sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
