|
If someone from Debian were to contact me about any licensing issues I'd be happy to discuss them with them...
Honestly I'm not willing to read though a 184 comment message list to figure out what they don't like. I've made changes in the past to accommodate various Linux distros and I'm still willing to do so if they contact me about it.
Honestly it really pisses me off that Distros like Debian and Fedora (Yes I'm calling out the two biggest offenders) just maintain their own patch sets and _NEVER_ even make the upstream project aware of them. It literally took a third party to point me to the patches and help me get a number of them integrated for Fedora and Debian in the past.
This is why I refuse to support (building and running is supported but I mean as far as providing help) for Linux. Linux packagers (I work on multiple projects including Sigil) never communicate with upstream and are often hostile uncommunicative when upstream tries to reach out to them to resolve any issues they may have. I simple have no desire to waste my time or effort reaching out to every distro to see if they have any issues or complaints. If they have an issue they know how to reach me and we can talk about it. But they don't.
The only issue brought up was quite a while ago and it was over the embedding of the xsd schema files. That Debian person said they'd take care of getting permissions to embed the files. They never got back to me about it. If that's still the issue, with the new plugin interface we can decouple FlightCrew and make it a plugin for the next minor release. We are planning on doing this anyway in the future but we can bump it up if need be. There will be a new validation app that isn't as strict (think more like what calibre does) and supports EPUB 3 we plan (there is a beta plugin right now) that we are currently working on to replace FlightCrew.
So... Tell me what's wrong and I can look into resolving the issue. But not communicating with upstream won't get any changes downstream.
|