From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com [96.44.175.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 612683FC0 for ; Fri, 17 Sep 2021 13:00:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hansenpartnership.com; s=20151216; t=1631883611; bh=ZOPaJbfizj2SVk+6cgy1IFOqZ6UyVbKrV3tVdli7zOo=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References:From; b=WV+vvhx/vnOxPtDQD73fbqmZ9HpEQrRuh0/EQwkcvyWhaXPFrau+5fk9mZ6gojGLb 1b818k5nTP4nWD2VPwWo7cXWGL3GEwEHZNIVTwAB4VB2RrH7GuzVcMR3UUBvq7Yhoe G1pDpmgz5fAYM64lC6CGNhxRYXahffXKVoHapnkI= Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id BB1681280BC1; Fri, 17 Sep 2021 06:00:11 -0700 (PDT) Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AgMMd75mjdMX; Fri, 17 Sep 2021 06:00:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hansenpartnership.com; s=20151216; t=1631883611; bh=ZOPaJbfizj2SVk+6cgy1IFOqZ6UyVbKrV3tVdli7zOo=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References:From; b=WV+vvhx/vnOxPtDQD73fbqmZ9HpEQrRuh0/EQwkcvyWhaXPFrau+5fk9mZ6gojGLb 1b818k5nTP4nWD2VPwWo7cXWGL3GEwEHZNIVTwAB4VB2RrH7GuzVcMR3UUBvq7Yhoe G1pDpmgz5fAYM64lC6CGNhxRYXahffXKVoHapnkI= Received: from jarvis.lan (c-67-166-170-96.hsd1.va.comcast.net [67.166.170.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id 634BE1280BB2; Fri, 17 Sep 2021 06:00:10 -0700 (PDT) Message-ID: <16bf12514f29a1b233c98cc8835f5e1b9331f719.camel@HansenPartnership.com> Subject: Re: [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers Summit topic? From: James Bottomley To: Konstantin Ryabitsev Cc: Chris Mason , Theodore Ts'o , Johannes Weiner , Kent Overstreet , Matthew Wilcox , Linus Torvalds , "linux-mm@kvack.org" , linux-fsdevel , "linux-kernel@vger.kernel.org" , Andrew Morton , "Darrick J. Wong" , Christoph Hellwig , David Howells , "ksummit@lists.linux.dev" Date: Fri, 17 Sep 2021 09:00:09 -0400 In-Reply-To: <20210917123654.73sz5p2yjtd3a2np@meerkat.local> References: <17242A0C-3613-41BB-84E4-2617A182216E@fb.com> <33a2000f56d51284e2df0cfcd704e93977684b59.camel@HansenPartnership.com> <261D65D8-7273-4884-BD01-2BF8331F4034@fb.com> <20210916210046.ourwrk6uqeisi555@meerkat.local> <20210917123654.73sz5p2yjtd3a2np@meerkat.local> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.4 Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 7bit 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. James