From: Ricardo Wurmus <rekado@elephly.net>
To: nly@disroot.org
Cc: 35423@debbugs.gnu.org
Subject: [bug#35423] [PATCH] gnu: Add julius.
Date: Mon, 06 May 2019 17:29:49 +0200 [thread overview]
Message-ID: <87h8a7fvo2.fsf@elephly.net> (raw)
In-Reply-To: <52e174f4e91974bc416b9c465ae31d48@disroot.org>
The license says:
3. When you publish or present any results by using the Software, you
must explicitly mention your use of "Large Vocabulary Continuous
Speech Recognition Engine Julius".
This looks like a problem. Also see
https://github.com/julius-speech/julius/issues/29.
Aside from this, I see that you delete the check phase. Could you
explain why?
--
Ricardo
next prev parent reply other threads:[~2019-05-06 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 2:34 [bug#35423] [PATCH] gnu: Add julius nly
2019-04-25 3:29 ` Tobias Geerinckx-Rice
2019-04-26 0:41 ` nly
2019-05-06 15:29 ` Ricardo Wurmus [this message]
2019-05-06 18:17 ` nly
2019-05-07 5:02 ` bug#35423: " Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8a7fvo2.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35423@debbugs.gnu.org \
--cc=nly@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).