From: Phillip Wood <firstname.lastname@example.org> To: Junio C Hamano <email@example.com>, firstname.lastname@example.org Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de> Subject: Re: Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks Date: Wed, 9 Oct 2019 16:13:14 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Junio On 09/10/2019 01:14, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > >> In other words, the commit message can be augmented by this: >> >> Acked-by: Johannes Schindelin <email@example.com> >> Acked-by: Derrick Stolee <firstname.lastname@example.org> >> Acked-by: Garima Singh <email@example.com> >> Acked-by: Jonathan Tan <firstname.lastname@example.org> >> Acked-by: Thomas Gummerer <email@example.com> >> Acked-by: brian m. carlson <firstname.lastname@example.org> >> Acked-by: Elijah Newren <email@example.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 <firstname.lastname@example.org> to my original reply in this thread, could you add it please Thanks Phillip > 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 email@example.com. 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 > firstname.lastname@example.org, or individually: > > - Ævar Arnfjörð Bjarmason <email@example.com> > - Christian Couder <firstname.lastname@example.org> > - Jeff King <email@example.com> > - Junio C Hamano <firstname.lastname@example.org> > > ## 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 >
next prev parent reply other threads:[~2019-10-09 15:13 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-07 3:38 What's cooking in git.git (Oct 2019, #02; Mon, 7) Junio C Hamano 2019-10-08 19:36 ` jk/code-of-conduct, was " Johannes Schindelin 2019-10-09 0:14 ` Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks Junio C Hamano 2019-10-09 0:22 ` Taylor Blau 2019-10-09 1:41 ` Emily Shaffer 2019-10-09 8:07 ` Johannes Schindelin 2019-10-09 1:48 ` Jonathan Nieder 2019-10-09 10:36 ` Christian Couder 2019-10-09 15:13 ` Phillip Wood [this message] 2019-10-09 18:29 ` Elijah Newren 2019-10-09 19:37 ` Junio C Hamano 2019-10-09 19:52 ` William Baker 2019-10-09 20:50 ` CB Bailey 2019-10-10 0:18 ` Eric Wong 2019-10-11 5:58 ` Jeff King 2019-10-17 13:56 ` Philip Oakley 2019-10-11 4:39 ` Junio C Hamano 2019-10-11 6:01 ` Jeff King 2019-10-09 1:39 ` jk/code-of-conduct, was Re: What's cooking in git.git (Oct 2019, #02; Mon, 7) SZEDER Gábor
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --cc=Johannes.Schindelin@gmx.de \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).