Skip to content

Latest commit

 

History

History
431 lines (321 loc) · 14.3 KB

CONTRIBUTING.md

File metadata and controls

431 lines (321 loc) · 14.3 KB
Raw

Contributing

  • Open an issue and state your feature request. We will get back to you.
  • Read this document, README.md and docs/dev-FAQ.md.
  • Ask before opening a pull request. We might not accept your code and it would be sad to waste the effort.
  • Respect the Code of Conduct (To date, we never had to intervene - Please keep it that way!)

Good First Contributions

  • Reviews are always welcome.
    • Read the code.
    • Read the documentation.
    • Test whether the documentation matches the code.
    • Test Cagebreak in more esoteric setups (many monitors, for instance).
    • Compile the code.
  • Ideas on improving the testing and quality assurance are particularly welcome.
  • You can share your cagebreak scripts and we might include them with Cagebreak provided you agree to release them under MIT and we agree with the use case and coding style.
  • If you are happy with Cagebreak under Arch Linux, you may vote for Cagebreak in the AUR.
  • The points from the Contributing section above still apply.

Philosophy

Cagebreak is currently developed to fit the needs of its creators.

The feature set is intentionally limited - we removed support for a desktop background image for example.

Nonetheless, don't be intimidated by any other part of this file. Do your best and we will collaborate toward a solution.

Development

Compatibility & Development Distribution

Cagebreak supports Arch Linux and uses the libraries versions as they are obtained from extra and core at the time of release.

However, Cagebreak may also work on other distributions given the proper library versions (Some package maintainers have done this and it seems to work.

Packaging status

You should use Arch Linux if you want to modify Cagebreak for yourself.

Review Requirements

Project-repo will review your proposal before your implementation for feasibility and desirability. After your pull request, the code will be reviewed in conjunction with all other changes before the release as per the release procedure.

All reviews performed by project-repo are verified by at least two people internally.

Developer Certificate of Origin (DCO)

On any pull requests please include a

signed-off-by: YOUR IDENTIFIER OR NAME

DCO statement.

By doing this you claim that you are legally allowed to contribute the code and agree to let project-repo publish it under the MIT License.

Development Environment

CAVEAT: This script works exclusively on Arch Linux, which, as outlined above, is the development distribution of Cagebreak.

Cloning the Cagebreak repository and building it is sufficient as a starting point.

All other dependencies can be installed by invoking

meson compile devel-install -C build

if meson is already available or

./scripts/install-development-environment

otherwise.

Scripts

Cagebreak provides a few convenience tools to facilitate development.

Fuzzing

If your fuzzing corpus is located in the directory fuzz_corpus you can just call:

meson compile fuzz -C build

If you want to use a different directory, configure cagebreak with -Dcorpus=OTHERDIRECTORY or call ./scripts/fuzz OTHERDIRECTORY.

Adjusting Epoch

To facilitate the creation of reproducible man pages an arbitrary release time has to be set in meson.build:

meson compile adjust-epoch -C build

Git tag

If you are on the master branch, everything is ready and you want to create a release tag you can call:

meson compile git-tag -C build

If you want to use another signing key than the prespecified one, configure Cagebreak with -Dgpg_id=GPGID.

Output Hashes

Hashes of release versions of all binaries can be output to local-hashes.txt via:

meson compile output-hashes -C build

Create Signatures

Creation of signatures for releases can be achieved through:

meson compile create-sigs -C build

Configure Cagebreak with -Dgpg_id=GPGID for a different gpg signing key.

Set Version Number

Once the version number is set within meson.build, you can use

meson compile set-ver -C build

to set the version number in the man pages and README repology minversion.

Use of the script without meson is discouraged because meson.build is not touched by the script.

Create Release Artefacts

The following command generates the release artefacts which must be created once a release is completely ready to be published (the commit is tagged with the version of the master branch, etc.):

meson compile create-artefacts -C build

Use of the script version is discouraged.

GCC and -fanalyzer

Cagebreak should compile with any reasonably new gcc or clang. Consider a gcc version of at least 10.1 if you want to get the benefit of the -fanalyzer flag. However, this new flag sometimes produces false-postives and we selectively disable warnings for affected code segments as described below.

Meson is configured to set CG_HAS_FANALYZE if -fanalyzer is available. Therefore, to maintain portability, false-positive fanalyzer warnings are to be disabled using the following syntax:

#if CG_HAS_FANALYZE
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "WARNING OPTION"
#endif

and after

#if CG_HAS_FANALYZE
#pragma GCC diagnostic pop
#endif

Test Suite

meson test -C build

invokes all tests. This is required for a release to occur.

There are four test suites:

  • basic: tests actual outward-facing functionality
    • Note optional dependencies for efficient socket interaction
      • nc (openbsd-netcat)
      • jq
  • devel: tests internal properties of the repository
    • Note potentially heavier dependencies such as
      • shellcheck
      • clang-format
  • devel-long: applies more costly testing
    • Note potentially heavier dependencies such as
      • scan-build (static analysis (including security-relevant issues))
  • release: tests release specific considerations
    • Note that this is only expected to pass just before a release. This checks mostly administrative things to check that a release is ready.
    • Note that non-auto tests are files in release-non-auto-checks and have to contain the release version and current date in YYYY-mm-dd format on seperate lines. This is our imperfect attempt to guarantee some hard-to-automate checks are carried out before a release is undertaken.

Every commit should pass at least the basic and devel suites.

It is expected that cagebreak passes at least the basic, devel and devel-long suites when commits are pushed:

meson test -C build --suite basic --suite devel

The basic suite can be used to test a binary. This is useful for PKGBUILDs and their equivalents in other systems.

meson test -C build --suite basic

Fuzzing

Along with the project source code, a fuzzing framework based on libfuzzer is supplied. This allows for the testing of the parsing code responsible for reading the cagebreak configuration file. When libfuzzer is available (please use the clang compiler to enable it), building the fuzz-testing software can be enabled by passing -Dfuzz=true to meson. This generates a build/fuzz/fuzz-parse binary according to the libfuzzer specifications. Further documentation on how to run this binary can be found here.

Here is an example workflow:

rm -rf build
CC=clang meson setup build -Dfuzz=true -Db_sanitize=address,undefined -Db_lundef=false
ninja -C build/
mkdir build/fuzz_corpus
cp examples/config build/fuzz_corpus/
WLR_BACKENDS=headless ./build/fuzz-parse -jobs=12 -max_len=50000 -close_fd_mask=3 build/fuzz_corpus/

You may want to tweak -jobs or add other options depending on your own setup. We have found code path discovery to increase rapidly when the fuzzer is supplied with an initial config file. We are working on improving our fuzzing coverage to find bugs in other areas of the code.

Reproducible Builds

Cagebreak offers reproducible builds given the exact library versions specified in meson.build. Should a version mismatch occur, a warning will be emitted. We have decided on this compromise to allow flexibility and security. In general we will adapt the versions to the packages available under Arch Linux at the time of release.

There are reproducibility issues up to and including release 1.2.0. See Issue 5 in Bugs.md.

Reproducible Build Instructions

All hashes and signatures are provided for the following build instructions.

meson setup build -Dxwayland=true -Dman-pages=true --buildtype=release
ninja -C build

Hashes for Builds

For every release after 1.0.5, hashes will be provided.

For every release after 1.7.0, hashes will be provided for man pages too.

See Hashes.md

GPG Signatures

For every release after 1.0.5, a GPG signature will be provided in signatures.

The current signature is called cagebreak.sig, whereas all older signatures will be named after their release version.

Due to errors in the release process, the releases 1.7.1 and 1.7.2 did not include the release signatures in the appropriate folder of the git repository. However, signatures were provided as release-artefacts at the time of release. The signatures were introduced into the repository with 1.7.3. The integrity of cagebreak is still the same because the signatures were provided as release-artefacts (which were themselves signed) and the hashes in Hashes.md are part of a signed release tag.

Signing Keys

All releases are signed by at least one of the following collection of keys.

Should we at any point retire a key, we will only replace it with keys signed by at least one of the above collection.

We registered project-repo.co and added mail addresses after release 1.3.0.

We now have a mail address and its key is signed by signing keys. See SECURITY.md for details.

The full public keys can be found in keys/ along with any revocation certificates.

Versioning & Branching Strategy

Cagebreak uses semantic versioning.

There are three permanent branches in cagebreak:

  • master (for releases)
  • development (for polishing code between releases)
  • hotfix (for small emergent releases, usually up-to-date with master)

Releases are merged to master as per the release procedure, with reasonable exceptions as the situation requires.

The release commit is tagged with the release version.

In the past, our git history did not perfectly reflect this scheme.

Release Procedure

The release procedure outlines the process for a release to occur.

  • git checkout development
  • git pull origin development
  • git push origin development
  • Arch Build System is up to date
  • meson test -C build/ just to get an overview
  • Update internal wiki
  • Adjust version number in meson.build
  • meson compile set-ver -C build
  • Add new files to meson.build or hardcoded testing variable
  • Commit changes
  • git push origin development
  • Complete relevant documentation
    • New features
      • tests added and old test scripts adjusted
      • man pages
        • cagebreak
        • cagebreak-config
        • cagebreak-socket
        • example config
      • FAQ.md
      • Changelog.md for major and minor releases but not patches
    • Check changes for SECURITY.md relevance (changes to socket scope for example)
      • Synchronize any socket changes to cagebreak-socket man page
    • Document fixed bugs in Bugs.md
      • Include issue discussion from github, where applicable
  • meson compile adjust-epoch -C build
  • Commit changes
  • git push origin development
  • Testing
    • Manual testing
    • meson compile fuzz -C build for at least one hour
  • Adjust Hashes.md - Use meson compile output-hashes -C build to add Hashes or aid in repro check
  • Commit changes
  • git push origin development
  • Complete release-non-auto-checks
  • meson compile create-sigs -C build
  • Commit and push signatures, hashes and non-auto-check files
  • meson test -C build passes everything except some release tests
  • git add relevant files
  • git commit
  • git push origin development
  • git checkout master
  • git pull --tags origin master
  • git merge --squash development
  • git commit and insert message
  • meson compile git-tag -C build
  • meson compile create-artefacts -C build
  • meson test -C build THIS MUST PASS WITHOUT ANY FAILURES WHATSOEVER
  • git push --tags origin master
  • git checkout development (merge to development depends on whether release was a hotfix)
  • git merge master
  • git push --tags origin development
  • git checkout hotfix (hotfix is to be kept current with master after releases)
  • git merge master
  • git push --tags origin hotfix
  • Upload archives and signatures as release assets
  • Delete feature branches if appropriate
  • Manage package release