Skip to content

Commit 8911159

Browse files
authored
Merge pull request #219 from tanto259/update-governance
Update Governance Files
2 parents ecbd505 + 241afb1 commit 8911159

File tree

13 files changed

+195
-25
lines changed

13 files changed

+195
-25
lines changed
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
name: Bug Report
2+
description: Create a report to help us improve the COBOL Programming Course
3+
labels: ['bug']
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Thank you for submitting a bug report. Please fill in the information below and we will get back to you as soon as possible.
9+
10+
Before opening an issue, please search our existing issues: https://github.com/openmainframeproject/cobol-programming-course/issues.
11+
- type: dropdown
12+
attributes:
13+
label: Course Details
14+
description: Where did you take the course?
15+
options:
16+
- GitHub
17+
- IBM Learning Platform
18+
- Coursera
19+
- edX
20+
- Pluralsight
21+
- YouTube
22+
validations:
23+
required: true
24+
- type: textarea
25+
attributes:
26+
label: Description
27+
description: What happened?
28+
validations:
29+
required: true
30+
- type: textarea
31+
attributes:
32+
label: Reproduction Steps
33+
description: What do we need to do to reproduce this bug?
34+
value: |
35+
1.
36+
2.
37+
3.
38+
...
39+
validations:
40+
required: true
41+
- type: textarea
42+
attributes:
43+
label: Additional Context
44+
description: Any other context about the problem?
45+
validations:
46+
required: false

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Slack Channel
4+
url: https://slack.openmainframeproject.org
5+
about: Need assistance on the course or just want to say hi? Join our Slack channel
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
name: Feature Request
2+
description: Suggest an idea for the COBOL Programming Course
3+
labels: ['enhancement']
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Thank you for submitting a feature request. Please fill in the information below and we will get back to you as soon as possible.
9+
10+
Before opening a feature request, please search our existing issues: https://github.com/openmainframeproject/cobol-programming-course/issues.
11+
- type: dropdown
12+
attributes:
13+
label: Course Details
14+
description: Where did you take the course?
15+
options:
16+
- GitHub
17+
- IBM Learning Platform
18+
- Coursera
19+
- edX
20+
- Pluralsight
21+
- YouTube
22+
validations:
23+
required: true
24+
- type: textarea
25+
attributes:
26+
label: Description
27+
description: Describe what you want to happen.
28+
validations:
29+
required: true
30+
- type: textarea
31+
attributes:
32+
label: Problems
33+
description: Is your feature request related to a problem? Please describe.
34+
validations:
35+
required: false
36+
- type: textarea
37+
attributes:
38+
label: Additional Context
39+
description: Any other context about the problem?
40+
validations:
41+
required: false
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
## Proposed changes
2+
3+
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)

CODE_OF_CONDUCT.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
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.

COMMITTERS.csv

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
Name,Email,GitHub ID
2-
Sudharsana Srinivasan,Sudharsana.Srinivasan@ibm.com,Sudharsana-Srinivasan
3-
Martin Keen,mkeen@us.ibm.com,martinkeen
4-
John Mertic,jmertic@linuxfoundation.org,jmertic
5-
Paul Newton,paulnewt@us.ibm.com,paulnewt
6-
Michael Bauer,Michael.Bauer2@broadcom.com,MikeBauerCA
7-
Jessielaine Punongbayan,Jessielaine.Punongbayan@broadcom.com,jellypuno
8-
Zeibura Kathau,Zeibura.Kathau@broadcom.com,zeibura
9-
Hartanto Ario Widjaya,hartanto@securitypuppy.com,tanto259
10-
Joe Winchester,winchest@uk.ibm.com,Joe-Winchester
1+
Name,Email,GitHub ID,Role
2+
Sudharsana Srinivasan,Sudharsana.Srinivasan@ibm.com,Sudharsana-Srinivasan,Lead
3+
Michael Bauer,Michael.Bauer2@broadcom.com,MikeBauerCA,Co-Lead
4+
Martin Keen,mkeen@us.ibm.com,martinkeen,
5+
John Mertic,jmertic@linuxfoundation.org,jmertic,
6+
Paul Newton,paulnewt@us.ibm.com,paulnewt,
7+
Jessielaine Punongbayan,Jessielaine.Punongbayan@broadcom.com,jellypuno,
8+
Zeibura Kathau,Zeibura.Kathau@broadcom.com,zeibura,
9+
Hartanto Ario Widjaya,hartanto@securitypuppy.com,tanto259,
10+
Joe Winchester,winchest@uk.ibm.com,Joe-Winchester,

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,4 +39,4 @@ If you are committing via the GitHub UI directly, check out these [useful tools]
3939

4040
## Pull Requests
4141
- All contributions must be reviewed by a [committer](COMMITTERS.csv)
42-
- Anyone can comment on a pull request to request delay on merging or to get questions answered.
42+
- Anyone can comment on a pull request to request delay on merging or to get questions answered.

GOVERNANCE.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,17 @@
22

33
# Overview
44

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).
66

77
# Project roles
88

99
## Contributor
1010

1111
The contributor role is the starting role for anyone participating in the project and wishing to contribute code.
1212

13-
# Process for becoming a contributor
13+
### Process for becoming a contributor
1414

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.
1616
* 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)
1717
* Have your submission approved by the committer(s) and merged into the codebase.
1818

@@ -25,7 +25,7 @@ The committer role enables the contributor to commit code directly to the reposi
2525
* Show your experience with the codebase through contributions and engagement on the community channels.
2626
* Request to become a committer.
2727
* 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.
2929

3030
### Committer responsibilities
3131

@@ -36,11 +36,11 @@ The committer role enables the contributor to commit code directly to the reposi
3636

3737
### When does a committer lose committer status
3838

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.
4040

4141
## Lead
4242

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.
4444

4545
# Release Process
4646

@@ -54,7 +54,7 @@ In general, we prefer that technical issues and committer membership are amicabl
5454

5555
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:
5656

57-
* Keep all communucation on open channels ( mailing list, forums, chat ).
57+
* Keep all communication on open channels ( mailing list, forums, chat ).
5858
* Be respectful of time and language differences between community members ( such as scheduling meetings, email/issue responsiveness, etc ).
5959
* Ensure tools are able to be used by community members regardless of their region.
6060

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
![](https://github.com/openmainframeproject/artwork/raw/master/projects/cobol-programming-course/cobol-programming-course-color.png)
1+
[![Logo](https://raw.githubusercontent.com/openmainframeproject/artwork/main/projects/cobol-pc/horizontal/color/cobol-pc-horizontal-color.png)](https://www.openmainframeproject.org/projects/cobolprogrammingcourse)
22

3-
![License](https://img.shields.io/github/license/OpenMainframeProject/cobol-programming-course)
3+
[![License](https://img.shields.io/github/license/OpenMainframeProject/cobol-programming-course)](LICENSE)
44
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/4770/badge)](https://bestpractices.coreinfrastructure.org/projects/4770)
55

66
# COBOL Programming Course
@@ -14,7 +14,7 @@ This project is a set of training materials and labs for COBOL on z/OS. The foll
1414
- [COBOL Programming Course #2 - Advanced Topics](COBOL%20Programming%20Course%20%232%20-%20Advanced%20Topics/README.md)
1515
- [COBOL Programming Course #3 - Testing](COBOL%20Programming%20Course%20%233%20-%20Testing/README.md)
1616

17-
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).
1818

1919
## Discussion
2020

@@ -38,7 +38,7 @@ This project is openly governed as defined in [GOVERNANCE.md](GOVERNANCE.md).
3838

3939
## Credits
4040

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.
4242

4343
## Video Course Links
4444

RELEASE.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Release guidelines
22

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 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.
44

5-
Releases are cut usually once a month from the then current 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

Comments
 (0)