From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Dave Airlie <airlied@gmail.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC FOR KS] CoC and Linus position (perhaps undocumented/closed/limited/invite session)
Date: Wed, 19 Sep 2018 19:44:44 -0700 [thread overview]
Message-ID: <1f375c3d2c41da463d0cd055428d2933984a5942.camel@perches.com> (raw)
In-Reply-To: <20180919210122.694bf4a3@coco.lan>
On Wed, 2018-09-19 at 21:01 -0300, Mauro Carvalho Chehab wrote:
> I'm actually in favor of the opposite: to remove everything that looks
> like a legal contract.
Yes please.
Our Responsibilities
> ====================
>
> Maintainers are responsible for clarifying the standards of acceptable behavior
> -and are expected to take appropriate and fair corrective action in response to
> +and are asked to take appropriate and fair corrective action in response to
> any instances of unacceptable behavior.
[]
> -Maintainers have the right and responsibility to remove, edit, or reject
> -comments, commits, code, wiki edits, issues, and other contributions that are
> +Maintainers have the right 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.
> +offensive or harmful.
This paragraph is unnecessary.
Maintainers are responsible for code.
Community is responsible for behavior.
next prev parent reply other threads:[~2018-09-20 11:04 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 5:55 Dave Airlie
2018-09-18 13:43 ` Steven Rostedt
2018-09-18 14:34 ` Daniel Vetter
2018-09-18 14:58 ` Geert Uytterhoeven
2018-09-20 9:12 ` Rafael J. Wysocki
2018-09-20 9:53 ` Daniel Vetter
2018-09-20 10:05 ` Daniel Vetter
2018-09-20 15:57 ` Mark Brown
2018-09-18 14:02 ` James Bottomley
2018-09-18 14:41 ` Daniel Vetter
2018-09-18 19:29 ` Mauro Carvalho Chehab
2018-09-18 19:36 ` Josh Triplett
2018-09-18 19:52 ` Mauro Carvalho Chehab
2018-09-18 20:52 ` Takashi Iwai
2018-09-18 21:15 ` Josh Triplett
2018-09-18 23:06 ` Steven Rostedt
2018-09-18 23:38 ` Laurent Pinchart
2018-09-18 19:58 ` Arnaldo Carvalho de Melo
2018-09-19 11:28 ` James Bottomley
2018-09-19 11:37 ` Mauro Carvalho Chehab
2018-09-19 12:03 ` Mauro Carvalho Chehab
2018-09-19 14:16 ` James Bottomley
2018-09-19 16:06 ` Mauro Carvalho Chehab
2018-09-19 19:55 ` Mauro Carvalho Chehab
2018-09-19 20:10 ` Luck, Tony
2018-09-19 23:28 ` Mauro Carvalho Chehab
2018-09-19 23:45 ` Tim.Bird
2018-09-19 20:23 ` Dave Airlie
2018-09-20 0:01 ` Mauro Carvalho Chehab
2018-09-20 0:22 ` Tim.Bird
2018-09-20 6:33 ` Jani Nikula
2018-09-20 7:01 ` Josh Triplett
2018-09-20 7:11 ` Daniel Vetter
2018-09-20 7:04 ` David Woodhouse
2018-09-24 13:53 ` Mel Gorman
2018-09-25 5:45 ` Leon Romanovsky
2018-09-20 10:19 ` Laurent Pinchart
2018-09-20 10:23 ` Mauro Carvalho Chehab
2018-09-20 12:31 ` Jani Nikula
2018-09-20 13:04 ` Mauro Carvalho Chehab
2018-09-20 13:49 ` Tim.Bird
2018-09-20 13:55 ` Laurent Pinchart
2018-09-20 19:14 ` Tim.Bird
2018-09-20 19:55 ` Laurent Pinchart
2018-09-20 20:11 ` Dmitry Torokhov
2018-09-20 20:14 ` Jonathan Corbet
2018-09-20 20:52 ` Mauro Carvalho Chehab
2018-09-20 2:44 ` Joe Perches [this message]
2018-09-20 11:11 ` Laurent Pinchart
2018-09-20 13:35 ` Joe Perches
2018-09-20 3:38 ` Stephen Hemminger
2018-09-20 12:28 ` Eric W. Biederman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f375c3d2c41da463d0cd055428d2933984a5942.camel@perches.com \
--to=joe@perches.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=airlied@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mchehab+samsung@kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox