|
1 | | -> [!WARNING] |
2 | | -> This page in the Chef Open Source Software Practices repository is currently undergoing content review. |
| 1 | +!!! warning |
| 2 | + This page in the Chef Open Source Software Practices repository is currently undergoing content review. |
3 | 3 |
|
4 | | -- **[Project State](https://github.com/chef/chef-oss-practices/blob/master/repo-management/repo-states.md): Active** |
5 | | -- **Issues [Response Time Maximum](https://github.com/chef/chef-oss-practices/blob/master/repo-management/repo-states.md): 7 days** |
6 | | -- **Pull Request [Response Time Maximum](https://github.com/chef/chef-oss-practices/blob/master/repo-management/repo-states.md): 7 days** |
7 | 4 |
|
8 | | -# Chef Software Open Source Communities |
| 5 | +# Progress Chef Communities |
| 6 | +Welcome to the Progress Chef Open Source community! |
9 | 7 |
|
10 | | -Welcome to the Chef Software Open Source communities! |
11 | | - |
12 | | -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. |
13 | | - |
14 | | -Looking for something specific? Check out our [Table of Contents](#table-of-contents). |
15 | | - |
16 | | -To learn more about each of our project's structure and organization, please refer to [Governance](./governance.md). |
17 | | - |
18 | | -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 to [contribute](./CONTRIBUTING.md)! |
19 | | - |
20 | | -## Inspiration |
21 | | - |
22 | | -The practices in this repo are inspired by [Adam Jacob's book on Free and Sustainable Open Source Communities](https://sfosc.org/). 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. |
| 8 | +This is your home for contributing to Progress Chef’s ecosystem. Whether you're improving a Chef Infra resource, improving documentation, crafting an InSpec control, extending Cookstyle, or building a new plugin — you’re in the right place. |
23 | 9 |
|
24 | 10 | ## How We're Organized |
| 11 | +Progress Software (the company) produces a range of Chef infrastructure automation products, such as **Chef Infra**, **Chef InSpec**, **Chef Habitat**, and the supporting ecosystem. These products are released and managed under Progress Chef’s **[Open Core](./policies/open-core.md)** model. |
25 | 12 |
|
26 | | -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. |
| 13 | +All Progress Chef Open Source projects are released and under the [Apache 2.0 license](https://www.apache.org/licenses/LICENSE-2.0). These open source projects serve as the shared foundation for our global community, while advanced features and platform capabilities are part of the Chef 360 commercial offerings. |
27 | 14 |
|
28 | | -All Chef projects operate under governance determined by the Chef OSS Practices Committee. These policies are documented under [Governance](./governance.md); however, *Teams* can have their own [policy for contribution](./repo-management/project-required-setup.md#CONTRIBUTING.md), communication standards, etc. so long as those policies meet the base governance policy. |
| 15 | +Many of the Progress Chef products includes one or more open source [projects](./projects/README.md) — for example, the Chef Infra product is comprised of `chef`, `ohai`, various `mixlib` libraries, and other interdependent tools. |
29 | 16 |
|
30 | | -We decide on the long term plan for projects through [Project planning](./contributors/guide/project-planning.md) and our [triage and prioritization](./contributors/guide/#issues-management-or-triage.md) processes. |
31 | | - |
32 | | -## Communicating With Us |
| 17 | +All open source projects operate under and are governed by the policies outlined in our [Governance](./policies/governance.md) document. |
33 | 18 |
|
34 | | -The [communication](./communication/README.md) page lists communications channels such as chat, GitHub issues, mailing lists, conferences, etc. |
| 19 | +We decide on long-term plans and direction through structured [Project Planning](./contributors/guide/project-planning.md) and our [Triage and Prioritization](./contributors/guide/README.md#issues-management-or-triage) processes. |
35 | 20 |
|
36 | | -For more detailed information, check the README.md in a project's repository. |
| 21 | +## Join Us in Building the Future |
| 22 | +Whether you're a long-time contributor or a first-time user, we invite you to help shape the future of infrastructure automation. We are only as strong as the community around it — and we’re committed to making Chef's ecosystem one that is worth building together. |
37 | 23 |
|
38 | | -## Getting Started Contributing |
| 24 | +### Getting Started Contributing |
| 25 | +1. Browse the [Projects List](./projects/README.md) to find something you care about. |
| 26 | +2. Read the relevant CONTRIBUTING guide for that project (see project for details). |
| 27 | +3. Learn how to [find something to work on](./contributors/guide/README.md#find-something-to-work-on). |
| 28 | +4. Learn how to [open a pull request](./contributors/guide/README.md#open-a-pull-request). |
39 | 29 |
|
40 | | -A first step towards contributing is to pick from the [list of Chef Software Projects](./projects-list.md). |
41 | | - |
42 | | -Once you've selected a project to contribute to, be sure to read the team's [contribution guide](./CONTRIBUTING.md). That guide will provide information on issues in need of contributors, team meetings schedules, and Slack channels / mailing lists where project discussions take place. |
43 | | - |
44 | | -The [Contributor Guide](./contributors/guide/README.md) provides detailed instructions on how to get your code accepted to Chef Software projects, including: |
45 | | - |
46 | | -1. How to [file an issue](./contributors/guide/README.md#file-an-issue) |
47 | | -2. How to [find something to work on](./contributors/guide/README.md#find-something-to-work-on) |
48 | | -3. How to [open a pull request](./contributors/guide/README.md#open-a-pull-request) |
49 | | - |
50 | | -## Creating a New Chef Open Source Project |
51 | | - |
52 | | -Creating a new project? Check out the [repo management](./repo-management/README.md) documentation for information on how to set your project up. |
| 30 | +Visit the [Contributor Guide](./contributors/guide/README.md) for help filing issues, opening PRs, and more. |
53 | 31 |
|
54 | 32 | ## Project Membership |
55 | 33 |
|
56 | | -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 our [Project Membership](./project-membership.md) page. |
57 | | - |
58 | | -## Table of Contents |
59 | | - |
60 | | -- [README](./README.md) |
61 | | -- [Contributing](./CONTRIBUTING.md) |
62 | | -- [Project Membership](./project-membership.md) |
63 | | -- [Projects List](./projects-list.md) |
64 | | -- [Governance](./governance.md) |
65 | | -- [Developer Certificate of Origin](./DCO.md) |
| 34 | +We encourage all contributors to become project members. We aim to grow an active, healthy community of contributors, reviewers, and advisors. Learn about the requirements and perks of membership on our [Project Membership](./policies/project-membership.md) page. |
66 | 35 |
|
67 | | -### Code of Conduct |
68 | | - |
69 | | -- [Physical and Virtual Spaces Code of Conduct](./CODE_OF_CONDUCT.md) |
70 | | - |
71 | | -### Contributors |
72 | | - |
73 | | -- [Contributor Licenses through the Entitlement Program](./contributors/contributor-entitlement-program.md) |
74 | | - |
75 | | -### Distributions |
76 | | - |
77 | | -- [Distribution Guidelines](./distributions/distribution-guidelines.md) |
78 | | -- [Distribution List](./distributions/distribution-list.md) |
79 | | - |
80 | | -### Guide |
81 | | - |
82 | | -- [README](./contributors/guide/README.md) |
83 | | -- [Collaborative Development](./contributors/guide/collaborative-dev.md) |
84 | | -- [Community Expectations](./contributors/guide/community-expectations.md) |
85 | | -- [Contributor Cheatsheet](./contributors/guide/contributor-cheatsheet.md) |
86 | | -- [Design Proposals](./contributors/guide/design-proposals.md) |
87 | | -- [Help Wanted](./contributors/guide/help-wanted.md) |
88 | | -- [Project Planning](./contributors/guide/project-planning.md) |
89 | | -- [Pull Requests](./contributors/guide/pull-requests.md) |
90 | | -- [Ways to Contribute](./contributors/guide/ways-to-contribute.md) |
91 | | - |
92 | | -### Communication |
93 | | - |
94 | | -- [README](./communication/README.md) |
95 | | -- [Community Meetings](./communication/community-meetings.md) |
96 | | -- [Decider](./communication/decider.md) |
97 | | -- [Triage](./communication/triage.md) |
98 | | -- [Project End of Life](./communication/project-eol.md) |
99 | | -- [Video Conferencing](./communication/video-conferencing.md) |
100 | | -- [Support Boundaries](./communication/support-boundaries.md) |
101 | | -- [Saying No](./communication/saying-no.md) |
102 | | -- [Communication FAQ](./communication/communication-faq.md) |
103 | | - |
104 | | -### Repo Management |
105 | | - |
106 | | -- [README](./repo-management/README.md) |
107 | | -- [Project Setup](./repo-management/project-required-setup.md) |
108 | | -- [Repo States](./repo-management/repo-states.md) |
109 | | -- [GitHub Labels](./repo-management/github-labels.md) |
110 | | - |
111 | | -### Guilds |
112 | | - |
113 | | -- [README](./guilds/README.md) |
114 | | - |
115 | | -### Checklists |
| 36 | +## Communicating With Us |
116 | 37 |
|
117 | | -- [Managing Pull Requests](./checklists/managing-pull-requests.md) |
118 | | -- [New Projects](./checklists/new-project.md) |
| 38 | +The [communication](./communication/README.md) page lists communications channels such as chat, GitHub issues, mailing lists, conferences, etc. |
0 commit comments