Cleanup and best practice docs

Author: paulswithers

CODE_OF_CONDUCT.md

@@ -0,0 +1,51 @@
+# Contributor Covenant Code of Conduct
+
+Projects should foster a positive environment, to ensure active and pleasant participation for all. This is wording for a contributor covenant, amended from [Contributor Covenant 2.0](https://www.contributor-covenant.org/version/2/0/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 HCL Open Source Project Officer, who is responsible for enforcement, at [ospo.hclsoftware@hcl.com](mailto:ospo.hclsoftware@hcl.com). All complaints will be reviewed and investigated promptly and fairly. The HCL Open Source Project Office is obligated to respect the privacy and security of the reporter of any incident. Details of enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by the HCL Open Source Project Office.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at <a href="https://www.contributor-covenant.org/version/2/0/code_of_conduct.html">https://www.contributor-covenant.org/version/2/0/code_of_conduct.html</a>.
+
+Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
+
+For answers to common questions about this code of conduct, see the FAQ at <a href="https://www.contributor-covenant.org/faq">https://www.contributor-covenant.org/faq</a>.

CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Contributing Guidelines
+
+## Contributor roles
+
+Open source should not be just about writing code. A good open source project also needs:
+
+- Documentation writers
+- Testers
+- Tutorial writers
+- Evangelists
+- Automation builders
+
+If you want to get involved in a role (including ones we may have missed!) reach out to one of the committers.
+
+## Working on issues
+
+- Ensure there is a GitHub issue for any bug before submitting a PR.
+- Enhancements should be discussed and a feature request issue created, before starting work on it.
+- Fork and raise a PR for work.
+- Add tests for any enhancements.
+- Ensure documentation is updated accordingly, including adding unit test reports.
+- Ensure API docs are updated (speak to an HCL-ite if required).
+- Ensure changelog is updated.
+
+## Development Environment
+
+- Develop code with Visual Studio Code and VoltScript extensions, see https://help.hcltechsw.com/docs/voltscript/early-access/howto/writing/index.html.
+- Documentation uses Material for MKDocs framework:
+    - Write documentation in the relevant area of the docs directory.
+    - Preview documentation using MKDocs, either [locally installed with relevant plugins](https://squidfunk.github.io/mkdocs-material/getting-started/) or using the [MKDocs HCL Container Image](https://github.com/HCL-TECH-SOFTWARE/hcl-mkdocs-build-image)
+
+## PRs
+
+- When ready, complete a PR and submit.
+- Review the requirements for submitting a PR, for example writing test and updating documentation.

README.md

@@ -52,15 +52,16 @@ Obviously the code runs certain core language functions. These are documented in
 
 There are three new VoltScript language functions used - Try/Catch/Finally and GetThreadInfo(12) in TestRunner.vss and ++/-- in SampleBeforeAfterTester.vss.
 
-### Documentation
+## Contributing
 
-Documentation uses [Material for MKDocs](https://squidfunk.github.io/mkdocs-material/getting-started/#installation), which uses Markdown files in the docs directory. The [awesome-pages](https://github.com/lukasgeiter/mkdocs-awesome-pages-plugin) is the only additional plugin in use.
+See [CONTRIBUTING.md](contributing.md).
 
-This can be previewed using a Docker container or locally. To run locally, follow the [Material for MKDocs documentation](https://squidfunk.github.io/mkdocs-material/getting-started/#with-pip) and the steps to install awesome-pages plugin on their GitHub.
+## Code of Conduct
 
-To use with Docker, a Dockerfile has been included. In a terminal, navigate to the docker directory. Issue the command `docker build -t mkdocs-plus .` This creates a Docker image based on MKDocs Material image, adding the additional plugin. If you are using a M1 Mac, a different starting image will be needed, `ghcr.io/afritzler/mkdocs-material`, see https://github.com/afritzler/mkdocs-material.
+See [CODE_OF_CONDUCT.md](code_of_conduct.md).
 
-Once the Docker container is created, it can be started as a temporary container by:
+## Issues and discussions
 
-1. Open a terminal and navigate to this directory.
-2. Issue the command `docker run --rm -it -p 8000:8000 -v ${PWD}:/docs mkdocs-plus`. On Windows, `${PWD}` maps to the current directory for PowerShell, `%cd%` for a normal Windows cmd prompt. Other MKDocs commands can be appended, as required - see MKDocs documentation for more details.
+Let's chat on [OpenNTF Discord](https://openntf.org/discord).
+
+For long-running discussions, use Discussions area in GitHub. For bugs and feature requests **specific to VoltScript Testing Framework** use, Issues area.