Re: Proposal to migrate from QUIC GitHub wikis to quicwg.org
Will Hawkins <hawkinsw@obs.cr> Mon, 29 July 2024 20:27 UTC
Return-Path: <hawkinsw@obs.cr>
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 0F800C1840C8 for <quic@ietfa.amsl.com>; Mon, 29 Jul 2024 13:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=obs-cr.20230601.gappssmtp.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 PZsceX2049Gn for <quic@ietfa.amsl.com>; Mon, 29 Jul 2024 13:27:06 -0700 (PDT)
Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (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 37D33C1840C3 for <quic@ietf.org>; Mon, 29 Jul 2024 13:27:06 -0700 (PDT)
Received: by mail-qv1-xf32.google.com with SMTP id 6a1803df08f44-6b7b23793c1so20442856d6.0 for <quic@ietf.org>; Mon, 29 Jul 2024 13:27:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=obs-cr.20230601.gappssmtp.com; s=20230601; t=1722284825; x=1722889625; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=DMmBBfSzK1u3+i43LC+UEV3UXmhOXuuIp+DroGoagnw=; b=unrmxfGQmZnOzpYde1NpTfkqf9rAZtUX5IDk7WeKndG8eaUYbCOWfBWFsUQqpi2GOH nIiHAu123evwDXbYqXfrigI6tzEGQNOnXWohk5TTRuDGr6/lUAO3EH6a4EapvfVxgHhT cXEKhaVN1GqvwPxxEiC6pHZIl0rHhIWuQFhmbwgrrFjLZg6FWmzG4YD53p9B8gKLMrfI RfIVrRScWPFj2Acxm7lKBmLj2WzYSVH5neP+a3nHKdL3dor1TyXsSdMmYimjwmJ9k4CW MzWBeWmDyl5ceFqRx7He6VXWdvIx/SHAz9rkg8RCr/4p0r/CA7iGwmtsMEw7fpp97IeM ZE9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722284825; x=1722889625; h=content-transfer-encoding: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=DMmBBfSzK1u3+i43LC+UEV3UXmhOXuuIp+DroGoagnw=; b=EtjJCviooBFnLJHf1F30nk/cOY9mfkTQufiHWi9eqZPMVdB0VPJg22Ht4tLkxtkYLF zsJmie+hrggoe4mgrRBF3P0J/Gc4kA9BXNqlLO5CHqmtuhp9HWClT7skCPCoExjX9AzV +3hHOi4ZhiZluTcUfLVfh0qREHQN+5pOwMdaFmY1qHXg9KjKIM/uj1VGfkzX+Z1Rhi1+ pza7IDP+EKLj8Dc/98YMp/DZAEMxnARYI48r2jc0K3dj8ozGmoY4mRCD9Et1qiQBpF6g Eu41iOMtwD5MV0tuJ9DrawLyedc1ntnqq3jSJXL+PjJEb6QqDIcD3QynShO9c7UNnNOq bx+w==
X-Gm-Message-State: AOJu0YycFBOkd+U5Fmgw3GutN2xslq+dGAJBmyzB/BjM/ClHRUfG6DAR lgZCPTnnFxlgkp2ocFN5Mb+pECy9RXBYXJK8KrcpnCRTA97Bt5LPRSphCb9Dpj5hr30EXYRmSCQ w0zxzbkacZ/QemkWtfDfqDxSoZUeBmdfywX4kIg==
X-Google-Smtp-Source: AGHT+IGYWVEFgzSpLTCx3MjOyaVHwMdBOYsT6q3IjspJTgEqL6qgXN7ynsNDg6jNgOzx0rZtg3i4dYKyzJSBBtNRWN4=
X-Received: by 2002:ad4:5d66:0:b0:6b5:4435:fe4d with SMTP id 6a1803df08f44-6bb55ab08d2mr99384206d6.38.1722284825008; Mon, 29 Jul 2024 13:27:05 -0700 (PDT)
MIME-Version: 1.0
References: <24f54137-c806-405d-8e62-235ccaad1b2a@app.fastmail.com>
In-Reply-To: <24f54137-c806-405d-8e62-235ccaad1b2a@app.fastmail.com>
From: Will Hawkins <hawkinsw@obs.cr>
Date: Mon, 29 Jul 2024 16:26:51 -0400
Message-ID: <CADx9qWj8cRagq-DkbmeNAtxi7Gn2q6F9ryckaw-ch3qdddT9mA@mail.gmail.com>
Subject: Re: Proposal to migrate from QUIC GitHub wikis to quicwg.org
To: Lucas Pardue <lucas@lucaspardue.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: ANQ6SKP66JK2UQMXQAHBXFL2CBQ4MAE6
X-Message-ID-Hash: ANQ6SKP66JK2UQMXQAHBXFL2CBQ4MAE6
X-MailFrom: hawkinsw@obs.cr
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/Nl8WIhzWKjC1n3YuwqZVYPRSXXg>
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>
On Sun, Jul 28, 2024 at 12:24 AM Lucas Pardue <lucas@lucaspardue.com> wrote: > > Hi folks, > > During the standardisation of QUIC, we made a lot of use of GitHub's wiki capabilities in the primary base-drafts repo that housed all drafts at that time [1]. This was a community effort. Everyone had write access and the wiki tracked the leading edge of development closely. > > Since the RFCs were published things have matured and stabilised. We've seen several new documents get adopted and worked on in their own repos. Yet the base-draft remained the spiritual centre of wiki, especially when it came to listing implementations or tools. Even if they weren't updated as frequently. > > Unfortunately, last year the wiki was vandalised and needed restoration. At the same time, to prevent further vandalism, we restricted access to wiki edits to GitHub accounts that had certain repo privileges. However, that's had the unfortunate effect of preventing useful grass roots contribution and maintenance. Further investigation into this area has indicated to me that the GitHub access control approach and UI for wikis is not suited to our regular ways of working: issues and pull requests from anyone, merges by authorised users only. > > The quicwg.org homepage is intended to be an easy-to-use hub for the QUIC WG. It's also powered by GitHub [2]. It links off to the wiki for some, but not all, content there. > > 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. > > I've already floated the idea in the QUIC slack, and the general sentiment is in support of doing the migration. So I'm opening up the proposal to a broader participant list. I'm especially interested if you have objections, or if you have thought or ideas about how best to migrate and present the content (especially if you'd like to volunteer on UI design or other related matters). I believe that my attempt at contributing a minor typo fix was the impetus for this email. Thank you for taking my attempt to "add value" so seriously. Because I had a hand in bringing this issue to a head, I wanted to 1. Nod in support of a migration, and 2. Offer to help with the technical aspects of the migration. Please let me know if/how I can help! Thank you, again, for bringing this discussion into the open! Sincerely, Will > > Cheers > Lucas > > > [1] https://github.com/quicwg/base-drafts/wiki > [2] https://github.com/quicwg/quicwg.github.io >
- Proposal to migrate from QUIC GitHub wikis to qui… Lucas Pardue
- Re: Proposal to migrate from QUIC GitHub wikis to… Will Hawkins
- Re: Proposal to migrate from QUIC GitHub wikis to… Ted Hardie
- Re: Proposal to migrate from QUIC GitHub wikis to… Lucas Pardue
- Re: Proposal to migrate from QUIC GitHub wikis to… Ted Hardie
- Re: Proposal to migrate from QUIC GitHub wikis to… Lucas Pardue