From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Chris Mason <clm@fb.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Theodore Ts'o <tytso@mit.edu>,
Johannes Weiner <hannes@cmpxchg.org>,
Kent Overstreet <kent.overstreet@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers Summit topic?
Date: Thu, 16 Sep 2021 17:00:46 -0400 [thread overview]
Message-ID: <20210916210046.ourwrk6uqeisi555@meerkat.local> (raw)
In-Reply-To: <261D65D8-7273-4884-BD01-2BF8331F4034@fb.com>
On Thu, Sep 16, 2021 at 08:38:13PM +0000, Chris Mason wrote:
> Agree here. Mailing lists make it really hard to figure out when these
> conflicts are resolved, which is why I love using google docs for that part.
I would caution that Google docs aren't universally accessible. China blocks
access to many Google resources, and now Russia purportedly does the same.
Perhaps a similar effect can be reached with a git repository with limited
commit access? At least then commits can be attested to individual authors.
> A living document with a single source of truth on key design points, work
> remaining, and stakeholders who are responsible for ack/nack decisions.
> Basically if you don’t have edit permissions on the document, you’re not one
> of the people that can say no.
>
> If you do have edit permissions, you’re expected to be on board with the
> overall goal and help work through the design/validation/code/etc until
> you’re ready to ack it, or until it’s clear the whole thing isn’t going to
> work. If you feel you need to have edit permissions, you’ve got a defined
> set of people to talk with about it.
>
> It can’t completely replace the mailing lists, but it can take a lot of the
> archeology out of understanding a given patch series and figuring out if
> it’s actually ready to go.
You can combine the two and use mailing lists as the source of truth by using
Link: tags in commits to make it easy to verify history and provenance.
-K
next prev parent reply other threads:[~2021-09-16 21:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 17:42 [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers Summit topic? Theodore Ts'o
2021-09-15 18:03 ` James Bottomley
2021-09-15 18:20 ` Theodore Ts'o
2021-09-15 18:41 ` Chris Mason
2021-09-15 19:15 ` James Bottomley
2021-09-15 20:48 ` Theodore Ts'o
2021-09-16 14:55 ` Kent Overstreet
2021-09-16 13:51 ` David Howells
2021-09-16 16:46 ` Chris Mason
2021-09-16 17:11 ` James Bottomley
2021-09-16 19:15 ` Theodore Ts'o
2021-09-16 19:26 ` Andrew Morton
2021-09-16 20:16 ` Kent Overstreet
2021-09-17 1:42 ` Theodore Ts'o
2021-09-17 4:58 ` Kent Overstreet
2021-09-16 20:38 ` Chris Mason
2021-09-16 21:00 ` Konstantin Ryabitsev [this message]
2021-09-17 11:14 ` James Bottomley
2021-09-17 12:36 ` Konstantin Ryabitsev
2021-09-17 13:00 ` James Bottomley
2021-09-17 14:36 ` Chris Mason
2021-09-16 17:15 ` Kent Overstreet
2021-09-16 22:27 ` Chris Mason
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=20210916210046.ourwrk6uqeisi555@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=kent.overstreet@gmail.com \
--cc=ksummit@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).