maggesandClaude Sonnet 5
e2fefcdf9c
- versions.env pins podman, conmon, crun, netavark, aardvark-dns, passt, and fuse-overlayfs to verified upstream source checksums; SlackBuild recipes, scripts/build-packages.sh, checksums.sh, release.sh, and update-versions.sh implement the reproducible pipeline; GitHub Actions workflows build in a Slackware container and publish releases without committing any binaries. - plugin/podman.plg installs/updates/removes all eight packages (the seven components plus the plugin's own unraid-podman scaffolding package) via upgradepkg, using the official Unraid array-event hook mechanism (event/disks_mounted, event/stopping) instead of editing /boot/config/go. rc.podman and the sbin/ helper scripts implement storage creation, config seeding/sync, preflight checks, autostart with per-container Safe-Mode, and package verify/update/rollback. - webui/plugins/podman implements the Dashboard, Containers, Pods, Images, Volumes, Networks, Logs, Terminal, Compose, and Settings panels against the approved mockup (webui/mockups/prototype.html), talking to podman system service exclusively via PodmanClient.php (libpod REST API over the Unix socket), with two documented exceptions: Terminal's one-shot exec model and Compose's use of the podman compose CLI, since libpod has no REST equivalent for either. - docs/ARCHITECTURE.md and docs/ROADMAP.md record the design decisions and honest current status (syntax-checked, unit- and integration-tested against fake sockets/servers; not yet run against a real Unraid/Podman/Slackware system). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
52 lines
1.9 KiB
Markdown
52 lines
1.9 KiB
Markdown
# Contributor Covenant Code of Conduct
|
|
|
|
## Our Pledge
|
|
|
|
We as members, contributors, and leaders pledge to make participation in our
|
|
community a harassment-free experience for everyone, regardless of age, body
|
|
size, visible or invisible disability, ethnicity, sex characteristics, gender
|
|
identity and expression, level of experience, education, socio-economic status,
|
|
nationality, personal appearance, race, religion, or sexual identity and
|
|
orientation.
|
|
|
|
## Our Standards
|
|
|
|
Examples of behavior that contributes to a positive environment:
|
|
|
|
- Demonstrating empathy and kindness toward other people
|
|
- Being respectful of differing opinions, viewpoints, and experiences
|
|
- Giving and gracefully accepting constructive feedback
|
|
- Focusing on what is best for the community
|
|
|
|
Examples of unacceptable behavior:
|
|
|
|
- The use of sexualized language or imagery, and unwelcome sexual attention
|
|
- Trolling, insulting or derogatory comments, and personal or political attacks
|
|
- Public or private harassment
|
|
- Publishing others' private information without explicit permission
|
|
|
|
## Enforcement Responsibilities
|
|
|
|
Project maintainers are responsible for clarifying and enforcing standards of
|
|
acceptable behavior and will take appropriate corrective action in response to
|
|
any behavior deemed inappropriate, threatening, offensive, or harmful.
|
|
|
|
## Scope
|
|
|
|
This Code of Conduct applies within all project spaces (issues, pull requests,
|
|
discussions) and when an individual is officially representing the project in
|
|
public spaces.
|
|
|
|
## Enforcement
|
|
|
|
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
reported to the maintainers via the contact listed in
|
|
[SECURITY.md](SECURITY.md). All complaints will be reviewed and investigated
|
|
promptly and fairly.
|
|
|
|
## Attribution
|
|
|
|
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
|
|
version 2.1, available at
|
|
https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
|