Merge pull request #3 from kommitters/v1.0

Release v1.0.0

CHANGELOG.md

@@ -0,0 +1,4 @@
+# Changelog
+
+## 1.0.0 (18.07.2021)
+* Allstar config for the kommit's OSPO.

CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community includes:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing other's private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at [[email protected]](mailto:[email protected]).
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,41 @@
+# How to contribute
+
+First off, thanks for taking the time to contribute, it is encouraging! 🎉🙌
+
+We want to make it as easy as possible to contribute changes that help the [.allstar allstar configuration repo][repo], this is a configuration repo for the good of the kommitters organization so every advice or contribution is well received. There are a few guidelines that we ask contributors to follow so that we can merge your changes quickly.
+
+## Getting started
+
+* Make sure you have a [GitHub account](https://github.com/signup/free).
+* Create a GitHub issue for your contribution, assuming one does not already exist.
+  * Clearly describe the issue including steps to reproduce if it is a bug.
+* Fork the repository on GitHub.
+* Try to keep your local repository in a "rebased" state.
+
+## Making changes
+
+* Create a topic branch from where you want to base your work.
+  * This is usually the `main` branch.
+  * Please avoid working directly on the `main` branch.
+
+## Submitting changes
+
+* All content, comments, pull requests and other contributions must comply with the
+  [Code of Conduct][coc].
+* Push your changes to a topic branch in your fork of the repository.
+* Submit a pull request.
+  * Include a descriptive [commit message][commit-msg].
+  * Changes contributed via pull request should focus on a single issue at a time.
+  * Rebase your local changes against the `main` branch. Resolve any conflicts that arise.
+
+At this point, you're waiting on us. We like to at least comment on pull requests within three
+business days (typically, one business day). We may suggest some changes, improvements or
+alternatives.
+
+## Additional resources
+
+* Get in touch: [[email protected]](mailto:[email protected]) | [@kommitters_oss](https://twitter.com/kommitters_oss) on Twitter.
+
+[repo]: https://github.com/kommitters/.allstar
+[coc]: https://github.com/kommitters/.allstar/blob/main/CODE_OF_CONDUCT.md
+[commit-msg]: https://github.com/erlang/otp/wiki/Writing-good-commit-messages

README.md

@@ -1,2 +1,75 @@
-# .allstar
-OSPO's policies for adherence to security best practices
+# kommitters Security Policies
+
+<img align="right" src="artwork/kommitters_ospo.jpeg"/>
+<p>&nbsp;</p>
+
+This repo establishes the kommit's OSPO security policies.
+
+Allstar is a security-policy GitHub app that continuously monitors organizations for adherence to security best practices. Security violations are reported as issues in the affected repositories.
+
+This README.md file describes in detail policies applied to this organization.
+
+To configure Allstar in your organization, fork this repository and modify the `.yaml` files to match your security policies. Visit the [Allstar installation][installation_options] page for more information.
+
+## Policy configuration
+
+The application is running on all the repos of this organization with the `OptOutStrategy` strategy with the following configurations:
+
+### Branch Protection
+
+| Name of setting         | Setting | Description                                                                                                                                                                            |
+| ----------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Branches enforced       | Yes     | Enforce upstream branches like `main` `develop` `v*.*` → `v0.1`.                                                                                                                        |
+| Approval required       | Yes     | If required pull request reviews are enabled on the branch, you won't be able to merge changes into the branch until all requirements in the pull request review policy have been met. |
+| Approvals required      | 1       | Approval reviews required to merge changes into a branch.                                                                                                                              |
+| Block Force Push        | Yes     | You won't be able to delete or force push to the branch.                                                                                                                               |
+| Status check required   | Yes     | If required status checks are enabled on the branch, you won't be able to merge changes into the branch until all of the required CI tests pass.                                       |
+| Signed commits required | Yes     | If required commit signing is enabled on a branch, you won't be able to push any commits to the branch that are not signed and verified.                                               |
+
+`Action: issue`
+`Active repositories: public only`
+
+### Binary artifacts
+
+* No binary artifacts allowed.
+
+`Action: issue`
+`Active repositories: public only`
+
+### Outside collaborators
+
+* Default push access not allowed, only organization members can push directly to the organization repositories.
+* Default admin access not allowed.
+
+`Action: issue`
+`Active repositories: public only`
+
+### Security
+
+* `SECURITY.md` not empty file required. 
+
+`Action: issue`
+`Active repositories: public only`
+
+---
+
+## Code of conduct
+We welcome everyone to contribute. Make sure you have read the [CODE_OF_CONDUCT][coc] before.
+
+## Contributing
+For information on how to contribute, please refer to our [CONTRIBUTING][contributing] guide.
+
+## Changelog
+Policies changes are listed in the [CHANGELOG][changelog] file.
+
+## License
+This repo is licensed under an MIT license. See [LICENSE][license] for details.
+
+## Acknowledgements
+The [OpenSSF organization](https://github.com/ossf), and the [Securing Critical Projects Working Group](https://github.com/ossf/wg-securing-critical-projects).
+
+[license]: https://github.com/kommitters/.allstar/blob/main/LICENSE
+[coc]: https://github.com/kommitters/.allstar/blob/main/CODE_OF_CONDUCT.md
+[changelog]: https://github.com/kommitters/.allstar/blob/main/CHANGELOG.md
+[contributing]: https://github.com/kommitters/.allstar/blob/main/CONTRIBUTING.md
+[installation_options]: https://github.com/ossf/allstar#installation-options

SECURITY.md

@@ -0,0 +1,5 @@
+# Reporting Security Issues
+
+To report a security issue, please email [[email protected]](mailto:[email protected]) with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue.
+
+If the issue is confirmed as a vulnerability, we will open a Security Advisory and acknowledge your contributions as part of it.

VERSION

@@ -0,0 +1 @@
+1.0.0

allstar.yaml

@@ -0,0 +1,3 @@
+optConfig:
+  optOutStrategy: true
+  optOutPrivateRepos: true

binary_artifacts.yaml

@@ -0,0 +1,3 @@
+optConfig:
+  optOutStrategy: true
+action: issue

branch_protection.yaml

@@ -0,0 +1,8 @@
+optConfig:
+  optOutStrategy: true
+action: issue
+enforceDefault: true
+requireApproval: true
+approvalCount: 1
+blockForce: true
+requireSignedCommits: true

outside.yaml

@@ -0,0 +1,4 @@
+optConfig:
+  optOutStrategy: true
+action: issue
+pushAllowed: false

security.yaml

@@ -0,0 +1,3 @@
+optConfig:
+  optOutStrategy: true
+action: issue