Create initial governance (openmainframeproject#29)

Create initial governance

Signed-off-by: John Mertic <[email protected]>
Co-authored-by: Sudharsana-Srinivasan <[email protected]>

Author: jmertic

CODE_OF_CONDUCT.md

@@ -0,0 +1 @@
+All participants agree to abide by the Code of Conduct available at https://github.com/openmainframeproject/tac/blob/master/CODE_OF_CONDUCT.md.

COMMITTERS.csv

@@ -0,0 +1,5 @@
+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

GOVERNANCE.md

@@ -0,0 +1,61 @@
+*Adapted from the [example_governance.md](https://github.com/openmainframeproject/tac/blob/master/process/example_governance.md) recommendation from Open Mainframe Project TAC*
+
+# 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).
+
+# Project roles
+
+## Contributor
+
+The contributor role is the starting role for anyone participating in the project and wishing to contribute code.
+
+# 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.
+* 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.
+
+## Committer
+
+The committer role enables the contributor to commit code directly to the repository, but also comes with the responsibility of being a responsible leader in the community.
+
+### Process for becoming a committer
+
+* 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.
+
+### Committer responsibilities
+
+* Monitor and moderate the [mailing list](https://lists.openmainframeproject.org/g/cobol-course-discussion).
+* Monitor [#cobol-programming-course Slack channel](https://slack.openmainframeproject.org) (delayed response is perfectly acceptable).
+* Triage [GitHub issues](https://github.com/openmainframeproject/cobol-programming-course/issues) and perform [pull request reviews](https://github.com/openmainframeproject/cobol-programming-course/pulls) for other committers and the community.
+* Make sure that ongoing PRs are moving forward at the right pace or closing them.
+
+### 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.
+
+## 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.
+
+# Release Process
+
+Project releases will occur on a scheduled basis as agreed to by the committers as defined in [RELEASE.md](RELEASE.md)
+
+# Conflict resolution and voting
+
+In general, we prefer that technical issues and committer membership are amicably worked out between the persons involved. If a dispute cannot be decided independently, the committers can be called in to decide an issue. If the committers themselves cannot decide an issue, the issue will be resolved by voting. The voting process is a simple majority in which each committer receives one vote.
+
+# Communication
+
+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 ).
+* 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.
+
+If you have concerns about communication challenges for this project, please contact the committers.

README.md

@@ -11,16 +11,34 @@ There are two sets of materials available
 - [Chapters](https://github.com/openmainframeproject/cobol-programming-course/blob/master/COBOL%20Programming%20with%20VSCode.pdf) which contain the lessons, broken up into chapters.
 - [Labs](https://github.com/openmainframeproject/cobol-programming-course/tree/master/Labs) which contain the source code used in the chapters.
 
+## Build
+
+You can use [pandoc](https://pandoc.org/) to convert the markdown files provided to any other format such as DOCX, PDF, or HTML.
+
 ## Contributing
 
 Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
 
 All contributions must align with the [Open Mainframe Project contribution guidelines](https://github.com/openmainframeproject/tac/blob/master/process/contribution_guidelines.md), including having a DCO signoff on all commits.
 
+# Discussion
+
+You can connect with the community in a variety of ways...
+
+- [COBOL Programming Course Discussion Mailing list](https://lists.openmainframeproject.org/g/cobol-course-discussion)
+- [#cobol-programming-course channel on Open Mainframe Project Slack](https://slack.openmainframeproject.org)
+- ['COBOL technical questions' category on Open Mainframe Project Community Forums](https://community.openmainframeproject.org/c/cobol-technical-questions/16)
+
+## Providers
+
+These materials are being used by other organizations to provide COBOL training to the community. This project, nor Open Mainframe Project, doesn't endorse any one of these particular providers. If you are using these materials in your training materials, feel free [to edit and issue a pull request](https://github.com/openmainframeproject/cobol-programming-course/edit/governance-docs/README.md) to have it included.
+
+- IBM is provided a [free environment for completing the labs](http://ibm.biz/cobollabs).
+
 ## Governance
 
-This project is openly governed, and currently establishing its processes. Stay tuned :-)
+This project is openly governed as defined in [GOVERNANCE.md](GOVERNANCE.md).
 
 ## Credits
 
-Thank you to IBM for the initial contribution and Open Mainframe Project for hosting this project.
+The courseware materials were developed leveraging grant funds made available through American River College and proposed as a new project by IBM.

RELEASE.md

@@ -0,0 +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.
+
+Releases are cut usually once a week from the then current HEAD of master, and provided as markdown files and source code only. If you desire a different format, please refer to the [build instructions](README.md#build).