Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Clips or Hours? ...how we communicate data going forward

See original GitHub issue

Currently we collect and validate clips, these translate magically to hours. The overall goals of the Common Voice project are measured in hours, though we are currently counting and measuring clips as user level stats.

Suggestion: move to time based measurements across the project (including user stats).

@mikehenrty @Gregoor @kdavis-mozilla what are the implications of doing this? Is it technically feasible?

cc @flekkowich @Gregoor @LRSaunders

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:15 (8 by maintainers)

Top GitHub Comments

1reaction

mikehenrtycommented, Jun 28, 2018

@mikehenrty @Gregoor @kdavis-mozilla what are the implications of doing this? Is it technically feasible?

Definitely technically feasible as we just estimate by average length of clip. This is what we currently do for the homepage progress bar for instance.

After giving this some though, I feel using hours/minutes vs clip count is better since it informs the user of the sense of scale we need. It might be a little disillusioning when their profile clip count changes from, say 2000 clips, to 2.5 hours. But I think the switch is worth it to not hide our goals and how we are actually making progress towards them.

Long story short, I agree with your suggestion 😃

0reactions

ghostcommented, Aug 15, 2018

➤ Megan Branson commented:

Moving this to done as we’ve started the implementation migration to hours. Thanks all!