Well, For those who are annoyed by my persistent will to improve A/ my understanding of the project, B/ the tools, and C/ the documentation associated, I sorry to say Oops ! I did it again . But not Britney’s style. More Corben Dallas style. I didn’t make it to the fog, but I least, I tried. Pl…

Nice diagram :slight_smile: But IMHO: This is not simplified for common user :slight_smile: It might be useful for those who start on coding or working on AI. You might need to specify the target audience beforehand (or different targets) for UX. All repos under commonvoice should be there and ca…

Thanks for keeping an eye on the documentation! Documentation usually doesn’t get the love it deserves, so any effort here is appreciated. Generally I agree with Bülent that this is not an “oversimplified” view and like his suggestion to split it up by workflow. Alternatively I could see benefit in …

In my opinion, the medium for documentation usually defines the structure. When second version of the Community Playbook came to review, I suggested the use of readthedocs.io , to keep the whole documentation, which supports github linking and localization. Most of the Mozilla projects are/were ther…

[image] bozden: But I feel the need of high level graph on how they all fit together, each box directing to individual repos. I’d like that, as long as it’s high-level and linking to details, I’d support that for sure! [image] bozden: Maybe we can start a topic on “how we can compile a n…

@mkohler , very nice :slight_smile: Perhaps some idea on what “manually” means? By who’s hand I mean :slight_smile:

Well, week end is gone, but I see you did well ! I looked at you diagram, many thanks, it make it more readable ! I totally agree on “level 1 oversight diagram” in higher repo, and “depper diagram” on lower levels. As I was doing my diagram, I was thinking that the very simple diagram for common vo…

@bozden Hey Bülent :raising_hand_man:, please accept my apology for not catching all your proposal upfront… I’ll retake your message and ask :smiley_cat: …I apologize if my question could be seen as rude, it’s not the point, I try to stay on the point of PRO/CONS, and of course I don’t try to hurt…

Updated version… [image] File is still located at : common-voice/docs/Process overview.svg at main · CapitainFlam/common-voice · GitHub

No need to apologize, this is a discussion area :slight_smile: [image] HelloTheWorld: Could you please elaborate In my opinion, the medium for documentation usually defines the structure. ? I was merely saying these: Each medium has its limits, and different set of audiences. In each medium…

Trying to create a 'Common Voice overview' for newbies, SVG drawin' style

Common Voice

mkohler (Michael Kohler) September 25, 2022, 9:51pm 6

Added here: GitHub - common-voice/cv-sentence-extractor: Scraping Wikipedia for fair use sentences

Topic		Replies	Views
Inadequate Documentation Common Voice documentation	9	1740	September 23, 2022
Common Voice Toolbox: Updated with CV v22.0 data Common Voice feedback , tooling	20	3661	November 19, 2025
I'm almost giving up on the project. Feedback from a big contributor (10000 sentences sent, 7000 listened) Common Voice	24	2414	March 15, 2023
📖 Readme: How to see my language on Common Voice Common Voice announcements	35	14554	May 10, 2022
Community Strategy: What does Community Health mean to you? Common Voice participation , feedback	26	3141	November 19, 2021

Trying to create a 'Common Voice overview' for newbies, SVG drawin' style

Related topics