Warning

This page in the Chef Open Source Software Practices repository is currently undergoing content review.

Getting in Touch

Below are recommended ways to engage with the Progress Chef community, depending on your role and intent. These examples help ensure that communication happens in the right place, with the right visibility.

As...	If I want to...	I should...	Notes
Anyone	Become a Project Member	Review the project membership guide	Membership criteria may differ by project.
Anyone	Report a bug	Open an issue in the appropriate GitHub repository	See the project's issue template.
Anyone	Submit a feature request	Submit an idea in the Aha! Ideas Portal	Best way to influence product roadmap. GitHub feature requests may be redirected here.
Anyone	Report a security vulnerability	Email security@chef.io	Please include detailed reproduction steps.
Anyone	Report a service outage	Email [email address TBD]
Project Member	Join a Community Slack channel	Visit Community Slack	Use project-specific dev channels for technical topics.
Project Member	Discuss technical issues	Post or comment on GitHub	Use Slack for real-time clarification, but document important decisions in GitHub.
Project Member	Get technical help	Start in GitHub, or ask in Slack if quick feedback is needed	Make sure resolutions are logged back in GitHub.
Project Member	Find something to work on	Look for issues tagged help wanted or good first issue on GitHub	Confirm interest in GitHub before starting work to avoid duplication.
Project Member	Check community announcements	Follow Discourse	Major release and security announcements also appear here.
Project Member	Regain access to an account	[Support contact TBD]
Project Member	Request a PR review	Use GitHub and tag the appropriate reviewers or approvers	Reviews must meet project criteria (e.g., 2 approvals including 1 Progress employee).
Project Member	Have a quick discussion	Use Community Slack	For non-durable chat. Outcomes should be summarized in GitHub.
Project Member	Become a Reviewer	Review Reviewer responsibilities and requirements	Nominations and sponsors required.
Project Member	Report a Code of Conduct violation	Email [email address TBD]	All reports are handled confidentially.
Project Member	Join project office hours	Check project documentation or GitHub Discussions	Typically held via Zoom and recorded when possible.
Reviewer	Become an Approver	Review Approver requirements	Requires sustained contributions, nomination, and team consensus.
Approver	Vote on a new Reviewer or Approver	Follow membership process in Project Membership	Votes are conducted in GitHub and require documentation in CODEOWNERS/TEAMS.
Contributor	Request a new platform, integration, or commercial feature	Submit an idea in the Aha! Ideas Portal	Managed by product management; preferred route for enhancements that require Progress investment.
Progress Staff	Track internal engineering work, sprints, or releases	Use Jira	Jira is the internal system of record; status may be reflected back in GitHub as appropriate.