workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: corbet@lwn.net, workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: maintainer: discourage taking conversations off-list
Date: Fri, 12 Jul 2024 16:25:56 +0100	[thread overview]
Message-ID: <7570937c-ead6-40bc-b17f-4ade34a2acf6@sirena.org.uk> (raw)
In-Reply-To: <20240712144903.392284-1-kuba@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

On Fri, Jul 12, 2024 at 07:49:03AM -0700, Jakub Kicinski wrote:

> +Open development
> +----------------
> +
> +Discussions about user reported issues, and development of new code
> +should be conducted in a manner typical for the larger subsystem.
> +It is common for development within a single company to be conducted
> +behind closed doors. However, maintainers must not redirect discussions
> +and development related to the upstream code from the upstream mailing lists
> +to closed forums or private conversations. Reasonable exceptions to this
> +guidance include discussions about security related issues.

Reviewed-by: Mark Brown <broonie@kernel.org>

I do think it's fine for people to have open places like github as an
option as well, so long as they're optional for contributors and things
pass through the lists in a normal fashion at some point.  Directing
people towards existing relevant discussions/reviews can work well.  The
main issues are taking things out of all visibility and blocking
contributors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2024-07-12 15:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 14:49 Jakub Kicinski
2024-07-12 15:06 ` Greg KH
2024-07-12 15:25 ` Mark Brown [this message]
2024-07-12 15:42   ` Shuah Khan
2024-07-12 18:11     ` Mauro Carvalho Chehab
2024-07-12 18:19       ` Randy Dunlap
2024-07-12 23:45       ` Jakub Kicinski
2024-07-13  0:00         ` Dan Williams
2024-07-13  0:12           ` Jakub Kicinski
2024-07-13  7:43         ` Mauro Carvalho Chehab
2024-07-12 18:43 ` Dan Williams
2024-07-13  0:05   ` Jakub Kicinski
2024-07-13  1:18     ` Dan Williams
2024-07-13  8:13     ` Mauro Carvalho Chehab
2024-07-13 14:19       ` Laurent Pinchart
2024-07-13 16:07         ` Mauro Carvalho Chehab
2024-07-13 23:29           ` Jakub Kicinski
2024-07-15 13:29       ` Mark Brown
2024-07-13 14:26 ` Laurent Pinchart
2024-07-13 23:23   ` Jakub Kicinski
2024-07-13 14:28 ` Carlos Bilbao
2024-07-13 16:25   ` Mauro Carvalho Chehab

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=7570937c-ead6-40bc-b17f-4ade34a2acf6@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=workflows@vger.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