[libcamera-devel,v1,0/5] Add a code of conduct to libcamera
mbox series

Message ID 20231110142311.3818-1-laurent.pinchart@ideasonboard.com
Headers show
Series
  • Add a code of conduct to libcamera
Related show

Message

Laurent Pinchart Nov. 10, 2023, 2:23 p.m. UTC 
Hello everybody,

libcamera doesn't have a formal code of conduct. This doesn't mean that
the project doesn't expect its maintainers, contributors and community
members in general to behave decently towards each other, only that we
have never taken the time to formalize and state our expectations
explicitly.

Adoption of different codes of conduct in free software communities has
increased over the past few years. I believe it is time for libcamera to
also formalize what constitutes acceptable and non-acceptable
behaviours, which I think just explicitly confirms the standards that
everybody was already expecting.

As indicated in the first patch in the series, codes of conduct, like
software licenses, can be written in a myriad of ways. And like software
licenses, using a widely adopted code of conduct instead of writing our
own help bringing clarity. I propose in this series to use the
Contributor Covenant v1.4([1]), stewarded by the Organization for
Ethical Source. Not only is it widely adopted, it is also quite notably
used by freedesktop.org, which libcamera will likely work with in the
future to implement a CI infrastructure.

The first patch in the series imports the Contributor Covenant Code of
Conduct verbatim in its original Markdown form to ease change tracking.
The rest of the patches then turn it into reST, add license and contact
information, and integrate it in the documentation build.

If anyone has any concern with libcamera adopting this particular code
of conduct, please feel free to contact me privately for a constructive
discussion if you don't feel safe expressing your concerns in public.
My limited knowledge of the topic doesn't allow me to tell if wide
adoption of codes of conduct have by itself made free software
communities significantly better places (any pointer to serious studies
on this topic would be interesting), but in any case I think it is fair
to say that the process has not been detrimental, and, in particular,
that the threat of weaponizing codes of conducts that have been raised
in the past has never materialized.

[1] https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

Laurent Pinchart (5):
  Documentation: Add code of conduct
  Documentation: code-of-conduct: Convert to reStructuredText
  Documentation: code-of-conduct: Add license information
  Documentation: code-of-conduct: Add contact information
  Documentation: contributing: Integrate the code of conduct

 Documentation/code-of-conduct.rst | 94 +++++++++++++++++++++++++++++++
 Documentation/contributing.rst    |  5 ++
 Documentation/meson.build         |  1 +
 3 files changed, 100 insertions(+)
 create mode 100644 Documentation/code-of-conduct.rst


base-commit: 73c7eeb3e4606853b44719a3b355e62c888df652