podman/contrib/snapcraft
tomsweeneyredhat 9db657f40c Clean up more language for inclusiveness
We had a number of references, mostly in docs, to the word master that
can now be changed to main.  This PR does that and makes the project a
bit more inclusive.

[NO NEW TESTS NEEDED]

Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
2023-01-27 09:40:27 -05:00
..
snap Fix updated link to install instructions 2022-08-11 20:34:59 -04:00
.editorconfig Enable pre-commit tool linting 2020-01-14 13:42:59 +00:00
.gitignore start groundwork for adding snap 2019-08-13 08:57:07 -04:00
LICENSE start groundwork for adding snap 2019-08-13 08:57:07 -04:00
README.md Clean up more language for inclusiveness 2023-01-27 09:40:27 -05:00

README.md

podman

This is the snap for podman, “Managing Pods, Containers, and Container Images in Multiple Formats (Docker, OCI, ...).”. It works on Ubuntu, Fedora, Debian, RHEL, SUSE, and other major Linux distributions.

Published for with 💝 by Snapcrafters

Install

sudo snap install podman

(Don't have snapd installed?)

Remaining tasks

Snapcrafters (join us) are working to land snap install documentation and the snapcraft.yaml upstream so podman can authoritatively publish future releases.

  • Fork the Snapcrafters template repository to your own GitHub account.
    • If you have already forked the Snapcrafter template to your account and want to create another snap, you'll need to use GitHub's Import repository feature because you can only fork a repository once.
  • Rename the forked Snapcrafters template repository
  • Update the description of the repository
  • Update logos and references to podman and [podman]
  • Create a snap that runs in devmode
  • Register the snap in the store, using the preferred upstream name
  • Add a screenshot to this README.md
  • Publish the devmode snap in the Snap store edge channel
  • Add install instructions to this README.md
  • Update snap store metadata, icons and screenshots
  • Convert the snap to strict confinement, or classic confinement if it qualifies
  • Publish the confined snap in the Snap store beta channel
  • Update the install instructions in this README.md
  • Post a call for testing on the Snapcraft Forum - link
  • Make a post in the Snapcraft Forum asking for a transfer of the snap name from you to snapcrafters - link
  • Ask a Snapcrafters admin to fork your repo into github.com/snapcrafters, and configure the repo for automatic publishing into edge on commit
  • Add the provided Snapcraft build badge to this README.md
  • Publish the snap in the Snap store stable channel
  • Update the install instructions in this README.md
  • Post an announcement in the Snapcraft Forum - link
  • Submit a pull request or patch upstream that adds snap install documentation - link
  • Submit a pull request or patch upstream that adds the snapcraft.yaml and any required assets/launchers - link
  • Add upstream contact information to the README.md
  • If upstream accept the PR:
    • Request upstream create a Snap store account
    • Contact the Snap Advocacy team to request the snap be transferred to upstream
  • Ask the Snap Advocacy team to celebrate the snap - link

If you have any questions, post in the Snapcraft forum.