Term list /glossary
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Documentación
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- rust
- Área
- audio-video-rtc, documentation
Línea de trabajo
Start by reading the glossary and documentation structure in the Rodio repository; the issue does not name specific files or tests. Identify terms for audio pipeline or tree steps, their relationships, and what consumes them, then add a glossary section that helps contributors use those terms consistently.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Rodio has more contributors 🎉 and the maintenance team is growing stronger 🥳. Communication and documentation efforts are harder then they have to be because we do not have words for every concept in rodio.
My goal is to build a glossary (specialized term list) and make that part of the documentation. We could make the docs link to that glossary each time one of its specialized terms is used.
It seems most urgent to get some words around the audio... pipelines?:
let thing = Decoder::new("path").amplify().pausable()
what do we call each of these steps and how they relate to each-other?
Lets give the steps names so we can discuss this more easily:
let decoder = Decoder::new();
let amplified = decoder.amplify();
let pausable = amplified.pausable();
This is an audio pipeline, but it could also be an audio tree (if we introduce mix). I think we need a words for
- the thing that generates the samples on one end of the pipeline/tree. Maybe it should be called the generator?
- referring to an earlier or later step in the pipeline/tree. Concretely is pausable, which is applied after amplify, the parent of amplify or its child? Maybe some other word works? And what is called the other way round?
- things that these pipelines are fed to. When this pipeline is consumed by something, what do we call it? consumer? It could also be called a Sink as that word will be freed up once we deprecate the
Sinkstruct.
- Lenguaje dominante
- Rust
- Estrellas
- 2.5k
- Forks
- 338
- Merge medio
- 1 d 3 h
- PR fusionados (30 d)
- 1
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de RustAudio/rodio
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 73/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 62/100
-
WavDecoder::size_hint underflows (u32 wrap, ~4.29e9) after EOF, causes multi-GB Vec::collect() allocationPosiblemente ocupada @marin-m la tomó hace 6 días. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Todos los issues de RustAudio/rodio
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
calcit-lang/caps#16 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
penso/herdr-gpui#934 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Y-ASLant/ElegantClipboard#178 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
linxiv-dev/linXiv#384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
priority middle
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
KATO-Hiro/AtCoderClans#12945 ·
Los mantenedores suelen responder en 1 día