Talk:Module Development Collaboration
Go Bible tools
Wrt "ThML for import to Go Bible?", I generally use a TextPipe filter for this purpose. Yet please remember that Go Bible Creator can process USFM files directly as one of the input formats, so ThML is not always required. David Haslam 03:34, 25 June 2012 (MDT)
- As regards nomenclature, to avoid confusion, I try to avoid the word "module" for Go Bible applications. It's preferable to reserve the word for SWORD modules. David Haslam 03:36, 25 June 2012 (MDT)
- If we can make the primary focus the collaboration on making the SWORD module, there are existing methods (involving the use of diatheke & TextPipe) to make a ThML file for use with Go Bible Creator. David Haslam 04:01, 25 June 2012 (MDT)
- Go Bible is considerably past its peak popularity due to the advent of smart phones and tablets. Development stopped in early 2013. David Haslam 05:53, 18 December 2015 (MST)
Trawling through correspondence with the owners/suppliers of the original files can be tedious, and may even be confusing. We should determine the important and critical properties for conf files as early as possible, and record permissions, license agreements, copyright status, etc in a separate meta folder. David Haslam 05:22, 25 June 2012 (MDT)
A lot of the work proposed could be done via githooks.
- Easily fixed. It was due to a spurious "|" in the external link. David Haslam 13:44, 17 December 2015 (MST)
Please add a section about the two collaborative Git based options available for hosting source texts.
- CrossWire Git Private – for copyrighted works
- CrossWire Bible Society on GitLab – for public domain works