[libcamera-devel,v1,1/5] Documentation: Add code of conduct

19201 diff mbox series

Communities have standards regarding behaviours they consider acceptable
or not acceptable, and expect community members to follow those
standards. libcamera is no different, even if it has never clearly
expressed those standards in a formal code of conduct document.

Like software licenses, codes of conduct can be written in a myriad of
ways. And like software licenses, using a widely adopted code of conduct
instead of writing our own can help bringing clarity. One such standard
code of conduct is the Contributor Covenant, stewarded by the
Organization for Ethical Source.

The Contributor Covenant has been adopted by the freedesktop.org
organization, which hosts a large number of projects historically
related to graphics, and more recently to multimedia in general.
freedesktop.org offers services such as git hosting with CI, which
libcamera could benefit from. There is therefore a clear incentive to
choose the same code of conduct as freedesktop.org, and no known
drawback.

As a first step towards this, and to keep the libcamera code of conduct
history clear in git, copy the original Contributor Covenant v1.4 from
https://github.com/EthicalSource/contributor_covenant/. "v1.4" is
ambiguous as the document initially published as v1.4 has received small
(but sometimes significant) modifications over time. The version
imported here is the most recent, and comes from commit 3fd3bf6d12de
("Merge pull request #1321 from story645/patch-2") which is the tip of
the release branch ([1]).

[1] https://github.com/EthicalSource/contributor_covenant/blob/3fd3bf6d12de15edfff1b30acd4de61502020a62/content/version/1/4/code-of-conduct.md

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
---
 Documentation/code_of_conduct.md | 78 ++++++++++++++++++++++++++++++++
 1 file changed, 78 insertions(+)
 create mode 100644 Documentation/code_of_conduct.md

Quoting Laurent Pinchart via libcamera-devel (2023-11-10 14:23:07)
> Communities have standards regarding behaviours they consider acceptable
> or not acceptable, and expect community members to follow those
> standards. libcamera is no different, even if it has never clearly
> expressed those standards in a formal code of conduct document.
> 
> Like software licenses, codes of conduct can be written in a myriad of
> ways. And like software licenses, using a widely adopted code of conduct
> instead of writing our own can help bringing clarity. One such standard
> code of conduct is the Contributor Covenant, stewarded by the
> Organization for Ethical Source.
> 
> The Contributor Covenant has been adopted by the freedesktop.org
> organization, which hosts a large number of projects historically
> related to graphics, and more recently to multimedia in general.
> freedesktop.org offers services such as git hosting with CI, which
> libcamera could benefit from. There is therefore a clear incentive to
> choose the same code of conduct as freedesktop.org, and no known
> drawback.
> 
> As a first step towards this, and to keep the libcamera code of conduct
> history clear in git, copy the original Contributor Covenant v1.4 from
> https://github.com/EthicalSource/contributor_covenant/. "v1.4" is
> ambiguous as the document initially published as v1.4 has received small
> (but sometimes significant) modifications over time. The version
> imported here is the most recent, and comes from commit 3fd3bf6d12de
> ("Merge pull request #1321 from story645/patch-2") which is the tip of
> the release branch ([1]).
> 
> [1] https://github.com/EthicalSource/contributor_covenant/blob/3fd3bf6d12de15edfff1b30acd4de61502020a62/content/version/1/4/code-of-conduct.md

With a direct import, I won't review this specifically.

Instead this is more reasonable I think:

Acked-by: Kieran Bingham <kieran.bingham@ideasonboard.com>

> 
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>  Documentation/code_of_conduct.md | 78 ++++++++++++++++++++++++++++++++
>  1 file changed, 78 insertions(+)
>  create mode 100644 Documentation/code_of_conduct.md
> 
> diff --git a/Documentation/code_of_conduct.md b/Documentation/code_of_conduct.md
> new file mode 100644
> index 000000000000..fcf453902224
> --- /dev/null
> +++ b/Documentation/code_of_conduct.md
> @@ -0,0 +1,78 @@
> +
> +# Contributor Covenant Code of Conduct
> +
> +## Our Pledge
> +
> +In the interest of fostering an open and welcoming environment, we as
> +contributors and maintainers pledge to make participation in our project and
> +our community a harassment-free experience for everyone, regardless of age, body
> +size, disability, ethnicity, sex characteristics, gender identity and expression,
> +level of experience, education, socio-economic status, nationality, personal
> +appearance, race, religion, or sexual identity and orientation.
> +
> +## Our Standards
> +
> +Examples of behavior that contributes to creating a positive environment
> +include:
> +
> +* Using welcoming and inclusive language
> +* Being respectful of differing viewpoints and experiences
> +* Gracefully accepting constructive criticism
> +* Focusing on what is best for the community
> +* Showing empathy towards other community members
> +
> +Examples of unacceptable behavior by participants include:
> +
> +* The use of sexualized language or imagery and unwelcome sexual attention or
> +  advances
> +* Trolling, insulting/derogatory comments, and personal or political attacks
> +* Public or private harassment
> +* Publishing others' private information, such as a physical or electronic
> +  address, without explicit permission
> +* Other conduct which could reasonably be considered inappropriate in a
> +  professional setting
> +
> +## Our Responsibilities
> +
> +Project maintainers are responsible for clarifying the standards of acceptable
> +behavior and are expected to take appropriate and fair corrective action in
> +response to any instances of unacceptable behavior.
> +
> +Project maintainers have the right and responsibility to remove, edit, or
> +reject comments, commits, code, wiki edits, issues, and other contributions
> +that are not aligned to this Code of Conduct, or to ban temporarily or
> +permanently any contributor for other behaviors that they deem inappropriate,
> +threatening, offensive, or harmful.
> +
> +## Scope
> +
> +This Code of Conduct applies within all project spaces, and it also applies when
> +an individual is representing the project or its community in public spaces.
> +Examples of representing a project or community include using an official
> +project e-mail address, posting via an official social media account, or acting
> +as an appointed representative at an online or offline event. Representation of
> +a project may be further defined and clarified by project maintainers.
> +
> +## Enforcement
> +
> +Instances of abusive, harassing, or otherwise unacceptable behavior may be
> +reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
> +complaints will be reviewed and investigated and will result in a response that
> +is deemed necessary and appropriate to the circumstances. The project team is
> +obligated to maintain confidentiality with regard to the reporter of an incident.
> +Further details of specific enforcement policies may be posted separately.
> +
> +Project maintainers who do not follow or enforce the Code of Conduct in good
> +faith may face temporary or permanent repercussions as determined by other
> +members of the project's leadership.
> +
> +## Attribution
> +
> +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
> +available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
> +
> +[homepage]: https://www.contributor-covenant.org
> +
> +For answers to common questions about this code of conduct, see
> +https://www.contributor-covenant.org/faq
> +
> -- 
> Regards,
> 
> Laurent Pinchart
>

Quoting Laurent Pinchart via libcamera-devel (2023-11-10 14:23:07)
> Communities have standards regarding behaviours they consider acceptable
> or not acceptable, and expect community members to follow those
> standards. libcamera is no different, even if it has never clearly
> expressed those standards in a formal code of conduct document.
> 
> Like software licenses, codes of conduct can be written in a myriad of
> ways. And like software licenses, using a widely adopted code of conduct
> instead of writing our own can help bringing clarity. One such standard
> code of conduct is the Contributor Covenant, stewarded by the
> Organization for Ethical Source.
> 
> The Contributor Covenant has been adopted by the freedesktop.org
> organization, which hosts a large number of projects historically
> related to graphics, and more recently to multimedia in general.
> freedesktop.org offers services such as git hosting with CI, which
> libcamera could benefit from. There is therefore a clear incentive to
> choose the same code of conduct as freedesktop.org, and no known
> drawback.
> 
> As a first step towards this, and to keep the libcamera code of conduct
> history clear in git, copy the original Contributor Covenant v1.4 from
> https://github.com/EthicalSource/contributor_covenant/. "v1.4" is
> ambiguous as the document initially published as v1.4 has received small
> (but sometimes significant) modifications over time. The version
> imported here is the most recent, and comes from commit 3fd3bf6d12de
> ("Merge pull request #1321 from story645/patch-2") which is the tip of
> the release branch ([1]).
> 
> [1] https://github.com/EthicalSource/contributor_covenant/blob/3fd3bf6d12de15edfff1b30acd4de61502020a62/content/version/1/4/code-of-conduct.md

I'm a little confused ...

https://github.com/EthicalSource/contributor_covenant/releases/tag/2.1
looks to be the most recent release.

v1.4 was released on January 30th 2016, while 2.1 was released August
4th 2021.

I can see that the different 'versions' are maintained, which I expect
is to support translations and fixes to those 'versions' ... but I can
see how this makes things a little difficult to define indeed.

Multiple versions (branches) of a versioned document ... all maintained
in a single repository....


Ok - so now I can see that freedesktop explicitly references that they
have used version 1.4.

"""
- This Code of Conduct is adapted from the Contributor Covenant,
version 1.4, available at http://contributor-covenant.org/version/1/4
"""

So in some ways, it could be said we are going to use version 2.1 of the
Contributor-Conenant-1.4.

(If we were to take the version at the v2.1 tag, which may be more clear
than an arbitrary latest snapshot from the latest development branch ...)


The only differences between release 2.1 and the point you have
referenced in regards to the Contributor-Conenant-1.4 is the following
commits:

5f8441873de9 Fixed Wrong Interpretation
35e7cd0ea967 Fixed Wrong Interpretation
aae9e3c57dab Improved the translation of bengali(bn) language
cde1689b75f7 Rectify the 𑘆 vowel when it is joined to other consonants
9e04a0bf24d9 Transliterate Marathi to its own original Modi Script

Which are all about correcting mis-translations of the document.

I think therefore it would be acceptable to say clearly we are using
Contributor-Conenant-1.4 version 2.1

(And no change of import here is required, as the document is
identical).


> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>  Documentation/code_of_conduct.md | 78 ++++++++++++++++++++++++++++++++
>  1 file changed, 78 insertions(+)
>  create mode 100644 Documentation/code_of_conduct.md
> 
> diff --git a/Documentation/code_of_conduct.md b/Documentation/code_of_conduct.md
> new file mode 100644
> index 000000000000..fcf453902224
> --- /dev/null
> +++ b/Documentation/code_of_conduct.md
> @@ -0,0 +1,78 @@
> +
> +# Contributor Covenant Code of Conduct
> +
> +## Our Pledge
> +
> +In the interest of fostering an open and welcoming environment, we as
> +contributors and maintainers pledge to make participation in our project and
> +our community a harassment-free experience for everyone, regardless of age, body
> +size, disability, ethnicity, sex characteristics, gender identity and expression,
> +level of experience, education, socio-economic status, nationality, personal
> +appearance, race, religion, or sexual identity and orientation.
> +
> +## Our Standards
> +
> +Examples of behavior that contributes to creating a positive environment
> +include:
> +
> +* Using welcoming and inclusive language
> +* Being respectful of differing viewpoints and experiences
> +* Gracefully accepting constructive criticism
> +* Focusing on what is best for the community
> +* Showing empathy towards other community members
> +
> +Examples of unacceptable behavior by participants include:
> +
> +* The use of sexualized language or imagery and unwelcome sexual attention or
> +  advances
> +* Trolling, insulting/derogatory comments, and personal or political attacks
> +* Public or private harassment
> +* Publishing others' private information, such as a physical or electronic
> +  address, without explicit permission
> +* Other conduct which could reasonably be considered inappropriate in a
> +  professional setting
> +
> +## Our Responsibilities
> +
> +Project maintainers are responsible for clarifying the standards of acceptable
> +behavior and are expected to take appropriate and fair corrective action in
> +response to any instances of unacceptable behavior.
> +
> +Project maintainers have the right and responsibility to remove, edit, or
> +reject comments, commits, code, wiki edits, issues, and other contributions
> +that are not aligned to this Code of Conduct, or to ban temporarily or
> +permanently any contributor for other behaviors that they deem inappropriate,
> +threatening, offensive, or harmful.
> +
> +## Scope
> +
> +This Code of Conduct applies within all project spaces, and it also applies when
> +an individual is representing the project or its community in public spaces.
> +Examples of representing a project or community include using an official
> +project e-mail address, posting via an official social media account, or acting
> +as an appointed representative at an online or offline event. Representation of
> +a project may be further defined and clarified by project maintainers.
> +
> +## Enforcement
> +
> +Instances of abusive, harassing, or otherwise unacceptable behavior may be
> +reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
> +complaints will be reviewed and investigated and will result in a response that
> +is deemed necessary and appropriate to the circumstances. The project team is
> +obligated to maintain confidentiality with regard to the reporter of an incident.
> +Further details of specific enforcement policies may be posted separately.
> +
> +Project maintainers who do not follow or enforce the Code of Conduct in good
> +faith may face temporary or permanent repercussions as determined by other
> +members of the project's leadership.
> +
> +## Attribution
> +
> +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
> +available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
> +
> +[homepage]: https://www.contributor-covenant.org
> +
> +For answers to common questions about this code of conduct, see
> +https://www.contributor-covenant.org/faq
> +
> -- 
> Regards,
> 
> Laurent Pinchart
>

Hi Kieran,

On Fri, Nov 24, 2023 at 04:28:33PM +0000, Kieran Bingham wrote:
> Quoting Laurent Pinchart via libcamera-devel (2023-11-10 14:23:07)
> > Communities have standards regarding behaviours they consider acceptable
> > or not acceptable, and expect community members to follow those
> > standards. libcamera is no different, even if it has never clearly
> > expressed those standards in a formal code of conduct document.
> > 
> > Like software licenses, codes of conduct can be written in a myriad of
> > ways. And like software licenses, using a widely adopted code of conduct
> > instead of writing our own can help bringing clarity. One such standard
> > code of conduct is the Contributor Covenant, stewarded by the
> > Organization for Ethical Source.
> > 
> > The Contributor Covenant has been adopted by the freedesktop.org
> > organization, which hosts a large number of projects historically
> > related to graphics, and more recently to multimedia in general.
> > freedesktop.org offers services such as git hosting with CI, which
> > libcamera could benefit from. There is therefore a clear incentive to
> > choose the same code of conduct as freedesktop.org, and no known
> > drawback.
> > 
> > As a first step towards this, and to keep the libcamera code of conduct
> > history clear in git, copy the original Contributor Covenant v1.4 from
> > https://github.com/EthicalSource/contributor_covenant/. "v1.4" is
> > ambiguous as the document initially published as v1.4 has received small
> > (but sometimes significant) modifications over time. The version
> > imported here is the most recent, and comes from commit 3fd3bf6d12de
> > ("Merge pull request #1321 from story645/patch-2") which is the tip of
> > the release branch ([1]).
> > 
> > [1] https://github.com/EthicalSource/contributor_covenant/blob/3fd3bf6d12de15edfff1b30acd4de61502020a62/content/version/1/4/code-of-conduct.md
> 
> I'm a little confused ...

I'm not surprised at all.

> https://github.com/EthicalSource/contributor_covenant/releases/tag/2.1
> looks to be the most recent release.
> 
> v1.4 was released on January 30th 2016, while 2.1 was released August
> 4th 2021.
> 
> I can see that the different 'versions' are maintained, which I expect
> is to support translations and fixes to those 'versions' ... but I can
> see how this makes things a little difficult to define indeed.
> 
> Multiple versions (branches) of a versioned document ... all maintained
> in a single repository....

I shed a few tears when I realized that. Even worse, there's a 1.4 tag
and a v1_4 branch, and of course the v1.4 version of the document
differs between the two.

> Ok - so now I can see that freedesktop explicitly references that they
> have used version 1.4.
> 
> """
> - This Code of Conduct is adapted from the Contributor Covenant,
> version 1.4, available at http://contributor-covenant.org/version/1/4
> """
> 
> So in some ways, it could be said we are going to use version 2.1 of the
> Contributor-Conenant-1.4.
> 
> (If we were to take the version at the v2.1 tag, which may be more clear
> than an arbitrary latest snapshot from the latest development branch ...)

The two are identical, yes. After seeing the mess that the git tree is,
I decided to point to an explicit commit, ss that clears all confusion.

> The only differences between release 2.1 and the point you have
> referenced in regards to the Contributor-Conenant-1.4 is the following
> commits:
> 
> 5f8441873de9 Fixed Wrong Interpretation
> 35e7cd0ea967 Fixed Wrong Interpretation
> aae9e3c57dab Improved the translation of bengali(bn) language
> cde1689b75f7 Rectify the 𑘆 vowel when it is joined to other consonants
> 9e04a0bf24d9 Transliterate Marathi to its own original Modi Script
> 
> Which are all about correcting mis-translations of the document.

Yes, there are no differences in the file I'm importing.

> I think therefore it would be acceptable to say clearly we are using
> Contributor-Conenant-1.4 version 2.1

I'm not sure it makes more (or less) sense. v2.1 of v1.4 is a concept I
can't wrap my brain around in any sensible way :-) Let's try to put all
this behind us and forget about it.

> (And no change of import here is required, as the document is
> identical).
> 
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> >  Documentation/code_of_conduct.md | 78 ++++++++++++++++++++++++++++++++
> >  1 file changed, 78 insertions(+)
> >  create mode 100644 Documentation/code_of_conduct.md
> > 
> > diff --git a/Documentation/code_of_conduct.md b/Documentation/code_of_conduct.md
> > new file mode 100644
> > index 000000000000..fcf453902224
> > --- /dev/null
> > +++ b/Documentation/code_of_conduct.md
> > @@ -0,0 +1,78 @@
> > +
> > +# Contributor Covenant Code of Conduct
> > +
> > +## Our Pledge
> > +
> > +In the interest of fostering an open and welcoming environment, we as
> > +contributors and maintainers pledge to make participation in our project and
> > +our community a harassment-free experience for everyone, regardless of age, body
> > +size, disability, ethnicity, sex characteristics, gender identity and expression,
> > +level of experience, education, socio-economic status, nationality, personal
> > +appearance, race, religion, or sexual identity and orientation.
> > +
> > +## Our Standards
> > +
> > +Examples of behavior that contributes to creating a positive environment
> > +include:
> > +
> > +* Using welcoming and inclusive language
> > +* Being respectful of differing viewpoints and experiences
> > +* Gracefully accepting constructive criticism
> > +* Focusing on what is best for the community
> > +* Showing empathy towards other community members
> > +
> > +Examples of unacceptable behavior by participants include:
> > +
> > +* The use of sexualized language or imagery and unwelcome sexual attention or
> > +  advances
> > +* Trolling, insulting/derogatory comments, and personal or political attacks
> > +* Public or private harassment
> > +* Publishing others' private information, such as a physical or electronic
> > +  address, without explicit permission
> > +* Other conduct which could reasonably be considered inappropriate in a
> > +  professional setting
> > +
> > +## Our Responsibilities
> > +
> > +Project maintainers are responsible for clarifying the standards of acceptable
> > +behavior and are expected to take appropriate and fair corrective action in
> > +response to any instances of unacceptable behavior.
> > +
> > +Project maintainers have the right and responsibility to remove, edit, or
> > +reject comments, commits, code, wiki edits, issues, and other contributions
> > +that are not aligned to this Code of Conduct, or to ban temporarily or
> > +permanently any contributor for other behaviors that they deem inappropriate,
> > +threatening, offensive, or harmful.
> > +
> > +## Scope
> > +
> > +This Code of Conduct applies within all project spaces, and it also applies when
> > +an individual is representing the project or its community in public spaces.
> > +Examples of representing a project or community include using an official
> > +project e-mail address, posting via an official social media account, or acting
> > +as an appointed representative at an online or offline event. Representation of
> > +a project may be further defined and clarified by project maintainers.
> > +
> > +## Enforcement
> > +
> > +Instances of abusive, harassing, or otherwise unacceptable behavior may be
> > +reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
> > +complaints will be reviewed and investigated and will result in a response that
> > +is deemed necessary and appropriate to the circumstances. The project team is
> > +obligated to maintain confidentiality with regard to the reporter of an incident.
> > +Further details of specific enforcement policies may be posted separately.
> > +
> > +Project maintainers who do not follow or enforce the Code of Conduct in good
> > +faith may face temporary or permanent repercussions as determined by other
> > +members of the project's leadership.
> > +
> > +## Attribution
> > +
> > +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
> > +available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
> > +
> > +[homepage]: https://www.contributor-covenant.org
> > +
> > +For answers to common questions about this code of conduct, see
> > +https://www.contributor-covenant.org/faq
> > +