|
The application uses calibre's command line tools to help users convert, reformat, reorganise etc. their eBooks. It runs commands and parses the output of those commands, e.g. JSON from calibredb with the --for-machine switch, and XML from fetch-ebook-metadata. It doesn't interact with calibre in any other way. It doesn't load any of its SQLite databases to get information from them, nor does it use the provided calibre-debug Python console to run any external code.
The application is primarily targeted at visually impaired screen reader users, hence its existence, as calibre's Qt GUI is not appropriately screen reader-accessible to allow for efficient, simple use of the program. As much processing of files and data is done in my own application as possible, but I'm using calibre in parts to avoid reinventing the wheel. It has excellent support for eBook formats already, and to recreate such support seems like a waste of development time and effort, not to mention an unrealistic goal for a single relatively new developer.
If I were to ask my users to install calibre separately, would these license terms still apply? If not, and I do place the source for my application on a public site such as GitHub, do I have to accept contributions, or is making the source available sufficient?
Apologies for all the questions, but I'm trying to work out a distribution method that, primarily, is right for my users, but calibre's tools are providing my application with some of its information so its only right that I respect the efforts of its developers as well.
Thanks.
|