1
-
2
-
3
- Please http://kaldi-asr.org/ for documentation on Kaldi.
1
+ *README*
4
2
5
3
To build the toolkit: see ./INSTALL. These instructions are valid for UNIX
6
4
systems including various flavors of Linux; Darwin; and Cygwin (has not been
@@ -10,7 +8,24 @@ instructions (excluding Cygwin), see windows/INSTALL.
10
8
To run the example system builds, see egs/README.txt
11
9
12
10
If you encounter problems (and you probably will), please do not hesitate to
13
- contact the developers at https://groups.google.com/forum/#!forum/kaldi-developers .
11
+ contact the developers at https://groups.google.com/forum/#!forum/kaldi-help .
14
12
In addition to specific questions, please let us know if there are specific
15
13
aspects of the project that you feel could be improved, that you find confusing,
16
14
etc., and which missing features you most wish it had.
15
+
16
+ ** Kaldi information channels **
17
+ For HOT news about Kaldi see: http://kaldi-asr.org/
18
+
19
+ Documentation of Kaldi: http://kaldi-asr.org/doc/
20
+ - info about the project, description of techniques, tutorial for C++ coding
21
+ - Doxygen reference of the C++ code
22
+
23
+ Kaldi forum, mailing-lists: http://kaldi-asr.org/forums.html
24
+ - User list : https://groups.google.com/forum/#!forum/kaldi-help (
[email protected] ).
25
+ - Developer list : https://groups.google.com/forum/#!forum/kaldi-developers (
[email protected] )
26
+ - also try luck and search in SourceForge archives: https://sourceforge.net/p/kaldi/discussion/
27
+
28
+ Development pattern for contributors:
29
+ A) create a personal fork of the kaldi-asr/kaldi repository in github,
30
+ B) make your changes in a named branch different from "master", e.g. you create a branch "my-awesome-feature"
31
+ C) generate a pull request through the web interface of github
0 commit comments