Re: sr.ht --- "sir hat" --- alternatives to Github

Richard Barnes <rlb@ipv.sx> Tue, 22 January 2019 21:03 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5321F1310F1 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2019 13:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.04
X-Spam-Level:
X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJzzliHbgqtf for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2019 13:03:41 -0800 (PST)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CE2E13107D for <ietf@ietf.org>; Tue, 22 Jan 2019 13:03:41 -0800 (PST)
Received: by mail-oi1-x22f.google.com with SMTP id t204so18653481oie.7 for <ietf@ietf.org>; Tue, 22 Jan 2019 13:03:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Am1SR+hVUULW9BmzZJlgqhyUOp/X8VB4mBDndKnkNGQ=; b=UiigdZfltVP4ZP5QZF1zWimu9ce48rPLt4LRWJ4c3/VuGYTHild64s1Wi4u4dc+rOP R8hDc/fBjxK4EK8LnQPkTD3SEcT95HP5mzRvQQptymFd5pJzYOu+7lGsQBU5iB+YiESD o9TFkRHOvDOsJlVDL8KklBjzi/hgVqU++NQTKm8WkMyVzrCWjSq44KATjqTiclMp1MFc jD2PQVyDydkx+AEgk7nLtwnHXXjCrANQn43La6Q9QSLg+r6SX1wTpeD7ONIOjZhKvcJO A1tP6qO27iFaKWDe6srrOUaJlg0a0BLokDXTbSnA282a/7IbNWR8ptDxGKIs2Es52HIQ OahQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Am1SR+hVUULW9BmzZJlgqhyUOp/X8VB4mBDndKnkNGQ=; b=Wyz5UQT9rDLSeS2QcZFg/zICLKkVT0p0oRM0cTPl4sEAOQPKSKYQRXbQe8PE/+hf7l rhQ7cFX1pbcn0HdqTUbm9dvpD83Lb0XQ8B85XD7Bj+k4otWsMZLfKH4v5hOxyyY8bjFb xXlhjLki/SD9eb0TQkCPkuM6DXPwv8EtxPKO4WD23syijDhD0UQvwlw5XxYIlnG19gs7 GdzaqZoSuzy/V6T4kD/Sx596AvQVKA7Gzk1BTkCxKdhNu1+j1j51CRNdOIexIJUQCKjU mPrIFCbWbx9Q4TB6RtYPEnvl6kERJmxoO4l/JKjkMmYoJN2s6ysNN+49LkxtCYuFJIh5 j7HQ==
X-Gm-Message-State: AJcUukcftOefFYVg//B5/5jjZWFzW7napnBq8YFCsxuJw8l65xgPWdUy d6psHKeSuThCKJHE+fv1iA+lrW9+Mupc9iNPWFsLSUFxMu8=
X-Google-Smtp-Source: ALg8bN7VkC58jIuPJPYtIcDagkMJW0NOdWP1FyrXlnnizxU78QfWuzS3o+fShEvxL3RYYNY99z/iG4fLisx7FuBTO7g=
X-Received: by 2002:aca:308f:: with SMTP id w137mr9753304oiw.49.1548191020385; Tue, 22 Jan 2019 13:03:40 -0800 (PST)
MIME-Version: 1.0
References: <25946.1547751133@localhost> <2062850122.1176466.1548052316757@mail.yahoo.com> <7C2EF2A7-B267-43BB-9A07-56835D184E71@tzi.org> <1a427a5b-dba7-5d18-393a-c39e99e1fbd8@joelhalpern.com> <CABcZeBMEw1Vmi9QFUOBOzav+tvxthPn+S=W_QJ0UfsjfhC4U1g@mail.gmail.com> <5C478267.5000904@isdg.net>
In-Reply-To: <5C478267.5000904@isdg.net>
From: Richard Barnes <rlb@ipv.sx>
Date: Tue, 22 Jan 2019 16:03:27 -0500
Message-ID: <CAL02cgSycu5AQ2+18_KfvFPMspfT-vaiX3vsi0h8fOiXg4-4XQ@mail.gmail.com>
Subject: Re: sr.ht --- "sir hat" --- alternatives to Github
To: hsantos@isdg.net
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d09c480580124fe1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DWvSKQKB6aNFjwbtGiXruBdUk44>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2019 21:03:43 -0000

On Tue, Jan 22, 2019 at 3:52 PM Hector Santos <hsantos=
40isdg.net@dmarc.ietf.org> wrote:

> On 1/21/2019 12:51 PM, Eric Rescorla wrote:
> >
> >
> > Yes, I agree with this, and I don't think that this proposed WG is or
> > should be about pushing people to adopt Git/Github.
> >
> > However, with that said, if someone came to me and asked me what
> > toolchain I thought they should use to write an I-D, I would advise
> > them to use Github.
> >
> > -Ekr
>
> Practical.  But why GITHUB?  Why not push for an IETF Git server?
>

Because GitHub > git.  Pull requests, diff views, review requirements, etc.

If you'd said GitLab, maybe more plausible.  But still not a good use of
IETF resources.


Full control. Not dependent on 3rd party and you don't have to wait on
> Microsoft/GitHub for any advanced integration with other parts of the
> IETF RFC review/editing/publishing system. Like you indicated, I would
> think most work is under one editor, so it's really an overkill.
>
> I understand the pressure to use what's comfortable with many today,
> so I don't like the idea its being used more and more, sort of forcing
> others to do the same.
>
> PS: We are still using CVS for our products! Very old school, but it
> does the job and no money wasted on duplicity.
>
> That said, is there an RFC on using GitHub for publishing?
>

I believe that a WG has been proposed to develop such a thing.  In the
meantime, there's https://github.com/martinthomson/i-d-template/

--RLB