List view
# Description This repo already has a lot of nice stuff to help other developers contribute. But it could be better. We will want to leverage GitHub features to help facilitate project management in an open-source, self-organizing project. ## Questions * What milestones should we create to group together issues? * How do we want to size issues? * What are the priorities of issues? * How can we better standardize issues? * How can we organize issues to give developers a better overview? ## DoD (Definition of Done) * General issue template * Bug report template * Issue backlog kanban board * Issues are organized into the backlog into their categories: new, in progress, done, etc. * Issues are sized: What is tiny, small, etc.? * Documented issue sizing: How much work is tiny? 1h, 1d? What about the other sizes? At what size should an issue be broken into 2 or more issues? * Issues are prioritized * New milestone(s) are created to group together the majority of issues that don't currently have a milestone
No due date•0/3 issues closed# Description MFCC rust is required for phase 2 of the wakeword project (TODO add in link to phase 2 milestone of project). We want to have a wakeword engine that can run a wakeword on any device, even a phone. Using Python can be problematic, so it was decided to do this in Rust. The engine itself has been written (see wakeword project phase 2 milestone). What is left is an MFCC crate in Rust that is similar to `SpeechPy` with the same output. `mfcc-rust` is a port of `SpeechPy`. # DoD (definition of done) * Passes the four unit tests * Train and run test with wakeword with Python version of Precise using `mfcc-rust` successfully * Benchmark `SpeechPy` vs. `mfcc-rust` * Attempt to run with Precise rust engine * Documentation
No due date•2/5 issues closed