Sign SHO: Initial version

Author: Sveino

.github/.cSpell.json

@@ -0,0 +1,8 @@
+{
+    "version": "0.2",
+    "language": "en-GB",
+    "words": [
+      ".adoc"
+    ]
+  }
+  

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# 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, 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 include:
+
+* 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 others' 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].
+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.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

.github/Contributing.md

@@ -0,0 +1,67 @@
+= Contributing to the project
+
+Thank you for your interest in contributing to this project! We value your contributions and strive to create an open and welcoming environment. This document outlines the guidelines for participating and ensuring a smooth collaboration process.
+
+== Code of conduct
+All contributors are expected to adhere to our project's Code of Conduct. Please read it before contributing:
+
+- **link:CODE_OF_CONDUCT.adoc[Code of Conduct]**
+
+== Contribution Guidelines
+
+=== General Guidelines
+- Follow our coding standards and best practices.
+- Ensure that your changes align with the link:ReadMe.adoc[project’s goals] and link:Roadmap.adoc[roadmap].
+- Open an issue before starting significant work to gather feedback.
+- All code must be reviewed before merging.
+
+=== British English Convention
+- Use **British English** for all comments, documentation, and discussions. A list of spelling differences between British and American English can be found link:https://www.britishcouncilfoundation.id/en/english/articles/british-and-american-english[here].
+- Maintain clear and concise documentation.
+
+== Developer Certificate of Origin (DCO)
+Before contributing, you must agree to the Developer Certificate of Origin (DCO). This ensures that all contributions are properly licensed and attributable:
+
+- **link:DCO[Developer Certificate of Origin]**
+
+== License
+By contributing to this project, you agree that your contributions will be licensed under the project's license:
+
+- **link:LICENSE[Project License]**
+
+== Governance
+The project follows a structured governance model. Refer to the governance document for more details on roles, responsibilities, and decision-making processes:
+
+- **link:Governance.adoc[Governance]**
+
+== Roadmap
+To align contributions with the project's vision and future direction, please review our roadmap:
+
+- **link:Roadmap.adoc[Project Roadmap]**
+
+== Security
+If you discover a security vulnerability, please follow the responsible disclosure process outlined in our security policy:
+
+- **Security.adoc[Security Policy]**
+
+== Support
+For questions, issues, or general discussions, refer to the support guidelines:
+
+- **Support.adoc[Support Guidelines]**
+
+== Submitting Changes
+
+1. **Fork the Repository**
+2. **Create a New Branch** for your feature or bug fix.
+3. **Commit Your Changes** following conventional commit messages.
+4. **Run Tests** to ensure your changes do not introduce issues.
+5. **Open a Pull Request** and link to the related issue.
+6. **Engage in Review** by addressing feedback and suggestions.
+
+== Issues and Feature Requests
+- Before opening a new issue, check existing issues to avoid duplicates.
+- Clearly describe the issue or feature request with relevant details.
+- Label the issue appropriately for better tracking.
+
+
+

.github/DCO

@@ -0,0 +1,36 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+660 York Street, Suite 102,
+San Francisco, CA 94110 USA
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.

.github/Governance.adoc

@@ -0,0 +1,59 @@
+= Project Governance
+
+This document outlines the governance model for the project, defining roles, responsibilities, and branch management strategy.
+
+== Roles and Permissions
+The project follows a structured role-based access control model. The roles are defined as follows:
+
+=== Read
+- Can view repository contents and discussions.
+- Can submit issues and comment on existing ones.
+- No write access.
+
+=== Triage
+- Can label, categorize, and prioritize issues.
+- Can assist in reviewing and managing issue reports.
+- Cannot merge pull requests or modify the repository.
+
+=== Write
+- Can create and push branches.
+- Can submit and review pull requests.
+- Can update documentation and contribute code.
+- Cannot modify project settings or manage permissions.
+
+=== Maintain
+- Can approve and merge pull requests.
+- Responsible for reviewing and enforcing coding standards.
+- Can manage project workflows and CI/CD configurations.
+- Cannot delete the repository or change administrative settings.
+
+=== Admin
+- Full control over repository settings and permissions.
+- Can manage roles and access levels.
+- Can enforce security policies and branch protections.
+- Responsible for repository governance and compliance.
+
+== Branch Management Strategy
+
+=== Default Branch
+- The default working branch for active development is **`development`**.
+- All new features and bug fixes must be merged into the **`development`** branch before being included in a release.
+
+=== Historical Branches
+- Versioning follows **Semantic Versioning** (MAJOR.MINOR.PATCH).
+- Major and minor releases are archived as historical branches following the format:
+  - `vX.Y` (e.g., `v1.0`, `v1.1`, `v2.0`)
+- Patch releases are handled within the latest minor release branch.
+
+=== Branch Protection Rules
+- The **`development`** branch is protected and requires pull request reviews before merging.
+- Historical branches are read-only to preserve past versions.
+- Direct pushes to protected branches are restricted to **Maintain** and **Admin** roles.
+
+== Decision-Making Process
+- Governance decisions are made by the **Admin** role in consultation with **Maintain** members.
+- Feature discussions, roadmaps, and major changes are discussed through issue tracking and proposal discussions.
+- Voting or consensus-based decision-making is used for impactful changes.
+
+== Amendments
+This governance document may be updated as needed. Changes must be reviewed and approved by **Admin** before adoption.