Closed matthewmcintire closed 3 years ago
Certainly. I can add the license name alongside Kaldi where the engine back-ends are listed, e.g. in the README file's Introduction section. I'll do the same for the CMU Sphinx back-end, which is also licensed differently.
David Zurow (@daanzu) has indicated on the KaldiAG project page here that he is willing to be flexible for those who find the license problematic.
Sorry for the late reply.
My aside on the license for CMU Sphinx is not so accurate. That license is permissive and appears essentially the same as the 2-clause BSD license.
Could a note be made somewhere more prominently in the documentation that when using the Kaldi back end, the AGPL license from kaldi_active_grammar subsumes the LGPL license from dragonfly? AGPL is significantly more restrictive.