Skip to content

Remove this page #4466

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 27, 2025
Merged

Remove this page #4466

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
94ec0d5
Remove this page
IanMadd Aug 12, 2025
436e4af
Minor cleanup of content
IanMadd Aug 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 11 additions & 19 deletions content/community_contributions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,21 +1,21 @@
+++
title = "Community Contributions"
title = "Community contributions"
draft = false
gh_repo = "chef-web-docs"
aliases = ["/community_contributions.html"]
product = []

[menu]
[menu.overview]
title = "Community Contributions"
title = "Community contributions"
identifier = "overview/community/contributing"
parent = "overview/community"
weight = 10
+++
<!-- markdownlint-disable-file MD033 -->
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.

## Submitting Issues
## Submitting issues

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.

Expand All @@ -29,32 +29,24 @@ We ask you not to submit security concerns using GitHub. For details on submitti

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/).

The following repositories are the preferred locations for the creation of issues and bug reports:

{{< repos >}}

For additional support about Chef products, including documentation, learning, and opening tickets with the support team, see [Chef Support](https://www.chef.io/support) .

{{< warning >}}
{{< note >}}

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.

{{< /warning >}}

{{< note >}}

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.
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.

{{< /note >}}

## Contribution Process
## Contribution process

Follow these steps to submit a contribution:

1. Fork the project repository to your own GitHub account.
2. Commit your changes to your fork, making sure to sign-off those changes for the Developer Certificate of Origin with `git commit -s`
3. Create a GitHub Pull Request for your change, following the instructions in the pull request template.
4. Perform a Code Review with the project maintainers on the pull
3. Create a GitHub pull request for your change, following the instructions in the pull request template.
4. Perform a code review with the project maintainers on the pull
request.

## About the Apache License
Expand Down Expand Up @@ -124,15 +116,15 @@ Chef doesn't merge any pull requests made against a Chef-managed open source rep
* Pull requests made against the docs.chef.io documentation repository (<https://github.com/chef/chef-web-docs>)
* 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)

## The "Obvious Fix" Rule
## The Obvious Fix Rule

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.

As a general standard, Chef requires every contribution to by signed for the Developer Certificate of Origin (DCO).

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.

### How does the Obvious Fix Rule Work?
### How does the Obvious Fix Rule work?

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.

Expand All @@ -151,7 +143,7 @@ Date: Wed Sep 18 11:44:40 2015 -0700
------------------------------------------------------------------------
```

### What qualifies as an Obvious Fix?
### What qualifies as an obvious fix?

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.

Expand Down
15 changes: 7 additions & 8 deletions content/feedback.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,25 +1,25 @@
+++
title = "Send Feedback"
title = "Send feedback"
draft = false
gh_repo = "chef-web-docs"
aliases = ["/feedback.html"]
product = []

[menu]
[menu.overview]
title = "Send Feedback"
title = "Send feedback"
identifier = "overview/community/feedback.md Send Feedback"
parent = "overview/community"
weight = 50
+++

chef-docs hopes that the documentation is always just what you are
looking for, but when that isn't the case we do appreciate
feedback. There are several ways to get feedback to chef-docs. For
feedback. There are several ways to get feedback to the Chef Documentation Team. For

Check failure on line 18 in content/feedback.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[write-good.ThereIs] Don't start a sentence with 'There are'.

Raw Output:
{"message": "[write-good.ThereIs] Don't start a sentence with 'There are'.", "location": {"path": "content/feedback.md", "range": {"start": {"line": 18, "column": 11}}}, "severity": "ERROR"}
members of the Chef community, customers, or people who just want to
send feedback, choose any of the following options:

## Feedback Form
## Feedback form

Every page in [docs.chef.io](https://docs.chef.io) has a feedback form
at the bottom of the page. Please feel free to include any thoughts or
Expand All @@ -38,13 +38,12 @@
not a support email address, however. If you need support,
contact [Chef support](https://supportlink.chef.io/).

## GitHub Issues
## GitHub issues

Open an issue in <https://github.com/chef/chef-web-docs/issues>
on GitHub. If you believe the issue may be a product bug within a Chef
itself, consider opening an issue in the relevant [product repository]({{< relref "repositories" >}}).
on GitHub.

## GitHub Pull Request
## GitHub pull request

You can open a pull request on <https://github.com/chef/chef-web-docs>.
Every page on <https://docs.chef.io> has a link to the Markdown page in the repository
Expand Down
10 changes: 0 additions & 10 deletions content/repositories.md
View file
Open in desktop

This file was deleted.

70 changes: 0 additions & 70 deletions layouts/shortcodes/repos.html
View file
Open in desktop

This file was deleted.

Loading