Add CoC, Contributing and Security markdown

Author: hughwphamill

CODE_OF_CONDUCT.md

@@ -0,0 +1,78 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, 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.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [[email protected]][conduct-email]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific 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 other
+members of the project's leadership.
+
+[conduct-email]: mailto:[email protected]
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,68 @@
+# How to Contribute
+
+Thank you for your interest in contributing to the dCloud Terraform Provider project! To ensure smooth collaboration and effective development, please review the following guidelines. By following these guidelines, you demonstrate respect for the time and efforts of the project's contributors. In return, they will reciprocate by addressing your issues, evaluating changes, and assisting with your pull requests. We strive to review incoming issues and pull requests within 10 days. Any lingering issues or pull requests inactive for 60 days will be closed.
+
+Please note that all interactions within the project are subject to our [Code of Conduct](/CODE_OF_CONDUCT.md). This applies to creating issues or pull requests, commenting on them, as well as any real-time discussions in platforms like Slack, Discord, etc.
+
+## Table Of Contents
+
+- [Troubleshooting and Debugging](#troubleshooting-and-debugging)
+- [Reporting Issues](#reporting-issues)
+- [Development](#development)
+    - [Setting up the Development Environment](#setting-up-the-development-environment)
+    - [Building the dCloud Terraform Provider](#building-the-dcloud-topology-builder-go-client)
+    - [Running Tests](#running-tests)
+- [Sending Pull Requests](#sending-pull-requests)
+- [Other Ways to Contribute](#other-ways-to-contribute)
+
+## Reporting Issues
+
+Before reporting a new issue, please search our [issues list](https://github.com/cisco-open/kapua-tb-go-client/issues) to ensure that it hasn't already been reported or fixed.
+
+When creating a new issue, include a clear title, a detailed description, relevant information, and if possible, a test case.
+
+**If you discover a security vulnerability, please refrain from reporting it through GitHub. Instead, follow the security procedures outlined in [SECURITY.md](/SECURITY.md).**
+
+## Development
+
+### Setting up the Development Environment
+
+To set up your development environment for the dCloud Terraform Provider, follow the instructions below:
+
+1. Clone the repository: `git clone https://github.com/cisco-open/terraform-provider-dcloudtb.git`
+2. Navigate to the project directory: `terraform-provider-dcloudtb`
+3. Install the necessary dependencies: https://go.dev/doc/install, https://developer.hashicorp.com/terraform
+
+### Building the dCloud Terraform Provider
+
+To build the dCloud Terraform Provider, execute the following steps:
+
+1. Install Go
+2. Execute the following from the root of the repository: `go build .`
+
+### Running Examples
+
+To run the example terraform definitions for the dCloud Terraform Provider, do the following:
+
+1. Navigate to each example directory under `/examples`
+2. Execute `terraform init`
+3. Create an environment variable to hold your Cisco Authentication Token (use a valid token) `export TB_AUTH_TOKEN=abc123`
+4. Execute `terraform apply`
+
+## Sending Pull Requests
+
+Before submitting a new pull request, please check existing pull requests and issues to ensure that your proposed changes or fixes haven't been discussed in the past or already implemented but not released.
+
+When submitting a pull request, include tests for any affected behavior. As we follow semantic versioning, breaking changes may be reserved for the next major version release.
+
+## Other Ways to Contribute
+
+We welcome contributions beyond code. Here are some ways you can contribute to the dCloud Terraform Provider project:
+
+- Help triage and respond to open issues, providing troubleshooting assistance and suggesting fixes.
+- Review existing pull requests and test patches against real applications that use the dCloud Terraform Provider.
+- Write new tests or add missing test cases to existing tests.
+
+Thank you for your interest in contributing to the dCloud Terraform Provider project!
+
+:heart:

SECURITY.md

@@ -0,0 +1,39 @@
+# Security Policies and Procedures
+
+This document outlines security procedures and general policies for the
+dCloud Terraform Provider project.
+
+- [Reporting a Bug](#reporting-a-bug)
+- [Disclosure Policy](#disclosure-policy)
+- [Comments on this Policy](#comments-on-this-policy)
+
+## Reporting a Bug
+
+The dCloud Terraform Provider team and community take all security bugs in
+the dCloud Terraform Provider seriously. Thank you for improving the security of the
+dCloud Terraform Provider. We appreciate your efforts and responsible disclosure and
+will make every effort to acknowledge your contributions.
+
+Report security bugs by emailing `[email protected]`.
+
+The lead maintainer will acknowledge your email within 48 hours, and will send a
+more detailed response within 48 hours indicating the next steps in handling
+your report. After the initial reply to your report, the security team will
+endeavor to keep you informed of the progress towards a fix and full
+announcement, and may ask for additional information or guidance.
+
+## Disclosure Policy
+
+When the security team receives a security bug report, they will assign it to a
+primary handler. This person will coordinate the fix and release process,
+involving the following steps:
+
+- Confirm the problem and determine the affected versions.
+- Audit code to find any potential similar problems.
+- Prepare fixes for all releases still under maintenance. These fixes will be
+  released as quickly as possible.
+
+## Comments on this Policy
+
+If you have suggestions on how this process could be improved please submit a
+pull request.