Difference between revisions of "CNMCyber transcript"

From CNM Wiki
Jump to: navigation, search
(→‎Scripting Tasks)
(→‎Transcription Tasks)
 
(28 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
[[CNMCyber script]] is technically wording which is used in [[CNMCyber Office Hours]] events. In the best case scenario, it should be typed and moved to the requirements.  
+
[[CNMCyber transcript]] is technically wording which is used in [[CNMCyber Office Hours]] events. In the best case scenario, it should be typed and moved to the requirements.  
  
−
The script can also be defined as the record of someone's requirement.  
+
The transcript can also be defined as the record of someone's requirement.  
  
−
A script is also an intermediate product, it's not a final product. It's a deliverable but is not user deliverable. It's a sub-product. So then when a script is available, a Wiki page can be developed from the requirements in the script.
+
The transcript is also an intermediate product, it's not a final product. It's a deliverable but is not user deliverable. It's a sub-product. So then when the transcript is available, a wikipage can be developed from the requirements in the transcript.
  
  
−
==Script Development for CNMCyber Events==
+
==Transcript Development for CNMCyber Events==
  
−
===Purpose and Importance of Scripting===
+
===Purpose and Importance of Transcription===
 
:*To have a written record of requirements discussed during the event.
 
:*To have a written record of requirements discussed during the event.
−
:*Support traceability between event discussions and final wiki pages. The script itself leads to requirements. The script isn't the final product, but the requirements that a customer agrees to become the actual product. This can be measured, and in the best situation, it should be a [[requirements traceability matrix]] ([[requirements traceability matrix|RTM]]) record.
+
:*Support traceability between event discussions and final wiki pages. The transcript itself leads to requirements. The transcript isn't the final product, but the requirements that a customer agrees to become the actual product. This can be measured, and in the best situation, it should be a [[requirements traceability matrix]] ([[requirements traceability matrix|RTM]]) record.
  
 
:For example, when you write down requirements on a page, imagine it's what you're presenting to your boss or customer. You're saying, "This is what you'll get." You list down everything – like having HumHub, Odoo, Jitsi set up in a certain way, using ProxmoxVE, making it highly available with three nodes, having a public IPv4 network, running on Apache and Nginx, using Ceph for storage, and routing with [[pfSense]]. You ask, "Is this what you want?" They either sign or confirm via email. This becomes a kind of blueprint.
 
:For example, when you write down requirements on a page, imagine it's what you're presenting to your boss or customer. You're saying, "This is what you'll get." You list down everything – like having HumHub, Odoo, Jitsi set up in a certain way, using ProxmoxVE, making it highly available with three nodes, having a public IPv4 network, running on Apache and Nginx, using Ceph for storage, and routing with [[pfSense]]. You ask, "Is this what you want?" They either sign or confirm via email. This becomes a kind of blueprint.
  
−
===Components of a script===
+
===Components of a transcript===
−
:A script should focus on important information, omitting irrelevant details. A script should omit things like;  
+
:A transcript should focus on important information, omitting irrelevant details. A transcript should omit things like;  
  
 
:*"my name is _ _ _"  
 
:*"my name is _ _ _"  
Line 22: Line 22:
 
:*"I will answer another call."  
 
:*"I will answer another call."  
  
−
:It's not important. So script should include what is important, what should be and what can be moved to requirements.
+
:It's not important. So a transcript should include what is important, what should be and what can be moved to requirements.
  
−
===Scripting for CNMCyber Events===
+
===Transcription for CNMCyber Events===
−
:Scripts will be developed on wiki project page (currently - discussion page) of the product page. The main page is the product and discussion will be a project. Project (current discussion page), here there will be information how the product was developed and what requirements were involved.
+
:Transcripts will be developed on wiki project page (currently - discussion page) of the product page. The main page is the product and discussion will be a project. Project (current discussion page), here there will be information how the product was developed and what requirements were involved.
  
 
===Target Audience and Deliverables===
 
===Target Audience and Deliverables===
−
:A developer working on the product is the target audience of the script. Script by itself is the intermediate product, the product page is the end product and script is a part of development with a deliverable.
+
:A developer working on the product is the target audience of the transcript. Transcript by itself is the intermediate product, the product page is the end product and transcript is a part of development with a deliverable.
  
 
===Success Criteria and Desired Outcome===
 
===Success Criteria and Desired Outcome===
−
:Success for a script is determined by how useful it is. The goal is having Wiki Pages that describe products. For example; we need to have this platform on which our Jitsi will work, which is called talk and we will do this conference one day on the Talk.cnmcyber.com slash something - So right now we are doing this on employableU which is temporary. So the end product is the service but to build this firm we need to have a description of what we are doing, what we need to look for, and what we need to do. So now, in this case the desired out come is a  working technology.
+
:Success for a transcript is determined by how useful it is. The goal is having Wiki Pages that describe products. For example; we need to have this platform on which our Jitsi will work, which is called talk and we will do this conference one day on the Talk.cnmcyber.com slash something - So right now we are doing this on employableU which is temporary. So the end product is the service but to build this firm we need to have a description of what we are doing, what we need to look for, and what we need to do. So now, in this case the desired out come is a  working technology.
  
−
:The technical sense, quality is confirmation the description of the product matches the product itself right. So we have requirements and we have a product. If there's gaps, it's a quality product. But to know that you have a quality product you need to have a description, if you don't have a description how would you know? Scripting is a good way to build this description.
+
:The technical sense, quality is confirmation the description of the product matches the product itself right. So we have requirements and we have a product. If there's gaps, it's a quality product. But to know that you have a quality product you need to have a description, if you don't have a description how would you know? Transcription is a good way to build this description.
  
−
===How to claim a Scripting task===
+
===How to claim a transcription task===
−
:If you are a contractor developing scripts for [[CNMCyber Office Hours]] you will need to;
+
:If you are a contractor developing transcripts for [[CNMCyber Office Hours]] you will need to;
−
:#Go to [[Talk:CNMCyber_script]] to access the scripting tasks list
+
:#Go to [[Talk:CNMCyber transcript]] to access the transcription tasks list
−
:#Find the title of the task you would like to create a script for
+
:#Find the title of the task you would like to create a transcript for
−
:#In the "Contractor" column on the row for that task, write your name to indicate you will be responsible for this script
+
:#In the "Contractor" column on the row for that task, write your name to indicate you will be responsible for this transcript
−
:#In the "Due Date" column on the same row, enter the date when you expect the script to be completed
+
:#In the "Due Date" column on the same row, enter the date when you expect the transcript to be completed
 
:#Notify your CNMCyber contact when you have claimed a task so they know it is assigned
 
:#Notify your CNMCyber contact when you have claimed a task so they know it is assigned
−
:#Develop the script according to the description requirements best described on this wiki page
+
:#Develop the transcript according to the description requirements best described on this wiki page
 
:#Once complete, notify your CNMCyber contact person.
 
:#Once complete, notify your CNMCyber contact person.
 
:#If you have any questions about the task, get clarification from your CNMCyber contact before claiming and beginning work.
 
:#If you have any questions about the task, get clarification from your CNMCyber contact before claiming and beginning work.
  
−
===Steps to create a script===
+
===Steps to create a transcript===
−
:#Transcribe the audio - This can be done manually by listening and typing or if the event is posted on YouTube Channel you can extract the transcript by clicking on the three dots at the bottom right of the video and select show transcript. A side bar will be displayed with the transcript and time stamps. Highlight the entire transcript then copy and paste to the page where you will create the script from.   
+
:#Transcribe the audio - This can be done manually by listening and typing or if the event is posted on YouTube Channel you can extract the transcript by clicking on the three dots at the bottom right of the video and select show transcript. A side bar will be displayed with the transcript and time stamps. Highlight the entire transcript then copy and paste to the page where you will create the transcript from.   
−
:#Clean up the transcript - correct any mistakes in the transcription, eliminate timestamps, and filler words such as "um," "hmm," "oh," "like," "you know," "so", as well as any unnecessary side conversations or interruptions that shouldn't be in the final script. Also remove any repetitions.  
+
:#Clean up the transcript - correct any mistakes in the transcription, eliminate timestamps, and filler words such as "um," "hmm," "oh," "like," "you know," "so", as well as any unnecessary side conversations or interruptions that shouldn't be in the final transcript. Also remove any repetitions.  
 
:#Structure the information - Break the transcript into logical sections using headers. For example, you may have a section for Introduction, topics that were discussed in the meeting
 
:#Structure the information - Break the transcript into logical sections using headers. For example, you may have a section for Introduction, topics that were discussed in the meeting
−
:#Focus on key points - Summarize the script while paying attention to key questions, decisions, and discussion points that are relevant for the requirements of the product.   
+
:#Focus on key points - Summarize the transcript while paying attention to key questions, decisions, and discussion points that are relevant for the requirements of the product.   
−
:#Review the scrip - Go over the draft script and make any final edits to improve clarity. The goal is to create a traceable record of the event that can used to create product requirements.
+
:#Review the scrip - Go over the draft transcript and make any final edits to improve clarity. The goal is to create a traceable record of the event that can used to create product requirements.
−
:#Stick to the requirements - Make sure the script contains the information needed for the product requirements.
+
:#Stick to the requirements - Make sure the transcript contains the information needed for the product requirements.
 
:#Add attributions - Note who said what using speaker attributions like "Kevin:".
 
:#Add attributions - Note who said what using speaker attributions like "Kevin:".
 
:#Add attribute questions - Note who asked each question using "[Name] asked:".
 
:#Add attribute questions - Note who asked each question using "[Name] asked:".
 
:#Add attribute answers - Indicate who provided each answer using "[Name] answered:".
 
:#Add attribute answers - Indicate who provided each answer using "[Name] answered:".
 
:#Check accuracy - Verify names, titles, terminology, and facts.
 
:#Check accuracy - Verify names, titles, terminology, and facts.
−
:#Save the script - Save the script to the discussion page (project page) of the product being developed.
+
:#Save the transcript - Save the transcript to the discussion page (project page) of the product being developed.
−
:#Ask clarifying questions - Get any needed context before beginning to create the script.
+
:#Ask clarifying questions - Get any needed context before beginning to create the transcript.
  
 
===Turn around time===
 
===Turn around time===
−
:When following the steps to claim a scripting task from the scripts list, contractors should set the due date in Step 4 to reflect completion of the script within a maximum of two days or less from the date the scripting task was claimed. After accessing the scripts list in Step 1, locating the desired task in Step 2, entering your name in the "Contractor" column in Step 3, and indicating the due date in Step 4, the claimed script development should then be finished within the due date indicated of less than two days or unless additional time was approved during claiming due to unusual circumstances.
+
:When following the steps to claim a transcription task from the transcripts list, contractors should set the due date in Step 4 to reflect completion of the transcript within a maximum of two days or less from the date the transcription task was claimed. After accessing the transcripts list in Step 1, locating the desired task in Step 2, entering your name in the "Contractor" column in Step 3, and indicating the due date in Step 4, the claimed transcript development should then be finished within the due date indicated of less than two days or unless additional time was approved during claiming due to unusual circumstances.
  
 
==Contracting==
 
==Contracting==
Line 67: Line 67:
 
===Order===
 
===Order===
 
: (For [[Careerprise contractor agreement]])
 
: (For [[Careerprise contractor agreement]])
−
:# The ''Contractor'' shall provide the ''Company'' with scripting services according to the requirements stated on the https://wiki.cnmcyber.com/en/CNMCyber_script page.
+
:# The ''Contractor'' shall provide the ''Company'' with transcription services according to the requirements stated on the https://wiki.cnmcyber.com/en/CNMCyber_transcript page.
−
:# The ''Company'' shall compensate the ''Contractor'' at the rate of $ ___ per minute of the scripted audio.
+
:# The ''Company'' shall compensate the ''Contractor'' at the rate of $ ___ per minute of the transcripted audio.
  
−
===Scripting Tasks===
+
===Transcription Tasks===
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Title !! Event Date !! Video Link !! Duration !! Script Page !! Contractor !! Due Date !! Complete
+
! Title !! Event Date !! Video Link !! Duration !! Transcript Page !! Contractor !! Due Date !! Complete
 
|-
 
|-
−
| Careerprise pitch || 4/9/23 || https://youtu.be/p3PSZLEoRuo || 29:35 || [[Talk:Careerprise pitch]] || Anthony || 8/9/23 ||  Yes
+
| Careerprise pitch || 04/09/23 || https://youtu.be/p3PSZLEoRuo || 29:35 || [[Talk:Careerprise pitch]] || Anthony || 08/09/23 ||  Yes
 
|-
 
|-
 
|-
 
|-
−
| Event scripting requirements || 2/8/23 || https://www.youtube.com/watch?v=pa5zQx5vU6o || 26:03 || [[Talk:CNMCyber event]] ||  || ||  Yes
+
| Event transcription requirements || 02/08/23 || https://www.youtube.com/watch?v=pa5zQx5vU6o || 26:03 || [[Talk:CNMCyber event]] ||  || ||  Yes
 
|-
 
|-
−
| CNMCyber Office Hours requirements (part 2) || 20/7/23 || https://youtu.be/VBp6iJ-YihM || 25:46 || [[Talk:CNMCyber Office Hours]] ||  || ||  Yes
+
| CNMCyber Office Hours requirements (part 2) || 20/07/23 || https://youtu.be/VBp6iJ-YihM || 25:46 || [[Talk:CNMCyber Office Hours]] ||  || ||  Yes
 
|-
 
|-
−
| CNMCyber Office Hours requirements (part 1) || 15/7/23 || https://youtu.be/zcc4f_4qg5A || 25:46 || [[Talk:CNMCyber Office Hours]] ||  || || Yes
+
| CNMCyber Office Hours requirements (part 1) || 15/07/23 || https://youtu.be/zcc4f_4qg5A || 25:46 || [[Talk:CNMCyber Office Hours]] ||  || || Yes
 
|-
 
|-
−
| CNMCyber event requirements || 10/7/23 || https://youtu.be/VgYursiLRoI || 21:48 || [[Talk:CNMCyber event]] ||  || || Yes
+
| CNMCyber event requirements || 10/07/23 || https://youtu.be/VgYursiLRoI || 21:48 || [[Talk:CNMCyber event]] ||  || || Yes
 
|-
 
|-
−
| CNMCyber Development: From hours to contracts || 6/7/23 || https://youtu.be/8KX9Elw-O-0 || 33:12 || [[Talk: Hours to contracts]] || Anthony || 15/9/23 || No
+
| CNMCyber Development: From hours to contracts || 06/07/23 || https://youtu.be/8KX9Elw-O-0 || 33:12 || [[Talk: From hours to contracts]] || Anthony || 15/09/23 || Yes
 
|-
 
|-
−
| CNM Social user-group requirements || 5/7/23 || https://youtu.be/tAFZzBX89R4 || 46:35 || [[Talk:CNM Social]] || || || No
+
| CNM Social user-group requirements || 05/07/23 || https://youtu.be/tAFZzBX89R4 || 46:35 || [[Talk:CNM Social]] || Anthony || 21/09/23 || Yes
 
|-
 
|-
−
| Tech-Board requirements (Part 2) || 5/7/23 || https://youtu.be/Z4eFfsM9IlM || 41:59 || [[Talk:CNM Technology Board]] || Anthony || 17/9/23  || No
+
| Tech-Board requirements (Part 2) || 05/07/23 || https://youtu.be/Z4eFfsM9IlM || 41:59 || [[Talk:CNM Technology Board]] || Anthony || 17/09/23  || Yes
 
|-
 
|-
−
| Website purposes for IA || 29/6/23 || https://youtu.be/7z56_IhZEPk || 38:51 || [[Talk:Website IA]] || || || No
+
| Website purposes for IA || 29/06/23 || https://youtu.be/7z56_IhZEPk || 38:51 || [[Talk:Website IA]] || Anthony || 03/10/23 || Yes
 
|-
 
|-
−
| CNM Tube requirements || 28/6/23 || https://youtu.be/QFhgg8uc1e0 || 54:34 || [[Talk:CNM Tube]] || || || No
+
| CNM Tube requirements || 28/06/23 || https://youtu.be/QFhgg8uc1e0 || 54:34 || [[Talk:CNM Tube]] || Anthony || 10/10/23 || Yes
 
|-
 
|-
−
| This-Week series requirements || 26/6/23 || https://youtu.be/ZtiJ9Ql0-ZI || 33:01 || [[Talk:CNMCyber This Week]] || || || No
+
| This-Week series requirements || 26/06/23 || https://youtu.be/ZtiJ9Ql0-ZI || 33:01 || [[Talk:CNMCyber This Week]] || Anthony || 08/10/23 || Yes
 
|-
 
|-
−
| Website IA sprint || 24/6/23 || https://youtu.be/-l7gJNlinso || 32:07 || [[Talk:CNMCyber.com IA]] || || || No
+
| Website IA sprint || 24/06/23 || https://youtu.be/-l7gJNlinso || 32:07 || [[Talk:CNMCyber.com IA]] || Anthony || 06/10/23 || Yes
 
|-
 
|-
−
| Personas for Friends Of CNM website || 21/6/23 || https://youtu.be/aNSHyvt07U8 || 39:34 || [[Talk:FriendsOfCNM.com IA]] || || || No
+
| Personas for Friends Of CNM website || 21/06/23 || https://youtu.be/aNSHyvt07U8 || 39:34 || [[Talk:FriendsOfCNM.com IA]] || Anthony || 08/10/23 || Yes
 
|-
 
|-
−
| CNMCyber.com IA and IA generally || 15/6/23 || https://youtu.be/7fXkON5rtVw || 27:17 || [[Talk:CNMCyber.com IA]] ||  || || No
+
| CNMCyber.com IA and IA generally || 15/06/23 || https://youtu.be/7fXkON5rtVw || 27:17 || [[Talk:CNMCyber.com IA]] || Anthony || 01/10/23 || Yes
 
|-
 
|-
−
| Tech-Board requirements (Part 1) || 13/6/23 || https://youtu.be/p3GrmsDVbnI || 11:19 || [[Talk:CNM Technology Board]] || Anthony || 16/9/23 || Yes
+
| Tech-Board requirements (Part 1) || 13/06/23 || https://youtu.be/p3GrmsDVbnI || 11:19 || [[Talk:CNM Technology Board]] || Anthony || 16/09/23 || Yes
 
|-
 
|-
−
| Website IA initiation || 8/6/23 || https://youtu.be/inzTVq140mg || 38:29 || [[Talk:Website IA]] || || || No
+
| Website IA initiation || 08/06/23 || https://youtu.be/inzTVq140mg || 38:29 || [[Talk:Website IA]] || Anthony || 04/10/23 || Yes
 
|}
 
|}

Latest revision as of 17:35, 11 October 2023

CNMCyber transcript is technically wording which is used in CNMCyber Office Hours events. In the best case scenario, it should be typed and moved to the requirements.

The transcript can also be defined as the record of someone's requirement.

The transcript is also an intermediate product, it's not a final product. It's a deliverable but is not user deliverable. It's a sub-product. So then when the transcript is available, a wikipage can be developed from the requirements in the transcript.


Transcript Development for CNMCyber Events

Purpose and Importance of Transcription

  • To have a written record of requirements discussed during the event.
  • Support traceability between event discussions and final wiki pages. The transcript itself leads to requirements. The transcript isn't the final product, but the requirements that a customer agrees to become the actual product. This can be measured, and in the best situation, it should be a requirements traceability matrix (RTM) record.
For example, when you write down requirements on a page, imagine it's what you're presenting to your boss or customer. You're saying, "This is what you'll get." You list down everything – like having HumHub, Odoo, Jitsi set up in a certain way, using ProxmoxVE, making it highly available with three nodes, having a public IPv4 network, running on Apache and Nginx, using Ceph for storage, and routing with pfSense. You ask, "Is this what you want?" They either sign or confirm via email. This becomes a kind of blueprint.

Components of a transcript

A transcript should focus on important information, omitting irrelevant details. A transcript should omit things like;
  • "my name is _ _ _"
  • "sorry I need to drink my coffee,"
  • "give me a post I will like,"
  • "I will answer another call."
It's not important. So a transcript should include what is important, what should be and what can be moved to requirements.

Transcription for CNMCyber Events

Transcripts will be developed on wiki project page (currently - discussion page) of the product page. The main page is the product and discussion will be a project. Project (current discussion page), here there will be information how the product was developed and what requirements were involved.

Target Audience and Deliverables

A developer working on the product is the target audience of the transcript. Transcript by itself is the intermediate product, the product page is the end product and transcript is a part of development with a deliverable.

Success Criteria and Desired Outcome

Success for a transcript is determined by how useful it is. The goal is having Wiki Pages that describe products. For example; we need to have this platform on which our Jitsi will work, which is called talk and we will do this conference one day on the Talk.cnmcyber.com slash something - So right now we are doing this on employableU which is temporary. So the end product is the service but to build this firm we need to have a description of what we are doing, what we need to look for, and what we need to do. So now, in this case the desired out come is a working technology.
The technical sense, quality is confirmation the description of the product matches the product itself right. So we have requirements and we have a product. If there's gaps, it's a quality product. But to know that you have a quality product you need to have a description, if you don't have a description how would you know? Transcription is a good way to build this description.

How to claim a transcription task

If you are a contractor developing transcripts for CNMCyber Office Hours you will need to;
  1. Go to Talk:CNMCyber transcript to access the transcription tasks list
  2. Find the title of the task you would like to create a transcript for
  3. In the "Contractor" column on the row for that task, write your name to indicate you will be responsible for this transcript
  4. In the "Due Date" column on the same row, enter the date when you expect the transcript to be completed
  5. Notify your CNMCyber contact when you have claimed a task so they know it is assigned
  6. Develop the transcript according to the description requirements best described on this wiki page
  7. Once complete, notify your CNMCyber contact person.
  8. If you have any questions about the task, get clarification from your CNMCyber contact before claiming and beginning work.

Steps to create a transcript

  1. Transcribe the audio - This can be done manually by listening and typing or if the event is posted on YouTube Channel you can extract the transcript by clicking on the three dots at the bottom right of the video and select show transcript. A side bar will be displayed with the transcript and time stamps. Highlight the entire transcript then copy and paste to the page where you will create the transcript from.
  2. Clean up the transcript - correct any mistakes in the transcription, eliminate timestamps, and filler words such as "um," "hmm," "oh," "like," "you know," "so", as well as any unnecessary side conversations or interruptions that shouldn't be in the final transcript. Also remove any repetitions.
  3. Structure the information - Break the transcript into logical sections using headers. For example, you may have a section for Introduction, topics that were discussed in the meeting
  4. Focus on key points - Summarize the transcript while paying attention to key questions, decisions, and discussion points that are relevant for the requirements of the product.
  5. Review the scrip - Go over the draft transcript and make any final edits to improve clarity. The goal is to create a traceable record of the event that can used to create product requirements.
  6. Stick to the requirements - Make sure the transcript contains the information needed for the product requirements.
  7. Add attributions - Note who said what using speaker attributions like "Kevin:".
  8. Add attribute questions - Note who asked each question using "[Name] asked:".
  9. Add attribute answers - Indicate who provided each answer using "[Name] answered:".
  10. Check accuracy - Verify names, titles, terminology, and facts.
  11. Save the transcript - Save the transcript to the discussion page (project page) of the product being developed.
  12. Ask clarifying questions - Get any needed context before beginning to create the transcript.

Turn around time

When following the steps to claim a transcription task from the transcripts list, contractors should set the due date in Step 4 to reflect completion of the transcript within a maximum of two days or less from the date the transcription task was claimed. After accessing the transcripts list in Step 1, locating the desired task in Step 2, entering your name in the "Contractor" column in Step 3, and indicating the due date in Step 4, the claimed transcript development should then be finished within the due date indicated of less than two days or unless additional time was approved during claiming due to unusual circumstances.

Contracting

Order

(For Careerprise contractor agreement)
  1. The Contractor shall provide the Company with transcription services according to the requirements stated on the https://wiki.cnmcyber.com/en/CNMCyber_transcript page.
  2. The Company shall compensate the Contractor at the rate of $ ___ per minute of the transcripted audio.

Transcription Tasks

Title Event Date Video Link Duration Transcript Page Contractor Due Date Complete
Careerprise pitch 04/09/23 https://youtu.be/p3PSZLEoRuo 29:35 Talk:Careerprise pitch Anthony 08/09/23 Yes
Event transcription requirements 02/08/23 https://www.youtube.com/watch?v=pa5zQx5vU6o 26:03 Talk:CNMCyber event Yes
CNMCyber Office Hours requirements (part 2) 20/07/23 https://youtu.be/VBp6iJ-YihM 25:46 Talk:CNMCyber Office Hours Yes
CNMCyber Office Hours requirements (part 1) 15/07/23 https://youtu.be/zcc4f_4qg5A 25:46 Talk:CNMCyber Office Hours Yes
CNMCyber event requirements 10/07/23 https://youtu.be/VgYursiLRoI 21:48 Talk:CNMCyber event Yes
CNMCyber Development: From hours to contracts 06/07/23 https://youtu.be/8KX9Elw-O-0 33:12 Talk: From hours to contracts Anthony 15/09/23 Yes
CNM Social user-group requirements 05/07/23 https://youtu.be/tAFZzBX89R4 46:35 Talk:CNM Social Anthony 21/09/23 Yes
Tech-Board requirements (Part 2) 05/07/23 https://youtu.be/Z4eFfsM9IlM 41:59 Talk:CNM Technology Board Anthony 17/09/23 Yes
Website purposes for IA 29/06/23 https://youtu.be/7z56_IhZEPk 38:51 Talk:Website IA Anthony 03/10/23 Yes
CNM Tube requirements 28/06/23 https://youtu.be/QFhgg8uc1e0 54:34 Talk:CNM Tube Anthony 10/10/23 Yes
This-Week series requirements 26/06/23 https://youtu.be/ZtiJ9Ql0-ZI 33:01 Talk:CNMCyber This Week Anthony 08/10/23 Yes
Website IA sprint 24/06/23 https://youtu.be/-l7gJNlinso 32:07 Talk:CNMCyber.com IA Anthony 06/10/23 Yes
Personas for Friends Of CNM website 21/06/23 https://youtu.be/aNSHyvt07U8 39:34 Talk:FriendsOfCNM.com IA Anthony 08/10/23 Yes
CNMCyber.com IA and IA generally 15/06/23 https://youtu.be/7fXkON5rtVw 27:17 Talk:CNMCyber.com IA Anthony 01/10/23 Yes
Tech-Board requirements (Part 1) 13/06/23 https://youtu.be/p3GrmsDVbnI 11:19 Talk:CNM Technology Board Anthony 16/09/23 Yes
Website IA initiation 08/06/23 https://youtu.be/inzTVq140mg 38:29 Talk:Website IA Anthony 04/10/23 Yes
Retrieved from "https://pravka.bskol.com/w/index.php?title=CNMCyber_transcript&oldid=118009"