You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/community_contributions.md
+11-19Lines changed: 11 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,21 @@
1
1
+++
2
-
title = "Community Contributions"
2
+
title = "Community contributions"
3
3
draft = false
4
4
gh_repo = "chef-web-docs"
5
5
aliases = ["/community_contributions.html"]
6
6
product = []
7
7
8
8
[menu]
9
9
[menu.overview]
10
-
title = "Community Contributions"
10
+
title = "Community contributions"
11
11
identifier = "overview/community/contributing"
12
12
parent = "overview/community"
13
13
weight = 10
14
14
+++
15
15
<!-- markdownlint-disable-file MD033 -->
16
16
We're glad you want to contribute to a Chef project! This guide will help answer common questions you may have during your first contribution.
17
17
18
-
## Submitting Issues
18
+
## Submitting issues
19
19
20
20
Not every contribution comes in the form of code. Submitting, confirming, and triaging issues is an important task for any project. At Chef we use GitHub to track all project issues.
21
21
@@ -29,32 +29,24 @@ We ask you not to submit security concerns using GitHub. For details on submitti
29
29
30
30
In addition to GitHub issues, we also use a feedback site that helps our product team track and rank feature requests. If you have a feature request, [this is an excellent place to start](https://chef-software.ideas.aha.io/).
31
31
32
-
The following repositories are the preferred locations for the creation of issues and bug reports:
33
-
34
-
{{< repos >}}
35
-
36
32
For additional support about Chef products, including documentation, learning, and opening tickets with the support team, see [Chef Support](https://www.chef.io/support) .
37
33
38
-
{{< warning >}}
34
+
{{< note >}}
39
35
40
36
If you require a response from Chef for each the terms of a support level agreement (SLA), please contact [Chef Support](https://www.chef.io/support) directly.
41
37
42
-
{{< /warning >}}
43
-
44
-
{{< note >}}
45
-
46
-
Questions on how to use Chef Infra should be sent as Support Tickets if you have an SLA, or asked on the [Chef Software Mailing List](https://discourse.chef.io/), or [Chef Community Slack](https://community-slack.chef.io/). Bug Trackers aren't appropriate for general purpose questions that aren't bugs.
38
+
Questions on how to use Chef Infra should be sent as support tickets if you have an SLA, or asked on the [Chef Software Mailing List](https://discourse.chef.io/), or [Chef Community Slack](https://community-slack.chef.io/). Bug Trackers aren't appropriate for general purpose questions that aren't bugs.
47
39
48
40
{{< /note >}}
49
41
50
-
## Contribution Process
42
+
## Contribution process
51
43
52
44
Follow these steps to submit a contribution:
53
45
54
46
1. Fork the project repository to your own GitHub account.
55
47
2. Commit your changes to your fork, making sure to sign-off those changes for the Developer Certificate of Origin with `git commit -s`
56
-
3. Create a GitHub Pull Request for your change, following the instructions in the pull request template.
57
-
4. Perform a Code Review with the project maintainers on the pull
48
+
3. Create a GitHub pull request for your change, following the instructions in the pull request template.
49
+
4. Perform a code review with the project maintainers on the pull
58
50
request.
59
51
60
52
## About the Apache License
@@ -124,15 +116,15 @@ Chef doesn't merge any pull requests made against a Chef-managed open source rep
124
116
* Pull requests made against the docs.chef.io documentation repository (<https://github.com/chef/chef-web-docs>)
125
117
* Pull requests that contain only documentation updates made against projects where the documentation is embedded in the project's repository (that's, the `docs` directory in the `chef/inspec` repository)
126
118
127
-
## The "Obvious Fix" Rule
119
+
## The Obvious Fix Rule
128
120
129
121
Chef's contribution policy is aimed at encouraging broad participation from our community, and minimizing risks to Chef and our community due to inappropriate contributions of the intellectual property of others.
130
122
131
123
As a general standard, Chef requires every contribution to by signed for the Developer Certificate of Origin (DCO).
132
124
133
125
HOWEVER, small contributions such as fixing spelling errors, where the content is small enough to not be considered intellectual property, can be submitted by a contributor as a patch, without a DCO sign-off. If you submit an obvious fix without a DCO sign-off, then you are agreeing that your submission isn't independently copyrightable. The purpose of this exception is to lower the barrier for new contributors to make contributions while retaining the integrity of the project and our community.
134
126
135
-
### How does the Obvious Fix Rule Work?
127
+
### How does the Obvious Fix Rule work?
136
128
137
129
Any committer may commit fixes without a DCO sign-off for obvious typos, grammar mistakes, and formatting problems wherever they may be * in the web pages, API documentation, source code, etc.
An obvious fix is a pull request that doesn't contain creative work. We rely on your judgment to determine what's "obvious"; if you're not sure, just ask by sending an email to: oss AT getchef DOT com.
0 commit comments