In order for the project to be scalable wrt the increase in scope,
number of contributors and associated organizations, we feel the need to
at least establish some rules that will make things easier. There are
1. Decrease maintenance costs by paying attention to the contribution
2. Enable the community to self-organize and get PRs merged at a faster
pace without increasing associated risks.
And there are two PRs where each addresses one of those points:
1. https://github.com/ComplianceAsCode/content/pull/8314 introduces new
code-related and review-related guidelines, and
2. https://github.com/ComplianceAsCode/content/pull/8359 introduces new
It reflects discussions among Red Hat developers, but as this is a
community project, please check it out and provide feedback:
* on Gitter if you feel that you need to ask a short question to
* directly in PRs as a comment or suggestion, or
* here if you don't have a GH account or if you want to approach the
topic on a higher level than PRs do.
In any case, please tell us something, so those guidelines don't come
into effect by being merged simply because they have been laying around
for a couple of weeks.
Release of Content version 0.1.61 is scheduled for March 25th, and as part
of the release process a stabilization branch was created.
Issues and PRs that were not solved were moved to the 0.1.62 milestone.
Any bug fix that you'd like to have included in the 0.1.61 release should
be proposed to the *stabilization* branch, the fixes then are later merged
The next version, 0.1.62, is scheduled to be released on May 27th, with the
stabilization phase starting on May 16th 2022.
Senior Software Engineer
Red Hat EMEA <https://www.redhat.com>