Skip to content

Communication

The Progress Chef Community is committed to keeping our space a fun, safe, and productive place to be, so please review the Community Code of Conduct before getting started. In general:

  • Be Kind — We get more done when people are helpful and respectful of one another. Plus, it feels better.
  • Listen — Try to understand someone's position before you respond to their suggestion or idea. Ask clarifying questions if something doesn't make sense to you. Understand that others may have a perspective, experience, or technical context that is different from your own.
  • Be Patient — We have no engineering team dedicated solely to Chef Community support, so responses will be semi-synchronous, or, more likely, asynchronous. Know that the Community appreciates all your contributions, and we're working to be as responsive as possible.

Reporting Code of Conduct Violations

Please email the Community Advocates listed in the Code of Conduct.

Reporting Security Vulnerabilities

If you discover a security vulnerability in this project, we kindly ask that you follow a responsible disclosure process. If any users, contributor, or security researchers find vulnerabilities, we ask that they responsibly report them by submitting them directly to us. This allows us time to investigate, develop a fix, and coordinate a release before disclosing the details publicly. Responsible disclosure helps protect users from potential exploitation and ensures that vulnerabilities are addressed in a safe and transparent manner. We appreciate your help in keeping the project and its users secure.

To submit a vulnerability, you please follow these instructions. It is important to us that we work together with the community to protect against threats.

What is Responsible Disclosure

Responsible disclosure is a vital practice when reporting Common Vulnerabilities and Exposures (CVEs), ensuring that security flaws are communicated ethically and effectively. It involves privately notifying the affected vendor or organization about the vulnerability, giving them adequate time to investigate and implement a fix before the details are made public. This approach helps prevent malicious exploitation while promoting transparency and collaboration within the cybersecurity community. By following responsible disclosure protocols, researchers contribute to a safer digital ecosystem while respecting the integrity of affected systems and users.

Communication Channels

Progress Chef uses a variety of communication channels, each serving a distinct purpose within our open source community. These channels help balance open collaboration with efficiency. If you're ever unsure about why a particular channel is used for a specific type of discussion, please refer to our Communication FAQ.

Aha! (Ideas Portal)

Progress Chef uses the Ideas Portal (powered by Aha!) to capture feature requests, platform support needs, and product suggestions. Community members can submit ideas they’d like Progress to prioritize in future roadmaps.

  • This is the best place to propose new platforms, integrations, or features.
  • Suggestions can be voted on, tracked, and reviewed by product management.
  • Not all ideas are guaranteed for implementation, but Aha! is the official intake path for roadmap consideration.

Jira (Internal System of Record)

Jira is the internal authoritative source of truth for all engineering work, release schedules, and project tracking across Chef products.

  • All Progress employees use Jira to manage sprints, epics, and releases.
  • External contributors will not have access to Jira; relevant updates will be surfaced via PR, GitHub issues, Architecture Decision Records, proposals, or discussions when appropriate.
  • Jira decisions and status updates will be summarized in weekly Community Meeting updates on Slack.

GitHub (Open Source Collaboration Hub)

GitHub is the primary communication platform for the open source community and the system of record for all technical collaboration across Progress Chef’s OSS projects. All issue discussions, code reviews, proposals, and community decisions must be captured in GitHub to ensure visibility and long-term traceability.

  • If a decision or insight originates from Slack, Zoom, or any other medium, it must be summarized in the relevant GitHub issue, pull request, or discussion.
  • GitHub reflects community-facing planning, contributor workflows, technical documentation, and change history.

Note: GitHub is not used for internal Progress team release planning or enterprise roadmap management. See the Aha! and Jira sections above for more on those systems.

Community Slack

Slack is used for ad hoc, ephemeral conversations. It’s perfect for clarifying questions, discussing active issues, or unblocking someone quickly.

  • Use Slack for non-durable exchanges, but ensure important decisions are reflected back in the Aha! Ideas Portal or GitHub.
  • Limit usage to project-specific channels and respect the boundary between informal chats and durable record keeping.

Note: The Chef Community Slack workspace is on a free tier Slack plan. There are several thousand members of the Workspace, and Slack's per-user pricing makes a commercial account untenable. This means that message retention in Slack is only 90 days, making it even more important to persist durable decisions back to an official channel.

Community Meetings are held, in text form, in the #community-meetings channel of the Chef Community Slack. These updates are posted nearly every Thursday at 12:00 noon Eastern Time U.S.

The Community Advisory Council meets monthly, via public Zoom, generally on the second Thursday of the month at 1:00 p.m. Eastern Time U.S. It is organized in the #community-advisory-council channel, where recordings of past meetings are also occasionally shared.

Discourse Mailing Lists

The Chef Community uses Discourse as our primary mailing list platform. This is the best place to:

  • Follow security announcements and release updates.
  • Engage in general community discussion.
  • Ask non-urgent, broad questions that don’t fit neatly into GitHub issues or Slack threads.