[sword-devel] Android SWORD
Manfred Bergmann
manfred.bergmann at me.com
Thu Sep 2 02:31:23 MST 2010
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.
Manfred
Am 02.09.2010 um 04:55 schrieb Troy A. Griffitts:
> Is there someone maintaining bindings on github who doesn't have access
> to our SVN repository?
>
> I'm happy to add more writers. Please let me know.
>
>
> Troy
>
>
>
>
> On 09/01/2010 09:45 AM, Matthew Talbert wrote:
>> On Tue, Aug 31, 2010 at 7:11 PM, Bill Burton <bburton at mail.com> wrote:
>>>
>>> Hello,
>>>
>>> On a related note, could this project be hosted on http://github.com? It would provide much better ability to collaborate since anyone can fork, make changes and then push them back for optional inclusion. The built-in wiki would make it easy to publish any appropriate docs.
>>>
>>> For an example of why this would be helpful, I have some libsword swig bindings for Ruby that never got committed because no one who was a commiter had the time or inclination to step up and look at them. If I could have forked the swig bindings, and checked in my changes, then whether or not they became incorporated in the official version, they would be readily available for anyone to find, evaluate and/or fix.
>>>
>>
>> Please consider branching http://launchpad.net/sword and publishing
>> your ruby swig bindings. Much of the recent bindings work has been
>> done on launchpad. I can't promise results, but the person who has
>> been doing the recent work will definitely be able to see your work
>> there.
>>
>> Matthew
>>
>> _______________________________________________
>> 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
More information about the sword-devel
mailing list