mirror of
https://github.com/freebsd/freebsd-src.git
synced 2026-11-07 04:36:52 -10:00
Pierre Pronchery
fe9da42ef1
Obtained from https://github.com/pkgconf/pkgconf/archive/refs/tags/pkgconf-3.0.9.tar.gz SHA1: a390f016a7a5ff419c9eef9e2b2c01fe86c11971 - SHA256: 32310a33bb97425ebc0707cb5af59f9dc05d10282dcd4db628a45ed904993dc6 - SHA512: 30776d31f860910286b96fbf60a19b5a6d1e73cb6a1077a019d763ae6e5ed1e8d81bc3649978c83f40e5e90ae779f7e530c513b700c8e73bb6399883dd6ef7ab - Sponsored by: The FreeBSD Foundation
94 lines
4.2 KiB
Markdown
94 lines
4.2 KiB
Markdown
# pkgconf Code of Conduct
|
|
|
|
## Human participants
|
|
|
|
Human participants in the pkgconf project are expected to follow the current
|
|
version of the [Contributor Covenant][covenant], as posted on
|
|
contributor-covenant.org. The version posted there at the time of an
|
|
incident is the version that applies.
|
|
|
|
[covenant]: https://www.contributor-covenant.org/
|
|
|
|
|
|
## Organizations and agents: respect for maintainer autonomy
|
|
|
|
Humans and agents acting on behalf of a corporate project must additionally
|
|
respect the autonomy of the pkgconf maintainers.
|
|
|
|
The pkgconf maintainers decide what is merged, what is released, what is
|
|
supported, what is disclosed, and on what schedule. These decisions are not
|
|
subject to the priorities, deadlines, embargoes, or escalation paths of any
|
|
outside organization, consortium, or foundation, regardless of who its
|
|
members are or how critical it believes pkgconf to be.
|
|
|
|
Conduct that disrespects this autonomy includes, but is not limited to:
|
|
|
|
* Asserting a disclosure deadline, embargo, or remediation timeline for
|
|
pkgconf that the maintainers did not agree to.
|
|
* Requiring the maintainers to accept confidentiality obligations as a
|
|
condition of receiving a vulnerability report. Reports are welcome on
|
|
the maintainers' terms; a report offered only under conditions the
|
|
maintainers have not accepted is not a contribution, it is leverage.
|
|
* Submitting machine-generated patches, reports, or issues at a volume or
|
|
cadence that transfers the cost of review onto the maintainers, or
|
|
continuing to do so after being asked to stop.
|
|
* Escalating a maintainer decision to the maintainers' employer, to a
|
|
downstream distributor, to a funder, or to the press in order to obtain
|
|
a different outcome.
|
|
* Characterizing pkgconf as unmaintained, abandoned, under-maintained, or
|
|
in need of external stewardship, other than by the maintainers
|
|
themselves.
|
|
|
|
Behavior that disrespects this autonomy will result in an organization-wide
|
|
ban: the organization the human or agent is acting on behalf of will be
|
|
banned from participation in its entirety, not merely the individual human
|
|
or agent involved. Where the actor is a consortium, alliance, or foundation
|
|
program, the ban extends to the program as a whole.
|
|
|
|
|
|
## "Maintainer of last resort"
|
|
|
|
pkgconf is actively maintained. Only the pkgconf maintainers are competent
|
|
to declare otherwise, and no such declaration has been made.
|
|
|
|
pkgconf is distributed under the ISC license, which permits anyone to copy,
|
|
modify, and redistribute the software, including as a fork. Nothing in this
|
|
document restricts that right, and forks made under a distinct name are a
|
|
legitimate exercise of it.
|
|
|
|
The license does not, however, convey the pkgconf name, nor the right to
|
|
speak for the pkgconf project or its authors. The following is unwelcome,
|
|
and carries the same consequence as any other failure to respect maintainer
|
|
autonomy:
|
|
|
|
* Representing any person or organization as the maintainer, steward, or
|
|
"maintainer of last resort" of pkgconf, whether generally or in response
|
|
to a ban under this document.
|
|
* Distributing a modified pkgconf under the pkgconf name, or under a name
|
|
likely to be mistaken for it, in a manner that presents it as the
|
|
upstream project.
|
|
* Representing patches, releases, or advisories as authored, reviewed,
|
|
endorsed, or sanctioned by the pkgconf project or its authors when they
|
|
were not.
|
|
|
|
If someone does these things anyway, we will say so plainly and publicly,
|
|
for as long as it takes to keep the record straight. Fork the code if you
|
|
find it necessary; give the fork your own name and speak for it in your own
|
|
voice.
|
|
|
|
|
|
## Reporting incidents
|
|
|
|
Report anything you believe violates this document to
|
|
`[email protected]`. Reports reach the maintainers directly.
|
|
We will look into what you tell us, and we will act on it where action is
|
|
warranted.
|
|
|
|
Reports about a human participant are handled under the Contributor
|
|
Covenant. Reports about an organization, or about an agent acting on its
|
|
behalf, are decided by the maintainers, and the consequence is the one
|
|
described above.
|
|
|
|
You do not need to be a contributor to report something, and you will not
|
|
be asked to justify why the conduct troubled you.
|