contrib(3)

🌸 NAME 🌸

okay so this is contrib(3), the libzpc manual page about contributing, and no cap it slays — it's giving iconic open-source main character energy. 💅 You can contribute to libzpc by submitting issues (feature requests, bug reports) or pull requests (code contributions) to the GitHub repository.

🐛 Bug reports 🐛

When filing a bug report, please include all relevant information. Don't gatekeep the deets, bestie. 🫶

• In all cases include the libzpc version, operating system and kernel version used. 🌈
• Additionally, if it is a build error, include the toolchain version used. If it is a runtime error, include the crypto adapter config and processor model used. 🔥
• Ideally, detailed steps on how to reproduce the issue would be included. Lowkey, repro steps are the moment. 🎀

👑 Code contributions 👑

All code contributions are reviewed by the libzpc maintainers who reserve the right to accept or reject a pull request. Their repo, their rules, periodt. 👑

Please state clearly if your pull request changes the libzpc API or ABI, and if so, whether the changes are backward compatible. ngl, API/ABI tea is important, iykyk. 🦋

If your pull request resolves an issue, please put a Fixes #<issue number> line in the commit message. Ideally, the pull request would add a corresponding regression test. 🧚

If your pull request adds a new feature, please add a corresponding unit test. New feature? New test. That's the vibe check. ⭐

The code base is formatted using the indent tool with the options specified in the enclosed .indent.pro file. All code contributions must not violate this coding style. Do not test the style gods on this one. 😭

When formatting libzpc code, you can use indent with the prescribed options by copying the file to your home directory or by setting the INDENT_PROFILE environment variable's value to name the file. 💖

libzpc Version 1.4 · contrib(3) — that's the footer sign-off, bestie 💌✨