Difference between revisions of "CNM Tech Board 2023-12-28"

From CNM Wiki
Jump to: navigation, search
(→‎Community to pivot)
(→‎Farms to review)
Line 14: Line 14:
 
===Farms to review===
 
===Farms to review===
 
:* '''Task''' (critical): To review [[Opplet Infrastructure]] in order to suggest optimization paths before each of the farms would be optimized further.
 
:* '''Task''' (critical): To review [[Opplet Infrastructure]] in order to suggest optimization paths before each of the farms would be optimized further.
−
:* '''Situation''': We have been developing [[CNM Farms]] for many years, but have never really optimized it. Over the years, we generated many [[DNS record]]s that are no longer in use and just generate security vulnerabilities. We also created a few resources that require payments, but no longer produce any value. Kevin proposed forming a Finance Board or Financial Oversight Committee that would table, say, any new purchase or payment for discussion and expected returns from this investment, budgeting, identifying cost-saving opportunities, and any other matter that involves purchase and payment. Gary feels like those tasks can be done within the existing board. At the same time, Gary believes that every of "infrastructure" wikage -- [[Bureau Infrastructure]], [[Lab Infrastructure]], [[Campus Infrastructure]], and [[Fed Infrastructure]] -- shall have its platform resource description, the current expense report, [[DNS record]]s, [[web server]] files, and [[business need]]s. Gary has already published the expense reports.
+
:* '''Situation''': We have been developing [[CNM Farms]] for many years, but have never really optimized it. Over the years, we generated many [[DNS record]]s that are no longer in use and just generate security vulnerabilities. We also created a few resources that require payments, but no longer produce any value. Kevin proposed forming a Finance Board or Financial Oversight Committee that would table, say, any new purchase or payment for discussion and expected returns from this investment, budgeting, identifying cost-saving opportunities, and any other matter that involves purchase and payment. Gary feels like those tasks can be done within the existing board. At the same time, Gary believes that<ol type="a"><li>Every of "infrastructure" wikage -- [[Bureau Infrastructure]], [[Lab Infrastructure]], [[Campus Infrastructure]], and [[Fed Infrastructure]] -- shall have its description of rented resources, the current expense report, and [[business need]]s. Gary has already published the expense reports.</li><li><li>Every of "farm" wikage -- [[CNM Bureau Farm]], [[CNM Lab Farm]], and [[CNM Campus Farm]], -- shall have its software description, [[DNS record]]s, [[web server]] files, and [[business need]]s.</li></ol>
 
:* '''Action decisions''':
 
:* '''Action decisions''':
 
:*# Natalia will summarize actual resources to compare against the expenses.
 
:*# Natalia will summarize actual resources to compare against the expenses.

Revision as of 22:28, 23 December 2023

CNM Tech Board 2023-12-28 is the meeting of CNM Technology Board‎ that occurred on December 28th, 2023. The predecessor meeting is CNM Tech Board 2023-12-21; the successor meeting is CNM Tech Board 2024-01-04.


Critical priority

All of "old" businesses are related to launch of iDosvid in Kenya in order to make iDosvid pitch real.

Elementor to retire

  • Task (critical): To retire Elementor by April 2024
  • Situation: In order to save costs, we would like to retire Elementor that we barely use. Our primary websites that deploy Elementor are https://vebka.theeconomicgroup.com/ and https://scheje.com/ . The current subscriptions expire in April of 2024.
  • Action decisions:
    1. Gary will move the movable contents to other CNM WordPress instances.
    2. Gary will assess whether we need to hire any contractors to move the unmovable parts.

Farms to review

  • Task (critical): To review Opplet Infrastructure in order to suggest optimization paths before each of the farms would be optimized further.
  • Situation: We have been developing CNM Farms for many years, but have never really optimized it. Over the years, we generated many DNS records that are no longer in use and just generate security vulnerabilities. We also created a few resources that require payments, but no longer produce any value. Kevin proposed forming a Finance Board or Financial Oversight Committee that would table, say, any new purchase or payment for discussion and expected returns from this investment, budgeting, identifying cost-saving opportunities, and any other matter that involves purchase and payment. Gary feels like those tasks can be done within the existing board. At the same time, Gary believes that
    1. Every of "infrastructure" wikage -- Bureau Infrastructure, Lab Infrastructure, Campus Infrastructure, and Fed Infrastructure -- shall have its description of rented resources, the current expense report, and business needs. Gary has already published the expense reports.
    3. Every of "farm" wikage -- CNM Bureau Farm, CNM Lab Farm, and CNM Campus Farm, -- shall have its software description, DNS records, web server files, and business needs.
  • Action decisions:
    1. Natalia will summarize actual resources to compare against the expenses.
    2. Gary will copy DNS records to analyze.
    3. Natalia will copy web server files to analyze.
    4. We will move Fed Infrastructure into Bureau Infrastructure
    5. Kevin will suggest the action plan for cost savings

GitLab to collaborate

  • Task (critical): To create the single platform for technology collaborations
  • Situation: Over the last years, unstructured onboarding of new technology contractors and collaboration of existing developers significantly slowed the development. Plus, we use no specialized tool to report bugs and issues, while relying on emails mostly. A couple of years ago, Natalia and Gary used Redmine, but later decided to switch to CNM GitLab. GitLab features software repository and, therefore, allows for file upload and version control; we don't plan to get rid of that software. The discussion is about its extension. GitLab features its own modules such as GitLab Issues (to manage and track tasks, bugs, and other project-related activities) and GitLab Boards (to visualize and manage our project tasks in a board format), as well as several integrations with standalone project management software such as Taiga or Redmine.
  • Action decisions:
    1. Natalia will evaluate the alternatives and report her findings.

HumHub to cultivate

  • Task (critical): To deliver CNM HumHub as the primary tool for initial engagement with the students.
  • Situation: Traditionally, a pair of CNM Moodle and CNM MediaWiki was used for initial engagement with the students. However, both of those tools lack social interaction, particularly, in meeting organizing. CNM HumHub looks like a way better tool. For CNMCyber Event-Driven Projects practice specifically, we have added the "Meetings" module. Kevin planned to suggest the action plan, but he lacks power-user permissions.
  • Action decisions:
    1. Natalia will grant power-user permissions to Kevin
    2. Natalia will create an experimental HumHub instance on CNM Lab Farm and grant Kevin administrator-level permissions, so he can experiment without worrying about CNM Social
    3. Kevin will review the issues and propose the action plan.

Recording to improve

  • Task (critical): To make recording tools available to the students
  • Situation: We have been trying to find a safe way of meeting recording for a while. Initially, we recorded CNM Jitsi sessions using own device software and, later, published it. That way came with multiple drawbacks such as (a) it depends on the recording person's connectivity. If the recording person is disconnected, the recording is interrupted; (b) it consumes the recording person's data transfer, which can be costly; (c) it depends on the recording person's device and makes impossible to record the sessions using smartphones for instance. While trying to record the sessions via VMs on CNM Lab Farm, we encountered two issues: (1) the recordings had some interruptions and (2) VMs went into sleeping modes. To make the newly-developed recording practical, we plan to use it for meetings of CNM Technology Board.
  • Action decisions:
    1. Kevin will review the issues and propose the action plan.

Revenue to plan

  • Task (critical): To identify the ways for revenue generation
  • Situation: Budget limitations have been slowing the development for a while. Although financing is not a technology issue, our technology shall be oriented on sales. For now, we build full-scope vocational orientation services, which will take at least a year to build and another year to sell. They are too big to be sold fast. The simpler the product, the faster the sales. Besides the products themselves, we also need (a) marketing to bring customers aboard for which we can particularly use CNMCyber Meetup group, (b) website and events to educate customers, and (c) payment option and assisting folks to charge and serve. With regards to those products, we may explore:
    1. Short hands-on training sessions via #Training to offer.
    2. Paid career days, other derivatives from Educaship pitch offerings, and add-ons such as paid certificates. For instance, emphasizing that students fulfilling program requirements will receive a notification of completion and, in turn, have the opportunity to obtain a certificate by paying a designated fee. Derivatives may include trips to Africa and other countries.
    3. Career counseling and other services. More ideas are expressed in Talk:The Economic Group.
  • Action decisions:
    1. Kevin will review the issues and propose the action plan.

Tech prototype to MVP

  • Task (critical): To define MVP of sandboxes that shall emulate workplaces for the students.
  • Situation: We have developed a range of technologies that we can offer our students for practice. However, we don't know at this moment what we shall offer initially and, therefore, what we are missing. Gary developed an initial draft on the Educaship pitch wikipage, but this draft needs reviews.
  • Action decisions:
    1. Kevin will review Gary's draft.
    2. Natalia will review Kevin's draft.
    3. If we bring a school tech lady aboard via #Community to pivot, she may review Natalia's draft.
    4. Based on the latest draft, we will decide the scope of the sandbox MVP.

Wiki to public

  • Task (critical): To move public contents from CNM MediaWiki.
  • Situation: CNM MediaWiki no longer satisfies us because of its (a) lack of CNM LDAP integration, so new students cannot access the wiki, and (b) weak mobile-friendly design. We assessed several wiki engines and are ready to make decisions.
  • Action decisions:
    1. We shall use CNM Social/CNM HumHub's wiki as our primary vehicle to deliver public contents.
    2. We shall keep XWiki in mind for its possible applications to our development and/or advanced training.
    3. We shall keep Wiki.js in mind for its possible applications to our website development training.
    4. We shall use BookStack as our marketing vehicle for EmployableU Concepts.
    5. We shall continue deploying CNM MediaWiki as our legacy system.
    6. If we build demonstrations for wiki engines, we may utilize BlueSpice.

WordPress to populate

  • Task (critical): To position our services on the market.
  • Situation: We are getting closer to our MVP, so we can start positioning our services on the market. This may help attract both potential customers and staffers. Natalia set up several CNM WordPress instances.
  • Action decisions:
    1. Gary will start populating those instances that Natalia has set up.

Critical, but depended

For the purposes of this meeting, Critical, but depended refers to those endeavors that literally have #Critical priority, but which execution depends on other projects.

Bureau to optimize

  • Task (critical, but having dependencies to be resolved): To optimize Bureau Infrastructure
  • Situation: CNM Bureau Farm is the newest farm within Opplet Infrastructure. It features a cluster that is built on the top of three bare-metal servers using ProxmoxVE. Initially, we plan to use this cluster to host CNM Social, CNM Corp, and CNM Talk. However, the CNM Talk instance is not yet performing as desired. We may consider optimizing it or moving it to another farm. Our competencies are not enough to continue and we need to bring external experts. Equally importantly, launching full-scale production on the "Bureau Farm" may allow for transfer of Opplet.net and, in the future, WSO2 IS to this farm.
  • Action decisions: Until we complete #Farms to review, the project is postponed.

Campus to optimize

Community to pivot

Lab to optimize

  • Task (critical, but having dependencies to be resolved): To optimize Lab Infrastructure
  • Situation: CNM Lab Farm is a legacy CNM Bureau Farm before it was clustered. When the cluster was created, its non-clustered node was called "Lab Farm". By their definition, clusters require more resources; the "Lab Farm" shouldn't host any critical instances. It is vital to state that a big number of virtual machines (VMs) would require #VMs to automate some day.
  • Action decisions: Until we complete #Farms to review, the project is postponed.

Training to offer

  • Task (critical, but having dependencies to be resolved): To launch short-term hands-on training
  • Situation: From our experience, short-term hands-on training sessions sold the fastest. "Short-term" implies anything from 90 minute sessions and up to packages of several sessions totaling 35 hours. "Hands-on" implies practical tasks during technology-based training. The training can be:
    1. Built and delivered by us. Particularly, it may relate to the technology that we use. Our professional groups such as CNM Proxmox Users, CNM Jitsi Users, and CNM TensorFlow Users can be instrumental.
    2. Built by someone else, but delivered by us. Recently, artificial intelligence (AI) also gains its grounds and many people are interested in obtaining some background. We are discussing opportunities to use partners' content and practices to introduce AI in our markets. In addition, a few software developers make their content available for learning. For instance, these are Odoo's resources -- https://www.odoo.com/slides/all/ . We can further augment those resources with our practical tasks.
    3. Built and delivered by partners. Traditionally, we teamed up with partners to offer preparation for credential exams in PMP, ITIL, and so on. Especially, we are interested in those who were accredited by credentialing authorities.
  • Action decisions: Until #Revenue to plan tasks are resolved, the project is postponed.

Non-critical priority

Clusters to document

  • Task (non-critical): To document clusters of Opplet
  • Situation: During 2023, we have rebuilt CNM Bureau Farm and CNM Campus Farm into clusters. Their optimization undergoes under the #Farms to optimize project. However, they also need to be documented, particularly because the students will need that documentation during their operational practice.
  • Action decisions: Until #Farms to optimize tasks are resolved, the project is postponed.

Committee to advise

  • Task (non-critical): To build our expertise in work with youth, as well as with high schools and other youth organizations
  • Situation: Our expertise in work with youth and youth organizations is limited. To attract experts, we would like to create a body, either an organization or a group. At the same time, those experts shall be advocates for smoothing of school-to-work transitions, so a working name for that body is International Council for Vocational Orientation.
  • Action decisions: Until #Critical priority tasks are resolved, the project is postponed.

Email fields to hide

  • Task (non-critical): To hide email fields from the registration, while offering to submit emails voluntarily through Opplet.net
  • Situation: Historically, email fields in the Opplet.net registration confuse the applicants. We plan to alternate the model; however, no developer is available at the moment. Gary wrote the initial code, which later was re-written by Sergey Zlomovsky. Then, Roman F. moved the code into the Yii framework. Gary failed to find Sergey. Natalia contacted Roman, but his original interest didn't fruit a solution. Now, we will look for new freelancers.
  • Action decisions: Until #Critical priority tasks are resolved, the project is postponed.

Help desks to create

  • Task (non-critical): To create help desks
  • Situation: Kevin raised an issue of help desks. Indeed, our customers and staffers need to have direct channels of bug reporting and troubleshooting. One, technical help desk should be delivered via the #GitLab to collaborate project; Natalia will serve it. For non-technical help desk, we plan to use a module of CNM Odoo.
  • Action decisions: Until #Critical priority tasks are resolved, the project is postponed.

Odoo to explore

  • Task (non-critical): To deliver CNM Odoo as the primary tool for advanced engagement with the volunteers, staffers, and whomever are engaged with the enterprise.
  • Situation: As of December 2023, we don't deploy any ERP or another software that makes a company a company. For instance, our staffer candidates haven't applied for a job via the company's website, the staffers don't use the company's email and don't report work hours. Furthermore, we will not be able to function when we get to sales and accounting.
  • Action decisions: Until #Critical priority tasks are resolved, the project is postponed.

No priority backlog

Cloudflare to utilize

LDAP to upgrade

  • Task (no priority): To upgrade CNM LDAP
  • Situation: Since its deployment in 2017, CNM LDAP was never revised, upgraded, nor optimized. Particularly, we missed OpenLDAP Long Term Support Release 2.5.16.
  • Action decisions: Until #Non-critical priority tasks are resolved, the project is postponed.

LMS to practice

Meetings to live-stream

Servers to mail

  • Task (no priority): To advance mail servers from prototypes to MVPs
  • Situation: Natalia has set up three mail servers -- mail.opplet.net, mail.bskol.com, mail.cnmcyber.com. However, we haven't revised, optimized, or integrated them with other of our applications but Opplet.net.
  • Action decisions: Until #Non-critical priority tasks are resolved, the project is postponed.

PHP to review

  • Task (no priority): To review PHP support at Opplet
  • Situation: Since its deployment in 2017, CNM PHP was never revised, upgraded, nor optimized. PHP troubles emerged a few times, particularly in connection with CNM MediaWiki.
  • Action decisions: Until #Non-critical priority tasks are resolved, the project is postponed.

Time to track

  • Task (no priority): To track time of volunteers and staffers
  • Situation: To emulate corporate work environment, we would like to track work time of volunteers and staffers, tentatively, while they are using virtual machines (VMs).
  • Action decisions: Until #Non-critical priority tasks are resolved, the project is postponed.

VMs to automate

VPN and proxy

WSO2 IS

Retrieved from "https://pravka.bskol.com/w/index.php?title=CNM_Tech_Board_2023-12-28&oldid=128728"