Add security policy, roadmap, and overall edit

tanto259 · tanto259 · commit 84bc2844252b · 2021-12-06T23:34:47.000+08:00
Signed-off-by: Hartanto Ario Widjaya &lt;tanto259@users.noreply.github.com&gt;
diff --git a/COMMITTERS.csv b/COMMITTERS.csv
@@ -1,10 +1,10 @@
-Name,Email,GitHub ID
-Sudharsana Srinivasan,Sudharsana.Srinivasan@ibm.com,Sudharsana-Srinivasan
-Martin Keen,mkeen@us.ibm.com,martinkeen
-John Mertic,jmertic@linuxfoundation.org,jmertic
-Paul Newton,paulnewt@us.ibm.com,paulnewt
-Michael Bauer,Michael.Bauer2@broadcom.com,MikeBauerCA
-Jessielaine Punongbayan,Jessielaine.Punongbayan@broadcom.com,jellypuno
-Zeibura Kathau,Zeibura.Kathau@broadcom.com,zeibura
-Hartanto Ario Widjaya,hartanto@securitypuppy.com,tanto259
-Joe Winchester,winchest@uk.ibm.com,Joe-Winchester
+Name,Email,GitHub ID,Role
+Sudharsana Srinivasan,Sudharsana.Srinivasan@ibm.com,Sudharsana-Srinivasan,Lead
+Michael Bauer,Michael.Bauer2@broadcom.com,MikeBauerCA,Co-Lead
+Martin Keen,mkeen@us.ibm.com,martinkeen,
+John Mertic,jmertic@linuxfoundation.org,jmertic,
+Paul Newton,paulnewt@us.ibm.com,paulnewt,
+Jessielaine Punongbayan,Jessielaine.Punongbayan@broadcom.com,jellypuno,
+Zeibura Kathau,Zeibura.Kathau@broadcom.com,zeibura,
+Hartanto Ario Widjaya,hartanto@securitypuppy.com,tanto259,
+Joe Winchester,winchest@uk.ibm.com,Joe-Winchester,
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
@@ -2,7 +2,7 @@
 
 # Overview
 
-This project aims to be governed in a transparent, accessible way for the benefit of the community. All participation in this project is open and not bound to corporate affilation. Participants are bound to the project's [Code of Conduct](CODE_OF_CONDUCT.md).
+This project aims to be governed in a transparent, accessible way for the benefit of the community. All participation in this project is open and not bound to corporate affiliation. Participants are bound to the project's [Code of Conduct](CODE_OF_CONDUCT.md).
 
 # Project roles
 
@@ -12,7 +12,7 @@ The contributor role is the starting role for anyone participating in the projec
 
 ### Process for becoming a contributor
 
-* Review the [contribution guidelines](CONTRIBUTING.md) guidelines to ensure your contribution is inline with the project's coding and styling guidelines.
+* Review the [contribution guidelines](CONTRIBUTING.md) guidelines to ensure your contribution is in line with the project's coding and styling guidelines.
 * Submit your code as a [pull request](https://github.com/openmainframeproject/cobol-programming-course/pulls) with the appropriate [DCO signoff](https://github.com/openmainframeproject/tac/blob/master/process/contribution_guidelines.md#developer-certificate-of-origin)
 * Have your submission approved by the committer(s) and merged into the codebase.
 
@@ -25,7 +25,7 @@ The committer role enables the contributor to commit code directly to the reposi
 * Show your experience with the codebase through contributions and engagement on the community channels.
 * Request to become a committer.
 * Have the majority of committers approve you becoming a committer.
-* Your name and email is added to the [COMMITTERS.csv](COMMITTERS.csv) file for the project.
+* Your name and email are added to the [COMMITTERS.csv](COMMITTERS.csv) file for the project.
 
 ### Committer responsibilities
 
@@ -36,11 +36,11 @@ The committer role enables the contributor to commit code directly to the reposi
 
 ### When does a committer lose committer status
 
-If a committer is no longer interested or cannot perform the committer duties listed above, they should volunteer to be moved to emeritus status. In extreme cases this can also occur by a vote of the committers per the voting process below.
+If a committer is no longer interested or cannot perform the committer duties listed above, they should volunteer to be moved to emeritus status. In extreme cases, this can also occur by a vote of the committers per the voting process below.
 
 ## Lead
 
-The project committers will elect a lead ( and optionally a co-lead ) which will be the primary point of contact for the project and representative to the TAC upon becoming an Active stage project. The lead(s) will be responsible for the overall project health and direction, coordination of activities, and working with other projects and committees as needed for the continuted growth of the project.
+The project committers will elect a lead ( and optionally a co-lead ) which will be the primary point of contact for the project and representative to the TAC upon becoming an Active stage project. The lead(s) will be responsible for the overall project health and direction, coordination of activities, and working with other projects and committees as needed for the continued growth of the project.
 
 # Release Process
 
@@ -54,7 +54,7 @@ In general, we prefer that technical issues and committer membership are amicabl
 
 This project, just like all of open source, is a global community. In addition to the [Code of Conduct](CODE_OF_CONDUCT.md), this project will:
 
-* Keep all communucation on open channels ( mailing list, forums, chat ).
+* Keep all communication on open channels ( mailing list, forums, chat ).
 * Be respectful of time and language differences between community members ( such as scheduling meetings, email/issue responsiveness, etc ).
 * Ensure tools are able to be used by community members regardless of their region.
 
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-![](https://raw.githubusercontent.com/openmainframeproject/artwork/main/projects/cobol-pc/horizontal/color/cobol-pc-horizontal-color.png)
+[![Logo](https://raw.githubusercontent.com/openmainframeproject/artwork/main/projects/cobol-pc/horizontal/color/cobol-pc-horizontal-color.png)](https://www.openmainframeproject.org/projects/cobolprogrammingcourse)
 
 [![License](https://img.shields.io/github/license/OpenMainframeProject/cobol-programming-course)](LICENSE)
 [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/4770/badge)](https://bestpractices.coreinfrastructure.org/projects/4770)
@@ -14,7 +14,7 @@ This project is a set of training materials and labs for COBOL on z/OS. The foll
     - [COBOL Programming Course #2 - Advanced Topics](COBOL%20Programming%20Course%20%232%20-%20Advanced%20Topics/README.md)
     - [COBOL Programming Course #3 - Testing](COBOL%20Programming%20Course%20%233%20-%20Testing/README.md)
 
-If you run into any issues, please don't hesitate to reach out on our [slack channel](https://openmainframeproject.slack.com/archives/C011NE32Z1T).
+If you run into any issues, please don't hesitate to reach out on our [Slack channel](https://openmainframeproject.slack.com/archives/C011NE32Z1T).
 
 ## Discussion
 
@@ -38,7 +38,7 @@ This project is openly governed as defined in [GOVERNANCE.md](GOVERNANCE.md).
 
 ## Credits
 
-The courseware materials were made available through a joint collaboration IBM, it's clients, and American River College and proposed as a new project by IBM.
+The courseware materials were made available through a joint collaboration between IBM, its clients, and American River College and proposed as a new project by IBM.
 
 ## Video Course Links
 
diff --git a/RELEASE.md b/RELEASE.md
@@ -1,5 +1,5 @@
 # Release guidelines
 
-This project is generally a rolling release project ( meaning the latest HEAD of master is the current materials ), but generally it's advised that those looking to leverage these materials in something downstream ( such as other training materials or labs enviroments ) pull from the [latest release tag](https://github.com/openmainframeproject/cobol-programming-course/releases) which makes it easier to see where the materials derived from.
+This project is generally a rolling release project ( meaning the latest HEAD of master is the current materials ), but generally, it's advised that those looking to leverage these materials in something downstream ( such as other training materials or labs environments ) pull from the [latest release tag](https://github.com/openmainframeproject/cobol-programming-course/releases) which makes it easier to see where the materials derived from.
 
-Releases are cut usually once a month from the then current HEAD of master, and provided as pdfs and source code only.
+Releases are cut usually once a month from the then-current HEAD of master and provided as PDFs and source code only.
diff --git a/ROADMAP.md b/ROADMAP.md
@@ -0,0 +1,20 @@
+# Roadmap
+
+These roadmap list out the possible and planned future contents for the COBOL Programming Course. If you are interested in contributing content, please review our [contribution guidelines](https://github.com/openmainframeproject/cobol-programming-course/blob/master/CONTRIBUTING.md).
+
+## In-Progress Future Contents
+
+- COBOL Interaction with CICS
+- VSAM File Handling
+- Object-Oriented COBOL
+- Subprograms
+- Sorting and Merging
+
+## Possible Future Contents
+
+- COBOL Interaction with IMS
+- COBOL Development in Mixed AMODE LE
+- COBOL Dynamic Link Libraries
+- Communication with Java Methods
+- Debugging and Testing
+- Processing JSON and XML
diff --git a/SECURITY.md b/SECURITY.md
@@ -0,0 +1,13 @@
+# Security Policy
+
+## Considerations
+
+The COBOL Programming Course does not produce any kind of software. This project produces a technical course aimed to educate people on COBOL programming. The output of this project came in the form of PDF documents detailing the course content. A Markdown version is also available on the repository.
+
+## Supported Version
+
+Only the [latest version](https://github.com/openmainframeproject/cobol-programming-course/releases/latest) of the course is supported with security updates.
+
+## Reporting a Vulnerability
+
+If you are aware of any significant vulnerability, or evidence of any, please send an email to the security contacts and we'll respond as soon as possible. For now, the security contacts are Michael Bauer, Hartanto Ario Widjaya and Sudharsana Srinivasan. The security contacts' email addresses can be found on the [COMMITTERS.csv](https://github.com/openmainframeproject/cobol-programming-course/blob/master/COMMITTERS.csv) file.
diff --git a/SUPPORT.md b/SUPPORT.md
@@ -8,11 +8,11 @@ There are a few ways to connect with the COBOL Programming Course project:
 
 ## How to Ask for Help
 
-If you have trouble installing, building, or using COBOL Programming Course, but there's not yet reason to suspect you've encountered a genuine bug, start by posting a question to the Slack channel. This is the place for question such has "How do I...".
+If you have trouble installing, building, or using COBOL Programming Course, but there's not yet reason to suspect you've encountered a genuine bug, start by posting a question to the Slack channel. This is the place for questions such as "How do I...".
 
 ## How to report a bug or request an enhancement
 
-COBOL Programming Course manages bug and enhancement using it's [issue tracker](https://github.com/openmainframeproject/cobol-programming-course/issues/new/choose). The issue template will guide you on making an effective report.
+COBOL Programming Course manages bug and enhancement using its [issue tracker](https://github.com/openmainframeproject/cobol-programming-course/issues/new/choose). The issue template will guide you in making an effective report.
 
 ## Contributing a fix
 
