Difference between revisions of "CNM Technology Board"
(→Current endeavors) |
|||
| (17 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | The [[CNM Technology Board]] (hereinafter, the ''Board'') is a type of [[CNM events|event]] where [[CNMCyber Team]] discuss and solve current technical [[CNMCyber]] problems. Formerly, [[CNM Technology Board]] was the strategic division of [[CNMCyber Team]] that (a) approves requirements for [[WorldOpp Fellow Staff]] and (b) supervises other divisions of the ''Team''. | + | The [[CNM Technology Board]] (alternatively known as [[CNM TechBoard]]; hereinafter, the ''Board'') is a type of [[CNM events|event]] where [[CNMCyber Team]] discuss and solve current technical [[CNMCyber]] problems. Formerly, [[CNM Technology Board]] was the strategic division of [[CNMCyber Team]] that (a) approves requirements for [[WorldOpp Fellow Staff]] and (b) supervises other divisions of the ''Team''. |
| Line 7: | Line 7: | ||
*Natalia -- system administrator | *Natalia -- system administrator | ||
*Sonya - host | *Sonya - host | ||
| − | + | *Kevin - host | |
===Meetings=== | ===Meetings=== | ||
Once a week | Once a week | ||
| Line 23: | Line 23: | ||
===... team's endeavors=== | ===... team's endeavors=== | ||
| − | :The ''Board'' approves or disapproves the strategy for the development of [[CNMCyber]] known as [[CNM Digital Transformation]]. | + | :The ''Board'' approves or disapproves the strategy for the development of [[CNMCyber]] known as [[CNM Digital Transformation]]. The ''Board'' is responsible for overseeing the current state of technology initiatives, addressing the challenges, and brainstorm potential solutions. |
===... team's services=== | ===... team's services=== | ||
| Line 29: | Line 29: | ||
===... the technology=== | ===... the technology=== | ||
| − | :The ''Board'' defines the [[ | + | :The ''Board'' defines the [[Opplet]], which is the bundle of technology that supports [[CNMCyber]]. |
==Current endeavors== | ==Current endeavors== | ||
===Meeting sofware=== | ===Meeting sofware=== | ||
| − | :The ''Board'' would like to have a stable working instance of the [[ | + | :The ''Board'' would like to have a stable working instance of the [[Educaship Jitsi]] and solve the challenges described [[Educaship Jitsi#Challenges|here]]. The ''Board'' published the job post on Upwork to hire a Jitsi expert. |
===Wiki software=== | ===Wiki software=== | ||
| − | :The ''Board'' would like to solve the [[ | + | :The ''Board'' would like to solve the [[Educaship MediaWiki]] challenges described [[Educaship MediaWiki#Challenges|here]]. The ''Board'' published the job post on Upwork to hire a MediaWiki expert. |
:Thus, the ''Board'' shall: | :Thus, the ''Board'' shall: | ||
| Line 46: | Line 46: | ||
===Registration (WSO2)=== | ===Registration (WSO2)=== | ||
| − | :The [[CNM Technology Board#Registration|CNM Registration Project]] was solved by integration [[ | + | :The [[CNM Technology Board#Registration|CNM Registration Project]] was solved by integration [[Educaship LDAP]] into the apps. But now the ''Board'' considered migration to the [[WSO2 IS]]-based integration and wasn't sure whether LDAP would remain necessary. |
| + | |||
| + | ===Proxmox=== | ||
| + | :The ''Board'' encountered a problem with the [[Educaship Proxmox]]. The problem turned out to be in the [[Educaship Ceph]] repository. It has lost metadata and our bare metals are inaccessible. Now a new [[ProxmoxVE]] instance has been installed on the ZFS storage. | ||
| + | |||
| + | ===CNM Odoo=== | ||
| + | |||
| + | ===CNM Humhub=== | ||
| − | === | + | ===Streaming=== |
| − | |||
==Previous/solved endeavors== | ==Previous/solved endeavors== | ||
| Line 55: | Line 61: | ||
:''Main wikipage: [[CNM Registration Project]]'' | :''Main wikipage: [[CNM Registration Project]]'' | ||
| − | :The [[CNM Registration Project]] aims to create a user-friendly process for registration of new volunteers and [[Certified | + | :The [[CNM Registration Project]] aims to create a user-friendly process for registration of new volunteers and [[KSA Certified Digital Operator]]s. Particular problems to be solved are: |
:*Real accounts to database so user updates can happen with database | :*Real accounts to database so user updates can happen with database | ||
:*Define how usability testing happens | :*Define how usability testing happens | ||
| Line 74: | Line 80: | ||
===Team's server(s)=== | ===Team's server(s)=== | ||
| − | :''Main wikipage: [[CNM | + | :''Main wikipage: [[CNM Lab Farm]]'' |
| − | :The [[Friends Of CNM]] runs the [[CNM Cloud Project]] designed to develop [[ | + | :The [[Friends Of CNM]] runs the [[CNM Cloud Project]] designed to develop [[Opplet]]. Currently, the [[CNM Bureau Farm]] handle [[CNMCyber]]. The [[Friends Of CNM]] makes a learning and testing variant of the [[CNM Bureau Farm]], called the [[CNM Lab Farm]], available to the ''Team''. Its system administrator is responsible for implementing the ''Board's'' decisions including permissions. |
:Upon the ''Board's'' decision, the [[Friends Of CNM]] is also committed to deploying another server for the ''Team's'' special projects such as deployment of [[Tiki Wiki CMS Groupware]], etc. | :Upon the ''Board's'' decision, the [[Friends Of CNM]] is also committed to deploying another server for the ''Team's'' special projects such as deployment of [[Tiki Wiki CMS Groupware]], etc. | ||
| Line 83: | Line 89: | ||
===Recruiting=== | ===Recruiting=== | ||
| − | :The ''Board'' would like to document its recruiting process from sourcing and up to onboarding, as well as best practices and/or recommendations for future. Particularly, [[EmployableU | + | :The ''Board'' would like to document its recruiting process from sourcing and up to onboarding, as well as best practices and/or recommendations for future. Particularly, [[EmployableU Concepts]] and instructions for beginner program coordinators (officially known as [[CNMCyber Coordinator]]s) as part of on-boarding process shall be created. |
===Mentoring=== | ===Mentoring=== | ||
| Line 98: | Line 104: | ||
:*https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-163r1.pdf | :*https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-163r1.pdf | ||
| − | ==Events== | + | ==Archive of Events== |
| − | + | [[:Category:CNM Tech Board Meetings]] | |
| − | |||
| − | : | ||
| − | : | ||
| − | |||
| − | |||
| − | |||
==Q&As== | ==Q&As== | ||
Latest revision as of 15:41, 29 May 2024
The CNM Technology Board (alternatively known as CNM TechBoard; hereinafter, the Board) is a type of event where CNMCyber Team discuss and solve current technical CNMCyber problems. Formerly, CNM Technology Board was the strategic division of CNMCyber Team that (a) approves requirements for WorldOpp Fellow Staff and (b) supervises other divisions of the Team.
Contents
Organization
Key members
- Gary Ihar -- gary
- Natalia -- system administrator
- Sonya - host
- Kevin - host
Meetings
Once a week
Decisions
Majority; а week for a decision
Methodologies
- Main wikipage: CNM Agile
- We need someone to own tasks. If you own it and can do it all, great. If you will need more than one person on it, that should be noted once we have the tasks in the wiki or via response to this if necessary. For example, MichaelC was looking for someone that would like to do some of the work under his direction for the training task as it can be a very useful learning experience as a software evaluation using a bake-off is a common practice.
Deciding on ...
... team's culture
... team's endeavors
- The Board approves or disapproves the strategy for the development of CNMCyber known as CNM Digital Transformation. The Board is responsible for overseeing the current state of technology initiatives, addressing the challenges, and brainstorm potential solutions.
... team's services
- The Board defines the portfolio of the services included into CNMCyber and the technology behind the services.
... the technology
Current endeavors
Meeting sofware
- The Board would like to have a stable working instance of the Educaship Jitsi and solve the challenges described here. The Board published the job post on Upwork to hire a Jitsi expert.
Wiki software
- The Board would like to solve the Educaship MediaWiki challenges described here. The Board published the job post on Upwork to hire a MediaWiki expert.
- Thus, the Board shall:
- Research documents on competitive packages. The results of this research shall be posted at the wiki engine document.
- Identify criteria to select a better-suited software package.
- Select 2-5 software packages to be evaluated more closely.
- Deploy the selected packages and evaluate them in order to make a decision to either migrate or combine the current MediaWiki instance with another software package or anything else.
Registration (WSO2)
- The CNM Registration Project was solved by integration Educaship LDAP into the apps. But now the Board considered migration to the WSO2 IS-based integration and wasn't sure whether LDAP would remain necessary.
Proxmox
- The Board encountered a problem with the Educaship Proxmox. The problem turned out to be in the Educaship Ceph repository. It has lost metadata and our bare metals are inaccessible. Now a new ProxmoxVE instance has been installed on the ZFS storage.
CNM Odoo
CNM Humhub
Streaming
Previous/solved endeavors
Registration
- Main wikipage: CNM Registration Project
- The CNM Registration Project aims to create a user-friendly process for registration of new volunteers and KSA Certified Digital Operators. Particular problems to be solved are:
- Real accounts to database so user updates can happen with database
- Define how usability testing happens
- Registration of new volunteers on wiki
- The initial registration function has been developed at CNM Cabin; however, it lacks its email confirmation since the text of the confirmation email hasn't been developed yet. The requirements for the complete registration have been developed, published on the CNM Registration Project wikipage and are waiting for their approval.
Product backlog
- Main wikipage: CNM Cyber requirements
- The Board would like to create a product backlog as a document or a set of documents on wiki with the tasks, who is lead on task and link to work on task.
- Ken is willing to take that task. For that he should be able to complete initial draft during a 1-hour working session on a Tuesday night. (If necessary, it could be done with much less time as a copy-paste from this email, but he would hope to have better quality than that.)
- This backlog document shall contain relevant user stories, so the task is to begin the process of creating project requirements in the form of user stories on one or more wiki pages. Each user story has a user story card which has a notes section with status information. Here is some information about that. The backlog email is a list of short descriptions of tasks or projects with some status information. That is a good place for us to start. Frequently Agile projects or Hybrid-Agile projects have task cards and/or story-cards describing the tasks to be completed. The tasks are often given as user stories in a certain form. (Sometimes these are on actual large index cards or post-it notes, but often they are on electronic task cards in a system like JIRA or a wiki or some other project management software system.)
- So requirements are often actually "Agile Stories" describing the desired outcome at very high level in the form of completing the blanks in this sentence: "As a [blank <type-of-user>] I want [blank <some-goal-or-objective>] so that [blank <benefit-or-value>]". Example from government website: "As an Editor, I want a way to review content before it is published so that I can assure it is optimized with correct grammar and tone." [Retrieved from public website https://tech.gsa.gov/guides/user_story_example/ ]. All this is simpler when you see it than when you try to understand it from a descriptive paragraph.
Team's server(s)
- Main wikipage: CNM Lab Farm
- The Friends Of CNM runs the CNM Cloud Project designed to develop Opplet. Currently, the CNM Bureau Farm handle CNMCyber. The Friends Of CNM makes a learning and testing variant of the CNM Bureau Farm, called the CNM Lab Farm, available to the Team. Its system administrator is responsible for implementing the Board's decisions including permissions.
- Upon the Board's decision, the Friends Of CNM is also committed to deploying another server for the Team's special projects such as deployment of Tiki Wiki CMS Groupware, etc.
- The Board needs to define the process of granting and changing permissions.
Recruiting
- The Board would like to document its recruiting process from sourcing and up to onboarding, as well as best practices and/or recommendations for future. Particularly, EmployableU Concepts and instructions for beginner program coordinators (officially known as CNMCyber Coordinators) as part of on-boarding process shall be created.
Mentoring
- The Board would like to create the Team's mentor-protégé program for those recruits who have succeeded in their CNMCyber Coordinator roles. MichaelC can mentor some learner in cyber-security, while Gary Ihar can mentor some learner in project administration.
- Technical links/sources as part of mentoring process: NIST Security Links:
- https://csrc.nist.gov/
- https://www.nist.gov/cyberframework
- https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.04162018.pdf
- https://www.nist.gov/sites/default/files/documents/2017/04/03/baldrige-cybersecurity-excellence-builder-v1.0.pdf
- https://csrc.nist.gov/CSRC/media/Publications/sp/800-171/rev-2/draft/documents/sp800-171r2-draft-ipd.pdf
- https://csrc.nist.gov/CSRC/media/Publications/sp/800-171b/draft/documents/sp800-171B-draft-ipd.pdf
- https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-171A.pdf
- https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-163r1.pdf
Archive of Events
Category:CNM Tech Board Meetings
Q&As
- I love to hear about the Board. Please tell me more.
- Scroll to the top of this page and read. Ask specific questions when you have those.
