Feedback about validated sentences

[nukeador (Rubén Martín [❌ taking a break from Mozilla])]

@jf99

We need a language specific place where we can discuss contribution rules within the community (including a language specific set of rules that can be complemented by the community). This place should ideally be integrated in the sentence-collector tool.

Feel free to open a topic here and we can figure out how to expose it from the tool.

@jf99

We need a way to directly correct a wrong sentence in such a way that the original author notices it.

Yes, that’s planned in our roadmap.

@jf99

Since it is too late for the sentences that are already in use, we need an official way to correct the wrong ones.

There is a cleanup planned for all the sentences in the repo, @gregor will be running it.

@jf99

We need a whitelist for allowed acronyms. Only for acronyms of which there really is just one correct pronunciation (such as BMW, BKA or DDR but not IT, DECT).

No acronyms are allowed, because we don’t really know how people are going to read them. They can be clear for you but we can’t ensure how other people will read them. I see you opened a topic about this.

@dabinat

But the frustrating part is that many of these I saw in my review queue and voted down, yet they still ended up getting approved. I have seen other errors since and voted them down, but are they all going to end up being approved in the next batch?

Well, if a sentences got a negative vote but then other 2 people voted positive, it will get validated. There is little we can do if people are voting positive here, we can however identify who voted on a specific sentence (checking the sentences json) and try to provide these people with feedback about it.

We can also think how to implement a system that allow us catch and fix this small percentage of wrong sentences that end up validated. Maybe from the voice web site? Other?