You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context to communicate to the maintainers why we should accept this pull request.
4
+
5
+
Fixes # (issue)
6
+
7
+
## Type of change
8
+
9
+
What type of changes does your PR introduce to the COBOL Programming Course? _Put an `x` in the boxes that apply._
10
+
11
+
-[ ] Bug fix (change which fixes one or more issues)
12
+
-[ ] New feature (change which adds functionality or features to the course)
13
+
-[ ] Translations (change which adds or modifies translations of the course)
14
+
-[ ] Documentation (change which modifies documentation related to the course)
15
+
-[ ] This change requires an update to the course's z/OS environment
16
+
17
+
## Checklist:
18
+
19
+
_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This checklist will be used as reference for both the contributor and the reviewer_
20
+
21
+
-[ ] I have read the [Contributing Guideline](https://github.com/openmainframeproject/cobol-programming-course/blob/master/CONTRIBUTING.md)
22
+
-[ ] I have included a title and description for this PR
23
+
-[ ] I have DCO-signed all of my commits that are included in this PR
24
+
-[ ] I have tested it manually and there are no regressions found
25
+
-[ ] I have commented my code, particularly in hard-to-understand areas (if appropriate)
26
+
-[ ] I have made corresponding changes to the documentation (if appropriate)
All participants agree to abide by the Code of Conduct available at https://github.com/openmainframeproject/tac/blob/master/CODE_OF_CONDUCT.md.
1
+
All participants agree to abide by the Code of Conduct available at https://github.com/openmainframeproject/tac/blob/master/CODE_OF_CONDUCT.md. Please contact conduct@openmainframeproject.org to report any violations or concerns.
Copy file name to clipboardExpand all lines: GOVERNANCE.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,17 @@
2
2
3
3
# Overview
4
4
5
-
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).
5
+
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).
6
6
7
7
# Project roles
8
8
9
9
## Contributor
10
10
11
11
The contributor role is the starting role for anyone participating in the project and wishing to contribute code.
12
12
13
-
# Process for becoming a contributor
13
+
###Process for becoming a contributor
14
14
15
-
* Review the [contribution guidelines](CONTRIBUTING.md) guidelines to ensure your contribution is inline with the project's coding and styling guidelines.
15
+
* Review the [contribution guidelines](CONTRIBUTING.md) guidelines to ensure your contribution is in line with the project's coding and styling guidelines.
16
16
* 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)
17
17
* Have your submission approved by the committer(s) and merged into the codebase.
18
18
@@ -25,7 +25,7 @@ The committer role enables the contributor to commit code directly to the reposi
25
25
* Show your experience with the codebase through contributions and engagement on the community channels.
26
26
* Request to become a committer.
27
27
* Have the majority of committers approve you becoming a committer.
28
-
* Your name and email is added to the [COMMITTERS.csv](COMMITTERS.csv) file for the project.
28
+
* Your name and email are added to the [COMMITTERS.csv](COMMITTERS.csv) file for the project.
29
29
30
30
### Committer responsibilities
31
31
@@ -36,11 +36,11 @@ The committer role enables the contributor to commit code directly to the reposi
36
36
37
37
### When does a committer lose committer status
38
38
39
-
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.
39
+
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.
40
40
41
41
## Lead
42
42
43
-
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.
43
+
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.
44
44
45
45
# Release Process
46
46
@@ -54,7 +54,7 @@ In general, we prefer that technical issues and committer membership are amicabl
54
54
55
55
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:
56
56
57
-
* Keep all communucation on open channels ( mailing list, forums, chat ).
57
+
* Keep all communication on open channels ( mailing list, forums, chat ).
58
58
* Be respectful of time and language differences between community members ( such as scheduling meetings, email/issue responsiveness, etc ).
59
59
* Ensure tools are able to be used by community members regardless of their region.
If you run into any issues, please don't hesitate to reach out on our [slack channel](https://openmainframeproject.slack.com/archives/C011NE32Z1T).
17
+
If you run into any issues, please don't hesitate to reach out on our [Slack channel](https://openmainframeproject.slack.com/archives/C011NE32Z1T).
18
18
19
19
## Discussion
20
20
@@ -38,7 +38,7 @@ This project is openly governed as defined in [GOVERNANCE.md](GOVERNANCE.md).
38
38
39
39
## Credits
40
40
41
-
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.
41
+
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.
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.
3
+
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.
4
4
5
-
Releases are cut usually once a month from the thencurrent HEAD of master, and provided as pdfs and source code only.
5
+
Releases are cut usually once a month from the then-current HEAD of master and provided as PDFs and source code only.
0 commit comments