File: README.md
Community at Harness
Hello and welcome to the Harness Community! We are glad to have you here. 👋 👋
This is the starting point for joining and contributing to the Harness Community.
Table of Contents
Community
The Harness Community lives in Slack! Please take a moment to introduce yourself in our #intro-yourself channel and tell us about who you are, what you are building, and what interests you! Then use the channel browswer to look at our other channels like #events or product specific channels like #drone or #cd-community
We also host events within the Harness User Group which encompass everything from office hours to technical deep dives!
🔎 Where to Seek Help 🔍
We have two main channels for seeking help and assistance.
We encourage you to use our Slack to ask for help with any issue.
Contributing
We expect contributors to abide by our underlying code of conduct. All conversations and discussions on GitHub (issues, pull requests) and across Harness socials must be respectful and harassment-free.
If you feel another member of the community has violated our Code of Conduct, you may anonymously contact the team with our code of conduct report form.
Remember that communication is the crucial to any project. We are all working on this together, and we are all benefiting from this software. It's very easy to misunderstand one another over asynchronous, text-based conversations: When in doubt, assume everyone within this project has the best intentions.
Code of Conduct
Our code of conduct is adapted from the Contributor Covenant and can be found here.
File: CODE_OF_CONDUCT.md
Harness Code of Conduct
As contributors and maintainers in the Harness community, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
We are committed to making participation in the Harness community a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
Scope
This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
Our Standards
Examples of behavior that contributes to a positive environment 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 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
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. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team.
Reporting
For incidents occurring in the Harness community, contact [email protected] or use this form to submit with the option of remaining anonymous. You can expect a response within three business days. Use of an outside mediator can be requested when reporting or used at Harness staff's discretion. In general, contacting [email protected] directly is preferred.
Enforcement
Harness’ Community Relations committee enforces code of conduct issues. Both bodies try to resolve incidents without punishment, but may remove people from the project or Harness communities at their discretion.
Acknowledgements
This Code of Conduct is adapted from the Contributor Covenant, version 2.0 available here.
File: CONTRIBUTING.md
Contributing to Harness Community Repositories
We currently accept contributions to Drone as well as Harness CD Community
Proposing Changes to Drone
Introduction
The Drone project's development process is design-driven. Significant changes to the project, libraries, or tools must be first discussed, and sometimes formally documented, before they can be implemented.
This document describes the process for proposing, documenting, and implementing changes to the Drone project.
The Proposal Process
Goals
- Make sure that proposals get a proper, fair, timely, recorded evaluation with a clear answer.
- Make past proposals easy to find, to avoid duplicated effort.
- If a design doc is needed, make sure contributors know how to write a good one.
Definitions
- A proposal is a suggestion filed as a GitHub issue, identified by having the Proposal label.
- A design doc is the expanded form of a proposal, written when the proposal needs more careful explanation and consideration.
Scope
The proposal process should be used for any notable change or addition to the project, libraries and tools. Since proposals begin (and will often end) with the filing of an issue, even small changes can go through the proposal process if appropriate. Deciding what is appropriate is matter of judgment we will refine through experience. If in doubt, file a proposal.
Yaml changes
Drone is a mature project with thousands of active installations, as such, significant or breaking yaml changes are unlikely to be accepted.
Process
Create an issue describing the proposal.
The proposal is followed by an initial discussion about the suggestion.
- The goal of the initial discussion is to reach agreement on the next step:
(1) accept, (2) decline, or (3) ask for a design doc. - The discussion is expected to be resolved in a timely manner.
- If the author wants to write a design doc, then they can write one.
- The goal of the initial discussion is to reach agreement on the next step:
If a Proposal issue leads to a design doc:
- The design doc should be checked in to the proposal repository as
design/{number}-{shortname}.md, where{number}is the GitHub issue number and{shortname}is a short title. - The design doc should address any specific issues asked for during the initial discussion.
- It is expected that the design doc may go through multiple checked-in revisions.
- Comments on the proposal should be addressed to the related GitHub issue.
- The design doc should be checked in to the proposal repository as
Once comments and revisions on the design doc wind down, there is a final discussion about the proposal.
- The goal of the final discussion is to reach agreement on the next step:
(1) accept or (2) decline. - The discussion is expected to be resolved in a timely manner.
- The goal of the final discussion is to reach agreement on the next step:
The author (and/or other contributors) do the work as described by the "Implementation" section of the proposal.
Help
If you need help with this process, please contact the project contributors by posting
to the Slack channel.
File: .github/ISSUE_TEMPLATE/bug-report--bug--.md
name: 'Bug report :bug: '
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.