Re: Proposal to migrate from QUIC GitHub wikis to quicwg.org

Ted Hardie <ted.ietf@gmail.com> Tue, 30 July 2024 13:43 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6063EC14CEE4 for <quic@ietfa.amsl.com>; Tue, 30 Jul 2024 06:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PUahGO5i4v1A for <quic@ietfa.amsl.com>; Tue, 30 Jul 2024 06:43:13 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F39EC14F71E for <quic@ietf.org>; Tue, 30 Jul 2024 06:43:13 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-58ef19aa69dso5091615a12.3 for <quic@ietf.org>; Tue, 30 Jul 2024 06:43:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722346992; x=1722951792; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=EmMxPhYYUXqNH5aWF/ls+tnlVYZ+uEYlTfa+swJ2fLI=; b=TMbErIg/U/4kZJyv8Tlx9xJmY7Egfg2un6JXCOJNxPyw6vElIPT9f/+FtKJ0ZrfWhw nyiipe/sqSxV52A54Zt3NSMazp3Pw07xMNK54zqI16cycXURCJQA+yxIKN8EkGdbbKRJ HxLRDCxucgG9FSM6KVXi/kXj6IMjPhQboDG3ga1rPexvzjymsBTAZGN+XZPHd2uoOtIm +kVaRIU9dn4xkUvR9u2/pSECeGS18hj6/v/YrNqJCr6GLh4sBBQkLt/zs62vht8QizJu lYVu3QvzufrC7Grmw3fOkyb+G2YIw0BXhfTwdl8rGRDWf5+ZStPVzsrqcR80D2s1rhGt emeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722346992; x=1722951792; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=EmMxPhYYUXqNH5aWF/ls+tnlVYZ+uEYlTfa+swJ2fLI=; b=AKPvm27fD53jcVsqg0osHUK3zSpa26nGewsy7YEKEc09exssC7ZYFP74CzXQw/8v9G TEtMPcItU4Ue22iEDgyhSS9QMAf9ShqcSBSAZ+6dTT78FR2O5+9nQcdQdhOegr2yhHqK j6sBF/lwcOql14dBZOHe30juRicX2LrwGku/yqDO4LFrh+3Wk/pNVvowliZoQoLNSNZM wbNTq5NriajNgKM3vkamN2/fz+xyF1N27OWdRQlaf3nh+UB0s5zjG3bc90dCcnf4XD8y FbuOiNR+CBQ6lIJS8bFIMC8w+ZhO2X9qs1K++uufgP2CsGrFkPYHbq41QkyY9BL8ZU9v KMRg==
X-Gm-Message-State: AOJu0Yz0JOJZtqXJ+yQ//UpRPCf5asEOu0oT52An+yR4PR9epYrZGPkz FI00sodGtOpIUFIbPkJ5gc4n3eamaJKoiVKuRhm2SMZElPrLg6TQTu3f1KOoL/vBAvsvd5P7D8w rhaO60jcFyw9joIIYc2qt4NLXzOXrju0n
X-Google-Smtp-Source: AGHT+IHGGXv76pOAzU4Ph8FsaNwCsHYABQP9DrCF+KepgUyWxLTOO67lUk0Z5lvgCvh4kg0ynV6RQBMnmUh7BhkSm6A=
X-Received: by 2002:a05:6402:2707:b0:58c:eee0:48f4 with SMTP id 4fb4d7f45d1cf-5b0224cf056mr7275451a12.31.1722346991501; Tue, 30 Jul 2024 06:43:11 -0700 (PDT)
MIME-Version: 1.0
References: <24f54137-c806-405d-8e62-235ccaad1b2a@app.fastmail.com> <CA+9kkMDTYeVvkPMHXz7EsNbO1qB0ArYnnFrCxio8X2QJGfjGfA@mail.gmail.com> <f3c381cc-8603-40f2-958e-333bba8bf1ef@app.fastmail.com>
In-Reply-To: <f3c381cc-8603-40f2-958e-333bba8bf1ef@app.fastmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 30 Jul 2024 14:42:44 +0100
Message-ID: <CA+9kkMA5x4X8ZgY1ENK2QvpFcFLfMQ6Fn9amffPCzYWT-hZvMA@mail.gmail.com>
Subject: Re: Proposal to migrate from QUIC GitHub wikis to quicwg.org
To: Lucas Pardue <lucas@lucaspardue.com>
Content-Type: multipart/alternative; boundary="0000000000009bcdb3061e77285c"
Message-ID-Hash: SE3JVJEEXYXITD7Z7TVJIVDQEFYSV5PA
X-Message-ID-Hash: SE3JVJEEXYXITD7Z7TVJIVDQEFYSV5PA
X-MailFrom: ted.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-quic.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: quic@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iOiXp2L17qydswdVrtxhIHwDTfI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Owner: <mailto:quic-owner@ietf.org>
List-Post: <mailto:quic@ietf.org>
List-Subscribe: <mailto:quic-join@ietf.org>
List-Unsubscribe: <mailto:quic-leave@ietf.org>

Hi Lucas,

Thanks for the reply.  Given that reply, I think it would make sense for
the wg to see a more worked description of how the contribution mechanics
would work.  At the moment, updating the wiki requires certain permissions
for the repo; if the end state after you've worked this out is functionally
the same, then this change doesn't really improve things and can probably
be safely put aside.  If there is a way to do this that allows "useful
grass roots contribution and maintenance" without similar permissions, it
would be useful for the working group to understand it when making this
decision and also to document that for other groups that might have similar
issues.

Just my personal opinion, of course,

Ted Hardie

On Tue, Jul 30, 2024 at 10:36 AM Lucas Pardue <lucas@lucaspardue.com> wrote:

> Hi Ted,
>
> On Tue, Jul 30, 2024, at 10:15, Ted Hardie wrote:
>
> Hi Lucas,
>
> I think I am missing something fundamental here:
>
> I'd like to propose that we migrate away from using GitHub wikis for all
> repositories in the quicwg org, towards using the quicwg.org pages. This
> is intended to improve the contribution and change process. It is hoped
> that this will also improve the discoverability of content on the wiki.
> During any migration, content will continue to reside on the wiki.
>
> There is nothing on those pages that I could see that indicates how you
> can propose a change to the pages.  If the aim here is to enable "useful
> grass roots contribution and maintenance.", I think it would be appropriate
> to say more about how this migration does that, because I don't understand
> it.  The quicwg website doesn't even indicate how to contact the
> maintainers, so it's hard to see how it enables a grassroots effort.
>
> Indeed, the current quicwg.org has been mostly operated by the chairs,
> with a small number of contributions from those that might have stumbled on
> the repo.
>
> Consolidating useful information to a single place would come with
> improving the documentation on how to contribute, whether it be an issue or
> a PR to the repo [1]. And of course, we would cover the requisite notes on
> contribution code of conduct and note well.
>
> Cheers
> Lucas
>
> [1] https://github.com/quicwg/quicwg.github.io
>
>