Repository files navigation

• Project State: Active
• IssuesResponse Time Maximum: 7 days
• Pull RequestResponse Time Maximum: 7 days

Welcome to the Chef Software Open Source communities!

This is a starting point for contributing to all of Chef's software and a wonderful spot for information on how to join in on the fun.

Looking for something specific? Check out ourTable of Contents.

To learn more about each of our project's structure and organization, please refer toGovernance.

We are currently rolling out these processes to all of Chef's Open Source projects in stages and will be iterating as we go - we would love you tocontribute!

The practices in this repo are inspired byAdam Jacob's book on Free and Sustainable Open Source Communities. Although we are inspired by it, this repo is not a full implementation of the practices described in that book. However, this is only the first iteration of this repo. We expect this repo to continue to evolve and grow as we learn. We may integrate more of Adam's book into this repo in the future.

Chef Software (the company) produces many products such as Chef Infra, Chef InSpec, Chef Habitat, and Chef Automate. Each of these products is fully open source and comprised of one or more open source projects. For instance, the Chef Infra product is comprised of chef, ohai, various mixlib projects, and other interdependent libraries. The project and/or sub-project scope is defined in the README.md file in each individual project's GitHub repository.

All Chef projects operate under governance determined by the Chef OSS Practices Committee. These policies are documented underGovernance; however,Teams can have their ownpolicy for contribution, communication standards, etc. so long as those policies meet the base governance policy.

We decide on the long term plan for projects throughProject planning and ourtriage and prioritization processes.

Thecommunication page lists communications channels such as chat, GitHub issues, mailing lists, conferences, etc.

For more detailed information, check the README.md in a project's repository.

A first step towards contributing is to pick from thelist of Chef Software Projects.

Once you've selected a project to contribute to, be sure to read the team'scontribution guide. That guide will provide information on issues in need of contributors, team meetings schedules, and Slack channels / mailing lists where project discussions take place.

TheContributor Guide provides detailed instructions on how to get your code accepted to Chef Software projects, including:

1. How tofile an issue
2. How tofind something to work on
3. How toopen a pull request

Creating a new project? Check out therepo management documentation for information on how to set your project up.

We encourage all contributors to become project members. We aim to grow an active, healthy community of contributors, reviewers, and project owners. Learn about requirements and perks of membership in ourProject Membership page.

• README
• Contributing
• Project Membership
• Projects List
• Governance
• Developer Certificate of Origin

• Physical and Virtual Spaces Code of Conduct

• Contributor Licenses through the Entitlement Program

• Distribution Guidelines
• Distribution List

• README
• Collaborative Development
• Community Expectations
• Contributor Cheatsheet
• Design Proposals
• Help Wanted
• Project Planning
• Pull Requests
• Ways to Contribute

• README
• Community Meetings
• Decider
• Triage
• Project End of Life
• Video Conferencing
• Support Boundaries
• Saying No
• Communication FAQ

• README
• Project Setup
• Repo States
• GitHub Labels

• README

• Managing Pull Requests
• New Projects