Difference between revisions of "CNMCyber event"

From CNM Wiki
Jump to: navigation, search
(Steps to create a script)
Line 206: Line 206:
 
===Steps to create a script===
 
===Steps to create a script===
 
:#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 script from.   
:#Clean up the transcript - Fix any transcription errors while removing any filler words (Examples; um, hmm, oh, like, you know, so) and side conversations, and interruptions that don't need to be included in the final script.
+
:#Clean up the transcript - Fix any transcription errors, remove the timestamps and any filler words (Examples; um, hmm, oh, like, you know, so) and side conversations, and interruptions that don't need to be included in the final script.
 
:#Structure the information - Break the transcript into logical sections using headers. For example, you may have sections for Introduction
 
:#Structure the information - Break the transcript into logical sections using headers. For example, you may have sections for Introduction
 
:#Focus on key points - Summarize the key questions, decisions, and discussion points that are relevant for the project and remove repetition.   
 
:#Focus on key points - Summarize the key questions, decisions, and discussion points that are relevant for the project and remove repetition.   
 
:#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 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.
:#Save the script - Save the script to the discussion page (project page) of the product being developed.  
+
:#Save the script - Save the script to the discussion page (project page) of the product being developed.
  
 
==Materials==
 
==Materials==

Revision as of 17:56, 8 August 2023

A CNMCyber event (hereinafter, the Event) is any event that matches two conditions: (a) the CNMCyber Team has designed to attract more CNM learners and (b) CNMCyber Customer has approved. Normally, the Events are organized by one or more CNM Event Organizers. Because of their outreach nature, all the Events are open to the general public free-of-charge. The CNMCyber Meetup group and WorldOpp fb-page serve as primary Outreach channels (hereinafter, the Channels).

  • Outreach events, which are the Events organized to promote the Cyber, the Cloud, CNMCyber Team, technologies, needs, and services to outreach to current and potential clients and participants. Specifically to the Coords, the outreach products include CNMCyber This Week events, which are weekly meetings of the Coords who present (a) what they accomplished last week, (b) what they plan to do next week, and (c) what assistance do they need. The outreach events are normally published on the CNMCyber Meetup group.
Moreover, meetings tend to address a number of purposes. For instance, meetings of the CNM Technology Board may touch both product and project features and decisions. When they are open to the general public, they also serve the outreach purpose.
Within the Project results, the outreach events represent project outputs. The other meetings should be considered as project scrap; those meetings are used to develop Documents.


Range of purposes

Any open-to-the-public Event shall contain a pitch to attract promising WorldOpp candidates, Careerprise contractors, Careerprise partners, and/or customers.

Team meetings

Learning seminars

Roundtables

Main wikipage: CNM Cyber roundtable

Standups

Main wikipage: CNM Cyber standup

Seminars

Main wikipage: CNM Cyber seminar

Operations

Pre-event operations

The primary platform to conduct pre-event operations is the designated Channel. Prior to the Event:
  1. Create the event on a Meetup group https://www.meetup.com/techdc/ at least one week in advance (you also should get the group administrator rights). Later, you can copy meetings and change small details and the date. The event should contain the following information:
    1. title (required);
    2. date and time: Time details;
    3. duration: Length;
    4. featured photo: it can be CNMCyber logo and other logos as well as photos from previous events (if they were offline);
    5. description: it should include meeting details and an agenda, you also should add the specific details to be discussed at this particular meeting for each event;
    6. topics: you can pick up to 5 topics. Topics describe what your Meetup event is about in a word or two. They also help show our event to members with matching interests. Select a relevant, but wide range of topics that describe our event. For example: Career Networks, Job Search, Reporting, Recruiting & Hiring, Project Management;
    7. location: the physical location shall have been booked or online room has been created; it is preferable to create a room in CNM Jitsi. There may be problems with CNM Jitsi, so you should have more than 1 alternative video conferencing platform, preferably one internal and one external such as Zoom or Google meet;
    8. allow guests: the number is to be decided, but it's allowed.
  2. If special participants are going to be invited to the Event, they need to be identified, contacted, and confirmed;
  3. All of the Time details and Price details shall be identified and communicated;
  4. The information about the event should add to the CNM Social group;
  5. Recording tool shall have been identified and prepared. You can use this function in CNM Jitsi, Zoom, or Google meet and have at least 2 alternative programs to record just in case such as Xbox Game Bar or OBS Studio, and you should use 2 programs in parallel, for example, recording in CNM Jitsi + OBS Studio (more details: issues). Detailed recording instructions are described below.
  6. The page of this meeting on wiki should be created. It includes a short description of the meeting subject and as well as links to predecessor and successor events, and to Category of this series;
The Host is also responsible for cancelling of the Event if no participant RSVPs.

Live-event operations

The primary platform to conduct event operations is the booked location for onsite Events and CNM Jitsi for online Events. During the Event, the Host shall:
  1. "Meet" and greet the participants;
  2. Facilitate the Event;
  3. Make sure that participants audio, video messages, and chat messages are identified and responded;
  4. Make sure that the Event is recorded.

Post-event operations

The primary platform to conduct post-event operations is CNM Wiki. After the Event,
  1. The recording of the Event shall be posted at https://www.youtube.com/@cnmcyber or https://www.youtube.com/@worldopp6393 YouTube channel and CNM AVideo;
  2. The wikipage shall be composed to include all available data of and about the Event including its minutes and link to its audio- and videorecords, as well as organizing lessons learned;
  3. A follow-up message shall be sent to those Event's participants who RSVPed for the Event.

How to record meetings

We are now practicing the way of recording meetings which includes using a virtual machine for recording so as not to overload your computer. Your steps are as follows:

One-time operations:

  1. Ask Natalia (sysadmin) to give you the remote computer name, user name, and password;
  2. Enter the remote desktop by using the Remote Desktop Connection function on Windows (search -> Remote Desktop Connection);
  3. Type the name of the PC you want to connect to, select Show Options and type your user name, then select Connect. Enter your password and congratulations, you are on the remote desktop.
  4. Upload OBS Studio:
    1. open the browser and visit the OBS Studio homepage;
    2. select the OBS Software instance that Windows supports from the home page and the download will begin automatically;
    3. open the downloaded file once it has been completed and installed;
    4. select the option For screen recording when installing;
  5. When you install the program, there will be many settings that you can adjust, but 1 setting is mandatory for correct recording:
    1. open OBS Studio -> File -> Settings -> Advanced -> Process Priority -> High.

Live-event operations:

  1. Open the remote desktop 10-15 minutes before the meeting;
  2. Open the browser and open CNM Jitsi;
  3. Create a meeting as moderator (you should log in for it);
  4. Start recording in CNM Jitsi:
    1. press the three-dot button;
    2. press the "Start recording" button;
    3. choose the part of the screen;
  5. Start recording in OBS Studio:
    1. open OBS Studio on your computer and click the plus sign in the "Sources" section;
    2. select "Window Capture";
    3. click "Create New", and name the window you are about to capture;
    4. press the "Ok" button, a "Properties Window" will appear, press "Ok" once again on the properties window;
    5. press the "Start Recording" button in the Controls section, and minimize OBS Studio window to proceed with the meeting;
  6. Copy the meeting link and minimize the remote desktop. Now you can attend the meeting from your desktop without worrying about recordings or unstable connections on your home computer;
  7. If you have problems with video quality after recording with OBS Studio, here is the lifehack:
    1. before you start recording, open Task Manager -> Details;
    2. find OBS and right-click -> Set priority -> Real-time;
    3. after the end of the recording, be sure to return the priority to medium;
  8. To finish recording, maximize remote desktop;
  9. Open CNM Jitsi and press the "close access" button, wait until the file is saved and just after that you can close the meeting in CNM Jitsi;
  10. Click the OBS Studio icon on the computer taskbar to maximize the OBS Studio window, press the "Stop Recording" button in the Controls section, the recording is automatically saved on your computer.

How to Stream

Soon we will have several ways of streaming, but for now, here is a description of streaming for the Jitsi + YouTube tandem:
  1. you should be the Youtube channel editor;
  2. click Create on the right side of the top panel and choose Go Live. If you do it the first time, Youtube will ask you to wait 24 hours before you can start streaming;
  3. then you get to YouTube Live Control Room and should choose when you want to go live: Right now and Later date. Let's start right now;
  4. choose Streaming software and press Go and after press "No, it's not made for kids";
  5. you can see the stream setting here: press Edit to choose the title, description, visibility, category, and other settings you need for the stream. After you've set everything up press Save;
  6. on this page you should see the stream key and copy it;
  7. open Jitsi and start the meeting as moderator;
  8. press the three-dot button;
  9. press the Start live stream;
  10. choose the name of live stream and paste the stream key from Youtube and press Start live stream;
  11. end the live stream on Youtube by using End Stream button at the top right and end the meeting on CNM Jitsi;
  12. after that you can edit the video of the meeting in Youtube Studio, so you don't need any additional software to record the conference
  13. you can also schedule streams on the stream setting page in the left sidebar.

Locations

The Events are usually organized simultaneously onsite to accommodate those who needs face-to-face interactions and online to accommodate those attendees who choose to participate remotely. Any onsite Event should be accompanied by an online Event, but not every online Event should be a Event onsite.

Onsite

The onsite events can be organized only if the Host can physically attend the Event or CNMC DevOps Administrator personally is the Host. The Events shall usually be scheduled to occur in any public space such as libraries, restaurants, parks, etc.
By default, the announcements should be published on the designated Channel. They can also be published on the Career Network Ministry meetup group. The cut-off RSVP shall be set at about 24 hours prior to the event and, if no member RSVPed, the onsite location of the Event shall be cancelled, so the Event shall be online only.

Online

  • The Events shall be broadcasted via Jitsi, which is selected as the webconferencing software for the Events. The announcements shall usually be published on http://worldopp.org when such an opportunity is technically available. Until it is, the designated Channel can be temporarily used.
  • If no new attendee RSVPed, the first part of the Event shall be cancelled. If no one, but the Host attends, the Event shall be cancelled.
  • The attendees may or may not choose to use their video; however, the Host shall be visible.

Time details

Start time

The online Events can start at any time. The onsite Events can start at any time between 9am and 7pm EST if organized in the Washington DC metro area. However, no two Events can be planned simultaneously. The Host who organizes the particular Event is supposed to check the calendar of the Group and the FB Page in order to comply.

Length

No length requirements have established yet. Some suggestions can be the following:
  1. From 45 minutes to one hour for online only Events;
  2. From one hour to 90 minutes for onsite Events.

Organizing details

Event host

Main wikipage: CNM Event Organizer
Requirements for the Host are published on the CNM Event Organizer wikipage.

Outreach channels

With regard to the announcement and other communication Channels,
  1. For Open-to-the-Public Events,
CNM Wiki (hereinafter, the Wiki) serves as the main platform for contents of the Events including their minutes and recordings.
Regarding the announcement and communication Channels,
    • When it is launched, CNM Social Office hours channel;
    • The CNMCyber Meetup group; Participants who join through the meetup group will receive prior notification that they will participate in the event via live streaming. If they wish to participate as members, they must attend the CNMCyber Welcome session as a prerequisite.

Calendar

When it is launched, worldopp.org will serve as the official calendar for the Events. The calendars of the Channels can be used temporarily as the calendars.

RSVP options

Open-to-the-Public Events

Unless they are the Host or special guests, participants of those Events that are open to the public shall be invited through the designated Channel, but may choose to participate or not to participate.
Any individual including employment candidates (primarily residing in Kenya and only English speakers for now), aspiring volunteers (primarily residing in the Washington DC metro area), contractors, and partners of the Buyer who is interested in becoming a staffer one day is usually welcome to participate.
The Buyer shall not collect private information such as actual name, social network, Skype and/or email credentials from the participants. During the Events, they may or may not identify or misidentify themselves; their emails and/or other contacts shall not be available for the Host or other participants.

Script Development for CNMCyber Events

What is a script

Script is technically wording which is used in various events for example CNMCyber Office Hours. 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.
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.

Purpose and Importance of Scripting

  • 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 (RTM).
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 monitoring with PF Sense. You ask, "Is this what you want?" They either sign or confirm via email. This becomes a kind of blueprint.

Components of a script

A script should focus on important information, omitting irrelevant details. A script should omit things like;
  • "my name is Gary,"
  • "sorry I need to drink my coffee,"
  • "give me a post I will like,"
  • "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.

Scripting 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.

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.

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.
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.

Steps to create a script

  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 script from.
  2. Clean up the transcript - Fix any transcription errors, remove the timestamps and any filler words (Examples; um, hmm, oh, like, you know, so) and side conversations, and interruptions that don't need to be included in the final script.
  3. Structure the information - Break the transcript into logical sections using headers. For example, you may have sections for Introduction
  4. Focus on key points - Summarize the key questions, decisions, and discussion points that are relevant for the project and remove repetition.
  5. 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.
  6. Save the script - Save the script to the discussion page (project page) of the product being developed.

Materials

Notifications

The Group publishes all the announcement and notifications for onsite Events and the FB Page does so for online Events in order at serves as a hub and/or notice board to reach out to potential and actual participants. Scripting shouldn't include something like; "my name is Gary," or "sorry I need to drink my coffee," or "give me a post I will like," or "I will answer another call." It's not important.

A script should include what is important, what can be moved to the requirements.

Videos and audios

The Wiki publishes all the content of the Event including its specific agenda, minutes and all available recordings. The recordings can also be published on YouTube in order to be available to the general public.

Texts and graphics

The Wiki publishes all the content of the Event including its specific agenda, minutes and all available recordings and, if the recordings are published on YouTube in order to be available to the general public, the links.

Agreement

The following text is based on Careerprise independent contractor agreement and may be used for any agreement to organize one or more CNMCyber events:

CNM Cyber event organizing agreement

This independent contractor agreement (hereinafter, the Agreement) is made and entered into as of 12:04 pm EST, January 1st, 2020 (hereinafter, the Effective Date) between Educaship Alliance LLC (hereinafter, the Company), a Virginia limited liability company, and ___________________________, a [State and business type] (hereinafter, the Contractor; both collectively, the Parties; separately, Party).

The Company requests the Contractor to organize one or more CNMCyber events (hereinafter, the Services) and the Parties therefore agree as follows:

  1. Term and Termination. This Agreement takes effect on the Effective Date, and remains in full force and effect until the Parties accomplish their obligations (hereinafter, the Term). Either Party may terminate this Agreement for any reason or no reason at all by providing the other Party written notice 30 days in advance.
  2. Contractor Services. The Services shall be provided according to the requirements stated at:
    1. https://wiki.cnmcyber.com/en/CNM_Cyber_event as of the Effective Date;
    2. https://wiki.cnmcyber.com/en/CNM_Cyber_seminar as of the Effective Date;
    3. https://wiki.cnmcyber.com/en/CNM_Cyber_Welcome_Webinar as of the Effective Date; and
    4. Schedule stated in Appendix C, which is an inalienable part of this Agreement.
    The Contractor shall provide the necessary equipment to perform the Services. If the Contractor has obtained employees or agents (hereinafter, the Contractor Personnel), the Contractor shall be solely responsible for all costs associated with the Contractor Personnel. As a result of providing the Services, the Contractor or Contractor Personnel may create certain work products (hereinafter, the Work Product). The work performed by the Contractor shall be performed at the rate, stated in Appendix A to this Agreement. The Contractor shall issue invoices to the Company's accounts payable department within 30 days of completing the Services, unless otherwise instructed by the Company, and provide documentation as instructed by the Company's accounts payable department. The Company shall pay to the Contractor within 30 days of receiving the invoice from the Contractor. The Company offers methods of the payments; they are listed in Appendix B to this agreement. The Contractor shall specify the method of the Company's payments. If the Contractor specifies the way, which is not listed in Appendix B, and some third-party fees are associated with that payment way, the Contractor is responsible for those fees. The Services cannot include, rely on, and/or imply any proprietary licenses or commercial restrictions.
  3. Independent Contractor Status. The Parties intend that the Contractor and any Contractor Personnel be engaged as independent contractors of the Company. Nothing contained in this Agreement will be construed to create the relationship of employer and employee, principal and agent, partnership or joint venture, or any other fiduciary relationship. The Contractor may not act as agent for, or on behalf of, the Company, or to represent the Company, or bind the Company in any manner. The Contractor will not be entitled to worker's compensation, retirement, insurance or other benefits afforded to employees of the Company. The Company shall not be responsible for federal, state and local taxes derived from the Contractor's net income or for the withholding and/or payment of any federal, state and local income and other payroll taxes, workers' compensation, disability benefits or other legal requirements applicable to the Contractor.
  4. Ownership. The Contractor transfers and assigns to the Company all rights, titles and interests throughout the world in and to any and all Work Product. This transfer and assignment includes, but is not limited to, the right to publish, distribute, make derivative works of, edit, alter or otherwise use the Work Product in any way the Company sees fit. The Company grants the Contractor, a limited, non-exclusive, non-transferable, non-assignable, royalty free, worldwide license to display the Work Product on a platform personally controlled, in whole or in part, by the Contractor. The Contractor shall notify the Company about the display or displays. The Company may revoke this license at any time by requesting the removal of the Work Product displayed by the Contractor. Upon such request, the Contractor shall remove the Work Product from the platform, and provide written notification of such removal.
  5. Representations. Both Parties represent that they are fully authorized and empowered to enter into this Agreement, and that the performance of the obligations under this Agreement will not violate or infringe upon the rights of any third-party, or violate any agreement between the Parties and any other person, firm or organization or any law or governmental regulation.
  6. Indemnification. The Contractor shall defend, indemnify, and hold harmless the Company, its affiliates, and its respective officers, directors, agents and employees from any and all claims, demands, losses, causes of action, damage, lawsuits, judgments, including attorneys' fees and costs, arising out of, or relating to, the Contractor's representation and services under this Agreement.
  7. Confidential Information. Excluded.
  8. Communications. All the communications between the Parties that are related to this Agreement may and tend to occur electronically. The email communication is official and can be presented during possible litigation. The Parties' email addresses are stated in Appendix C to this Agreement. If any Party would like to change its email address, that Party shall notify another Party before the change.
  9. Limited Warranty. The Contractor does not provide any warranty that operation of any services hereunder will be uninterrupted or error-free. The Contractor warrants that all services are be performed in a professional manner in accordance with generally applicable industry standards and laws. That provision includes, but not limited to, the respect to third-party intellectual properties, etc. Between the Parties, the Contractor's sole liability (and the Company's exclusive remedy) for any breach of this warranty shall be for the Contractor to re-perform any deficient services, or, if the Contractor is unable to remedy such deficiency within thirty (30) days, to void the invoice for the deficient services. The Contractor shall have no obligation with respect to a warranty claim if the claim is the result of third-party hardware or software malfunctioning, the actions of the Company or some other party or is otherwise caused by factors outside the reasonable control of the Contractor. This section 9 is a limited warranty, and sets forth the only warranties made by any Party. Any Party makes no other warranties, conditions, or undertakings, express or implied, statutory or otherwise, including but not limited to warranties or merchantability, fitness for a particular purpose or non-infringement or any warranties regarding the performance of anything provided or installed by the Contractor.
  10. Miscellaneous Provisions. This Agreement, and any accompanying appendices, requirement pages, duplicates, or copies, constitutes the entire agreement between the Parties with respect to the subject matter of this Agreement, and supersedes all prior negotiations, agreements, representations, and understandings of any kind, whether written or oral, between the Parties, preceding the date of this Agreement. This Agreement may be amended only by written agreement duly executed by an authorized representative of each party. If any provision or provisions of this Agreement shall be held unenforceable for any reason, then such provision shall be modified to reflect the Parties' intention. All remaining provisions of this Agreement shall remain in full force and effect for the duration of this Agreement. This Agreement shall not be assigned by either party without the express consent of the other party. A failure or delay in exercising any right, power or privilege in respect of this Agreement will not be presumed to operate as a waiver, and a single or partial exercise of any right, power or privilege will not be presumed to preclude any subsequent or further exercise, of that right, power or privilege or the exercise of any other right, power or privilege. This Agreement is be governed by and construed in accordance with the laws of the State of ­­­­­­­­­­­­Virginia without reference to any principles of conflicts of laws, which might cause the application of the laws of another state. Any action instituted by either party arising out of this Agreement will only be brought, tried and resolved in the applicable federal or state courts having jurisdiction in the State of Virginia. Each Party hereby consents to the exclusive personal jurisdiction and venue of the courts, state and federal, having jurisdiction in the State of Virginia.

The Parties are signing this Agreement electronically on the dates stated below.

Educaship Alliance LLC; by: GARY IHAR; name, title: Gary Ihar, director; date: January 7th, 2020

[CONTRACTOR NAME]; by: ________________________________; name: ________________; title:

See also

Related lectures

Archive