-1 #ˆl–ß=¿J•7µ8 Eq–î2ò˜´o¿ „€ËßÂÁ?÷![PODMAN logo](https://raw.githubusercontent.com/containers/common/main/logos/podman-logo-full-vert.png) # Contributing to Podman We'd love to have you join the community! Below summarizes the processes that we follow. ## Topics * [Reporting Issues](#reporting-issues) * [Working On Issues](#working-on-issues) * [Contributing to Podman](#contributing-to-podman) * [Continuous Integration](#continuous-integration) [![Build Status](https://api.cirrus-ci.com/github/containers/podman.svg)](https://cirrus-ci.com/github/containers/podman/main) * [Submitting Pull Requests](#submitting-pull-requests) * [Communications](#communications) ## Reporting Issues Before reporting an issue, check our backlog of [open issues](https://github.com/containers/podman/issues) to see if someone else has already reported it. If so, feel free to add your scenario, or additional information, to the discussion. Or simply "subscribe" to it to be notified when it is updated. Please do not add comments like "+1" or "I have this issue as well" without adding any new information. Instead, please add a thumbs-up emoji to the original report. Note: Older closed issues/PRs are automatically locked. If you have a similar problem please open a new issue instead of commenting. If you find a new issue with the project we'd love to hear about it! The most important aspect of a bug report is that it includes enough information for us to reproduce it. To make this easier, there are three types of issue templates you can use. * If you have a bug to report, please use *Bug Report* template. * If you have an idea to propose, please use the *Feature Request* template. * If your issue is something else, please use the default *Blank issue* template. Please include as much detail as possible, including all requested fields in the template. Not having all requested information - for example, a full `podman info` - makes it much harder to find and fix issues. A reproducer is the best thing you can include. Reproducers make finding and fixing issues much easier for maintainers. The easier it is for us to reproduce a bug, the faster it'll be fixed! Please don't include any private/sensitive information in your issue! Security issues should NOT be reported via Github and should instead be reported via the process described [here](https://github.com/containers/common/blob/main/SECURITY.md). ## Working On Issues Once you have decided to contribute to Podman by working on an issue, check our backlog of [open issues](https://github.com/containers/podman/issues) looking for any that are unassigned. If you want to work on a specific issue that is already assigned but does not appear to be actively being worked on, please ping the assignee in the issue and ask if you can take over. If they do not respond after several days, you can notify a maintainer to have the issue reassigned. When working on an issue, please assign it to yourself. You can use the `/assign` bot command in a comment on an issue to assign it to yourself. If you lack permissions to do so, you can ping the `@containers/podman-maintainers` group to have a maintainer set you as assignee. If you are a maintainer of Podman project, please following the [instructions](https://github.com/containers/podman/blob/main/TRIAGE.md) to triage new issues. ## Contributing to Podman This section describes how to make a contribution to Podman. These instructions are geared towards using a Linux development machine, which is required for doing development on the Podman backend. Development for the Windows and Mac clients can also be done on those operating systems. Check out these instructions for building the Podman client on [MacOSX](./build_osx.md) or [Windows](./build_windows.md). ### Prepare your environment Read the [install documentation to see how to install dependencies](https://podman.io/getting-started/installation#build-and-run-dependencies). The install documentation will illustrate the following steps: - Installation of required libraries and tools -