Sure, Chris, if you give me appropriate permissions to do so. My current github username is "jotik-".
Jaak On 17.12.2012 22:47, Chris Burrell wrote: > Can I suggest we put this on github under the crosswire organisation? We > already have JSword there... > > github.com/crosswire <http://github.com/crosswire> > > Chris > > > > On 17 December 2012 20:13, Jaak Ristioja <j...@ristioja.ee > <mailto:j...@ristioja.ee>> wrote: > > 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 > <http://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 > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > <mailto: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 >
signature.asc
Description: OpenPGP digital 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
