Show 19 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>> In other words, the commit message can be augmented by this:
>>
>> Acked-by: Johannes Schindelin <johannes.schindelin@gmx.de>
>> Acked-by: Derrick Stolee <stolee@gmail.com>
>> Acked-by: Garima Singh <garimasigit@gmail.com>
>> Acked-by: Jonathan Tan <jonathantanmy@google.com>
>> Acked-by: Thomas Gummerer <t.gummerer@gmail.com>
>> Acked-by: brian m. carlson <sandals@crustytoothpaste.net>
>> Acked-by: Elijah Newren <newren@gmail.com>
>>
>> Junio, would you mind picking it up, please?
>
> I trust you enough that I won't go back to the cited messages to
> double check that these acks are real, but I'd still wait for a few
> days for people who expressed their Acks but your scan missed, or
> those who wanted to give their Acks but forgot to do so, to raise
> their hands on this thread.
I forgot to add
Acked-by: Phillip Wood <phillip.wood@dunelm.org.uk>
to my original reply in this thread, could you add it please
Thanks
Phillip
Show 104 quoted lines
> Thanks for starting the concluding move on this topic.
>
> For reference, here is the CoC the patch wants to add (there is no
> such topic yet locally, nor a single patch that can be made into
> such a topic, so there isn't exactly something people can Ack on
> yet. So here is a "preview" of what we would see once such a series
> lands).
>
> CODE_OF_CONDUCT.md | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> # Git Code of Conduct
>
> This code of conduct outlines our expectations for participants within
> the Git community, as well as steps for reporting unacceptable behavior.
> We are committed to providing a welcoming and inspiring community for
> all and expect our code of conduct to be honored. Anyone who violates
> this code of conduct may be banned from the community.
>
> ## 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 git@sfconservancy.org. 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.
>
> The project leadership team can be contacted by email as a whole at
> git@sfconservancy.org, or individually:
>
> - Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> - Christian Couder <christian.couder@gmail.com>
> - Jeff King <peff@peff.net>
> - Junio C Hamano <gitster@pobox.com>
>
> ## 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
>