A new poll has been created: Today we demonstrated Zoom's automated closed captioning feature during the TSC meeting. The functionality did a so-so job. As you would expect from the large array of acronyms, non-native English speakers and speech patterns present our wonderful global community the tool has some significant limitations. Here are the issues I see.
* There is no indication of who is/was speaking at the time * Comments from multiple speakers may be mixed on the same line of text * Lots of incorrect word substitution * Lack of appropriate punctuation changing the context of what is captured * It will drop text when there isn't a sufficient gap between words or speakers For example see what you can figure out from this snippet of text it created while at least 5 different people were participating in a discussion. > > 06:50:04 So for I release we will take it according > 06:50:09 to like, try to. > 06:50:11 I think we are all in line, I just wanted to be sure that my, my > peers in the TSP go for line with what has been discussed and have any > concerns and ppl as well, right. > 06:50:23 So, I just type in the chat, that the requirements, etc. peace > treaty will remain a feature or a robot best fit for a new requirement, x > x will be submitted as a PLC to validate the implementation. > 06:50:37 Later on, this new hex requirement xx will be subject to JIRA > approval Cindy's requirement cannot be implemented for new code only, and > therefore approved best practice by default. > 06:50:47 And I should say, for all newly, so we should add owners. And > then I think one for free to will rely on Julian Pathak doctor that I hope > I've kept your quality the distribution, are the ones I would like to > invite somebody to, to help us to be sure that > 06:51:06 we are capturing what has been discussed on the call. And again, > my apologize to Joan Late, the cold had the family emergency. But I'm glad > to be part of this call today. > 06:51:18 So one thing Catherine, is that it's currently listed as a best > practice, not know I just, Oh, > 06:51:30 yeah, you're right maybe there is a litigation problem I don't > know, but it should be soon as a feature. > 06:51:39 Yeah, I'm sure it. > 06:51:43 So did you read a book. > 06:51:45 And that's it. Yeah. > 06:51:47 Yeah, if it's marked as PLC it will show in the PLC section. > 06:51:55 So David, that's going to be marked as a feature. > 06:52:01 And the TLC pick is not big fantasy books is not sick. Oh, it's > not okay. > There was no discussion of a "peace treaty" or "litigation", no "hex" requirement, no mention of any "Cindy", "Joan Late", or "Julian Pathak", or anything about "robot" or reading a book or anything being "not okay". "PLC" is a common acronym for Project Life Cycle. Even if everyone was a native speaker, there would still be problems with what was captured. To me this is all highly confusing and is likely to lead to misunderstandings and communication issues if someone reads the transcript instead of listening to the recording or if they happen to include a cut-n-paste in an email or something. Personally I don't think that the functionality provides sufficient benefit in the context of our community to warrant using it. Regardless I wanted to see how the community feels about using this functionality for the TSC meetings going forward, so I'm tossing it our as a general poll -kenny 1. Yes- use it during the TSC meeting 2. Yes- use it during the TSC meeting AND attach the automated transcription to the meeting minutes 3. No - don't use it during the TSC meeting Vote Now: https://lists.onap.org/g/onap-tsc/vote?pollid=19269 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#7405): https://lists.onap.org/g/onap-tsc/message/7405 Mute This Topic: https://lists.onap.org/mt/79506263/21656 Mute #poll-notice:https://lists.onap.org/g/onap-tsc/mutehashtag/poll-notice Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
