From d1f5aa7cadc554e36f300ff111dfcfdec50006a4 Mon Sep 17 00:00:00 2001 From: Jade Carino Date: Tue, 28 Apr 2026 16:35:07 +0100 Subject: [PATCH 1/5] fix: Update correct slack channel info in README.md Signed-off-by: Jade Carino --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0c4ec98..11cbbeb 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ This repository contains the integration tests that are used to test Galasa Mana ## Documentation -More information can be found on the [Galasa Homepage](https://galasa.dev). Questions related to the usage of Galasa can be posted in the [galasa-users channel](https://openmainframeproject.slack.com/archives/C05TCCQDE65) on the Open Mainframe Project Slack workspace. +More information can be found on the [Galasa Homepage](https://galasa.dev). Questions related to the usage of Galasa can be posted in the [galasa-users channel](https://openmainframeproject.slack.com/archives/C05ST4K4K54) on the Open Mainframe Project Slack workspace. ## Where can I get the latest release? @@ -13,7 +13,7 @@ Other repositories are available via [GitHub](https://github.com/galasa-dev). ## Contributing -If you are interested in the development of Galasa, take a look at the documentation and feel free to ask a question in the [galasa-users channel](https://openmainframeproject.slack.com/archives/C05TCCQDE65) on the Open Mainframe Project Slack workspace, or raise new ideas/features/bugs as Issues on [GitHub](https://github.com/galasa-dev/projectmanagement). +If you are interested in the development of Galasa, take a look at the documentation and feel free to ask a question in the [galasa-users channel](https://openmainframeproject.slack.com/archives/C05ST4K4K54) on the Open Mainframe Project Slack workspace, or raise new ideas/features/bugs as Issues on [GitHub](https://github.com/galasa-dev/projectmanagement). Take a look at the [contribution guidelines](https://github.com/galasa-dev/galasa/blob/main/CONTRIBUTING.md). From 5651b325fe2d58c056efaa85b2615a3e80990a19 Mon Sep 17 00:00:00 2001 From: Jade Carino Date: Tue, 28 Apr 2026 16:35:21 +0100 Subject: [PATCH 2/5] Add code of conduct Signed-off-by: Jade Carino --- CODE_OF_CONDUCT.md | 90 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 90 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..9832e67 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,90 @@ +# Contributor Covenant 3.0 Code of Conduct + +## Our Pledge + +We pledge to make our community welcoming, safe, and equitable for all. + +We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant. + +## Encouraged Behaviors + +While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language. + +With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including: + +1. Respecting the **purpose of our community**, our activities, and our ways of gathering. +2. Engaging **kindly and honestly** with others. +3. Respecting **different viewpoints** and experiences. +4. **Taking responsibility** for our actions and contributions. +5. Gracefully giving and accepting **constructive feedback**. +6. Committing to **repairing harm** when it occurs. +7. Behaving in other ways that promote and sustain the **well-being of our community**. + + +## Restricted Behaviors + +We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct. + +1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop. +2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people. +3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits. +4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community. +5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission. +6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group. +7. Behaving in other ways that **threaten the well-being** of our community. + +### Other Restrictions + +1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions. +2. **Failing to credit sources.** Not properly crediting the sources of content you contribute. +3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community. +4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors. + + +## Reporting an Issue + +Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm. + +When an incident does occur, it is important to report it promptly. To report a possible violation, **[please contact one of the maintainers](https://github.com/orgs/galasa-dev/teams/org-owners), or reach out on the [galasa-users slack channel](https://openmainframeproject.slack.com/archives/C05ST4K4K54).** + +Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. + + +## Addressing and Repairing Harm + +**** + +If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped. + +1) Warning + 1) Event: A violation involving a single incident or series of incidents. + 2) Consequence: A private, written warning from the Community Moderators. + 3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations. +2) Temporarily Limited Activities + 1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation. + 2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members. + 3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over. +3) Temporary Suspension + 1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation. + 2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions. + 3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted. +4) Permanent Ban + 1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member. + 2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior. + 3) Repair: There is no possible repair in cases of this severity. + +This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community. + + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. + + +## Attribution + +This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/). + +Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/) + +For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion). \ No newline at end of file From 3003f9936e00a720c7e94af408deff0b03295168 Mon Sep 17 00:00:00 2001 From: Jade Carino Date: Tue, 28 Apr 2026 16:37:37 +0100 Subject: [PATCH 3/5] add contributing guide Signed-off-by: Jade Carino --- CONTRIBUTING.md | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..e9e04e6 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,3 @@ +# Contributing + +To learn more about contributing to this project, see the [CONTRIBUTING](https://github.com/galasa-dev/galasa/blob/main/CONTRIBUTING.md) guide. \ No newline at end of file From 074805c7a0e8bf429b36051a41ef24a85ab5ed68 Mon Sep 17 00:00:00 2001 From: Jade Carino Date: Tue, 28 Apr 2026 16:38:56 +0100 Subject: [PATCH 4/5] add security policy Signed-off-by: Jade Carino --- SECURITY.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..d59d4b0 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,5 @@ +# Security Policy + +## Reporting a Vulnerability + +To report a vulnerability, [please contact a maintainer](https://github.com/orgs/galasa-dev/teams/org-owners), [raise a bug report](https://github.com/galasa-dev/projectmanagement/issues) or reach out to us on the [galasa-users](https://openmainframeproject.slack.com/archives/C05ST4K4K54) slack channel on the [Open Mainframe Project Slack org](openmainframeproject.slack.com). \ No newline at end of file From f089fc06dfd6fe33a2b9da3383b4451feff145df Mon Sep 17 00:00:00 2001 From: Jade Carino Date: Tue, 28 Apr 2026 16:41:17 +0100 Subject: [PATCH 5/5] add pull request template and issue template Signed-off-by: Jade Carino --- .../redirect_issues_to_project_management.md | 11 +++++++++++ SECURITY.md => .github/SECURITY.md | 0 .github/pull_request_template.md | 6 ++++++ 3 files changed, 17 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/redirect_issues_to_project_management.md rename SECURITY.md => .github/SECURITY.md (100%) create mode 100644 .github/pull_request_template.md diff --git a/.github/ISSUE_TEMPLATE/redirect_issues_to_project_management.md b/.github/ISSUE_TEMPLATE/redirect_issues_to_project_management.md new file mode 100644 index 0000000..b1a8fdd --- /dev/null +++ b/.github/ISSUE_TEMPLATE/redirect_issues_to_project_management.md @@ -0,0 +1,11 @@ +--- +name: Please read +about: Please do not create issues on this repository, but use the projectmanagement repository instead. +title: '' +labels: '' +assignees: '' + +--- + +## Please redirect issues to Galasa's 'projectmanagement' Repository +Please raise your issue(s) on [Galasa's projectmanagement repository](https://github.com/galasa-dev/projectmanagement/issues). \ No newline at end of file diff --git a/SECURITY.md b/.github/SECURITY.md similarity index 100% rename from SECURITY.md rename to .github/SECURITY.md diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 0000000..c5f1c8d --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,6 @@ +## Why? + +Refer to [link-to-github-issue]. + +## Changes +- [ ] \ No newline at end of file