From: Chris Mason <clm@fb.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
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: Fri, 17 Sep 2021 14:36:31 +0000 [thread overview]
Message-ID: <323217C4-92F6-404B-857A-D40CDE6CADBC@fb.com> (raw)
In-Reply-To: <16bf12514f29a1b233c98cc8835f5e1b9331f719.camel@HansenPartnership.com>
> On Sep 17, 2021, at 9:00 AM, James Bottomley <James.Bottomley@hansenpartnership.com> wrote:
>
> On Fri, 2021-09-17 at 08:36 -0400, Konstantin Ryabitsev wrote:
>> On Fri, Sep 17, 2021 at 07:14:11AM -0400, James Bottomley wrote:
>>>> 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.
>>>
>>> In days of old, when knights were bold and cloud silos weren't
>>> invented, we had an ancient magic handed down by the old gods who
>>> spoke non type safe languages. They called it wiki and etherpad
>>> ... could we make use of such tools today without committing heresy
>>> against our cloud overlords?
>>
>> You mean, like https://pad.kernel.org ? :)
>>
>> However, a large part of why I was suggesting a git repo is because
>> it is automatically redistributable, clonable, and verifiable using
>> builtin git tools. We have end-to-end attestation with git, but we
>> don't have it with etherpad or a wiki. If the goal is to use a
>> document that solicits acks and other input across subsystems, then
>> having a tamper-evident backend may be important.
>
> I think the goal is to have a living document that records who should
> ack, what the design goals are who has what current concerns and how
> they're being addressed and what the status of the patch set is.
> Actually collecting acks for the patches would be the job of the author
> as it is today and verification would be via the public lists.
Thanks Konstantin for bringing up issues with google docs. I assumed different groups of people would store state differently, but didn’t think of this problem. One nice feature about google docs is you can mark issues as resolved etc, but obviously people can simulate that in other ways with etherpad.
-chris
next prev parent reply other threads:[~2021-09-17 14:37 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
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 [this message]
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=323217C4-92F6-404B-857A-D40CDE6CADBC@fb.com \
--to=clm@fb.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=kent.overstreet@gmail.com \
--cc=konstantin@linuxfoundation.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).