From 9d0bf08ad9682a7ec3487a6f1435b138e3805750 Mon Sep 17 00:00:00 2001 From: Nathan Wallace Date: Tue, 5 Mar 2024 17:36:36 -0500 Subject: [PATCH] Remove org-wide files. Draft changelog for v0.1.0. --- CHANGELOG.md | 18 +++++++++++ CODE_OF_CONDUCT.md | 74 ---------------------------------------------- CONTRIBUTING.md | 20 ------------- SECURITY.md | 10 ------- 4 files changed, 18 insertions(+), 104 deletions(-) delete mode 100644 CODE_OF_CONDUCT.md delete mode 100644 CONTRIBUTING.md delete mode 100644 SECURITY.md diff --git a/CHANGELOG.md b/CHANGELOG.md index e69de29b..c29357c0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -0,0 +1,18 @@ + +## v0.1.0 [2024-03-05] + +Introducing Powerpipe - Dashboards for DevOps. + +*Benchmarks* - 5,000+ open-source controls from CIS, NIST, PCI, HIPAA, FedRamp and more. Run instantly on your machine or as part of your deployment pipeline. + +*Relationship Diagrams* - The only dashboarding tool designed from the ground up to visualize DevOps data. Explore your cloud,understand relationships and drill down to the details. + +*Dashboards & Reports* - High level dashboards provide a quick management view. Reports highlight misconfigurations and attention areas. Filter, pivot and snapshot results. + +*Code, not clicks* - Our dashboards are code. Version controlled, composable, shareable, easy to edit - designed for the way you work. Join our open-source community! + +Learn more at: +- Website - https://powerpipe.io +- Docs - https://powerpipe.io/docs +- Hub - https://hub.powerpipe.io +- Introduction - https://powerpipe.io/blog/introducing-powerpipe \ No newline at end of file diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index 66bac053..00000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,74 +0,0 @@ -## Code of Conduct - -### Our Pledge - -In the interest of fostering an open and welcoming environment, we as members, -contributors and maintainers pledge to making participation in our project and -our community a harassment-free experience for everyone, regardless of age, body -size, disability, ethnicity, gender identity and expression, level of experience, -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 both within project spaces and in public spaces -when an individual is representing the project or its community. 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 [help@turbot.com](mailto:help@turbot.com). 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. - -### Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, -available at [http://contributor-covenant.org/version/1/4][version] - -[homepage]: http://contributor-covenant.org -[version]: http://contributor-covenant.org/version/1/4/ diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 3498f481..00000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,20 +0,0 @@ -# Contributing to Steampipe - -Because Open Source plays a major part in how we build our products, -we see it as a matter of course to give the same effort back to our -community by creating extensible and easy-to-use software. - -We welcome contributions from the community and have created some -resources to help you get started extending Powerpipe: - -## Steampipe Architecture - -https://powerpipe.io/docs/develop/architecture - -## Naming Standards - -https://powerpipe.io/docs/develop/standards - -## Coding Standards - -https://steampipe.io/docs/develop/coding-standards diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index 1da4ddae..00000000 --- a/SECURITY.md +++ /dev/null @@ -1,10 +0,0 @@ -We deeply appreciate any effort to discover and disclose security vulnerabilities responsibly. - -If you would like to report a vulnerability in one of our products, or have security concerns regarding Turbot or Steampipe software, please email security@turbot.com. - -In order for us to best respond to your report, please include any of the following: -* Steps to reproduce or proof-of-concept -* Any relevant tools, including versions used -* Tool output - -For additional information about Turbot security, please see https://turbot.com/security.