[sword-devel] Android SWORD
manfred.bergmann at me.com
Thu Sep 2 10:47:34 MST 2010
Am 02.09.2010 um 18:18 schrieb Dmitrijs Ledkovs:
> On 2 September 2010 17:28, Matthew Talbert <ransom1982 at gmail.com> wrote:
>> On Thu, Sep 2, 2010 at 5:31 AM, Manfred Bergmann
>> <manfred.bergmann at me.com> wrote:
>>> I don't know but isn't it contra productive and actually a lot more work to maintain the sources on a variety on source control platforms?
>>> We end up having SWORD source trees on Github, Bitbucket and Launchpad and eventually on any other system that will come up.
>>> For all of those we need people to maintain the sources otherwise we will have a mess of different sources version and implementations.
>>> In my opinion, the main and official sources of SWORD have to be maintained by responsible people from Crosswire.
>>> And it has to be clear that Crosswire will have and is in control of the official sources. I don't actually care which source control system is used for that, though I think that Subversion is the greatest common divisor because all other DVCSs can bi-directional access Subversion.
>> As far as I know, only Launchpad is being used (other than svn). It is
>> quite helpful, because it allows people to publish branches of code
>> and work on them together to finish a feature before it is committed
>> to sword svn. If there is a proliferation of source control systems
>> being used, I'm unaware of it.
> Plus on Launchpad it is clearly stated where the upstream svn
> repository is. The bzr imports are run every 6 hours for many sword
> projects (jsword, sword, xiphos, bibletime). And bzr is fully
> compatible with svn, i.e. you can seamlessly commit to svn from bzr if
> you have access.
That is totally fine.
The use case you are outlining is comprehensible. Btw: MacSword is mirrored on Launchpad as well.
Who is maintaining the Launchpad repos? I mean, one of the branches probably is used to push back to SWORD svn?
More information about the sword-devel