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

Alissa Cooper <alissa@cooperw.in> Sun, 27 January 2019 02:15 UTC

Return-Path: <alissa@cooperw.in>
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 A4A5A1288BD for <ietf@ietfa.amsl.com>; Sat, 26 Jan 2019 18:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=awJwxmNm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=e374qpsu
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 8nPvpUnsc9pG for <ietf@ietfa.amsl.com>; Sat, 26 Jan 2019 18:15:21 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B73F12896A for <ietf@ietf.org>; Sat, 26 Jan 2019 18:15:21 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2053E221A6; Sat, 26 Jan 2019 21:15:20 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Sat, 26 Jan 2019 21:15:20 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm2; bh=XORzMmtjfYXmzWznnBO4F1r Hjzi1vu9RodJLgRXgOrc=; b=awJwxmNmNyjxT7DA6DFhzyjuFHCXuyCNatdDVVQ 8eWcx4hUw9xnLB2RclFLo4qLXGdXVqyimcFMrl65M4CvOmVB/hxqA994zH60NMef 9Kt7rpvoI7avoKgeR13rLfjpn/yFMFwKasVMKSyEtdTweD7Stfk7rSmE2BAaVDIH q+ytMzHcoYUlv9mo7oWkr5W3ajfIDE55OYeIFE8osXbbVnYCrASMbjG1m5NQkgS2 V2dVRl2OXTioiQHMLTIlVTJJcWuy4GkiPkqWpe8RPK8hXXwig26Pwv+uPwBReJgD tiiu1gg4BjOs0ZBPVg2qHvF9X5RU3oa+9O1UlVKKdELcK8A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=XORzMm tjfYXmzWznnBO4F1rHjzi1vu9RodJLgRXgOrc=; b=e374qpsu2s8yO4+VT5Q9vj vTtCRV5JTiHbxa6NtBxYwWvHidX4tQSvu1BYwg5S7aWknbSfd9A77vqvc61JUQhd f/bzTjtB7XSt+zH7NAvHQmjZc9UZn5h/VgFigQPSuIbBrvrWmPfgtrokaMZvL8Sp aL1ZUeSVpLrFP0LtLDZrAME3GJncURzqGoZQ9UzMEsntkpSujyRPxt5Jo+BImjEl 0EkPAgdXgYXzED9R93w5ZAupbKzLgOiHxXD4r9vGwGRCBvOAp46irC8xZz720fCl FMf65FIJt3EgNpDhZTl6HyACiRBJcQC+piX2GNQjV4SVwjZmnSjxvRMB1nX9dqaA ==
X-ME-Sender: <xms:NxRNXBxXmmJ_1eTx5k6_Ayz1En5N9DFSwDgCJOSknLa9ynrsgTKqYA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrieejgdefkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffktgggufffjg fvfhfosegrtdhmrehhtdejnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceorghl ihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrihhnpehivghtfhdrohhrghdpgi hktggurdgtohhmnecukfhppedujeefrdefkedruddujedrieeknecurfgrrhgrmhepmhgr ihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsthgvrhfuih iivgeptd
X-ME-Proxy: <xmx:NxRNXJdPPP4agRvJrDkZzHkbXyIpTa7jStQ4sbhXlnkT5XBQix6P_w> <xmx:NxRNXG5P3kkga-jC_JFWHtkIqWyE-hCPTZ4kPt8NO1dmm2hjUjf1QQ> <xmx:NxRNXOIr5S5V34jozbqkxzQHxN-4atrLazOJPvVbuP1Tkhi1o6X4iA> <xmx:OBRNXFlN1sOpGGDuHeTRb6YB1xxteKfIPeIfiND6-ZoB2tq7-g7Acw>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.68]) by mail.messagingengine.com (Postfix) with ESMTPA id 252D3100BB; Sat, 26 Jan 2019 21:15:19 -0500 (EST)
From: Alissa Cooper <alissa@cooperw.in>
Message-Id: <57A386F8-080E-44D5-90DE-9B1B87CB2C88@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0E5EBDF9-BC09-415D-81C1-D392F4C0BB1F"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: sr.ht --- "sir hat" --- alternatives to Github
Date: Sat, 26 Jan 2019 21:15:17 -0500
In-Reply-To: <537655472.2105263.1548456565875@mail.yahoo.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>, IETF <ietf@ietf.org>
To: lloyd.wood=40yahoo.co.uk@dmarc.ietf.org
References: <25946.1547751133@localhost> <2062850122.1176466.1548052316757@mail.yahoo.com> <7C2EF2A7-B267-43BB-9A07-56835D184E71@tzi.org> <1a427a5b-dba7-5d18-393a-c39e99e1fbd8@joelhalpern.com> <20190121152616.GE81907@kduck.mit.edu> <009b01d4b238$901cb460$4001a8c0@gateway.2wire.net> <16559.1548194651@localhost> <5C47A7DF.7030307@isdg.net> <0160ae34-ec39-dda5-75c3-2dd87d35c7a3@si6networks.com> <26eb6a40-219f-84e1-03f6-21ad1037248a@outer-planes.net> <A6411553-A27C-4B06-9CEF-5A7E5A0C19B0@gmail.com> <537655472.2105263.1548456565875@mail.yahoo.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QM4hFDjeXkgS2AgNJ8BregzclxY>
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: Sun, 27 Jan 2019 02:15:23 -0000

Hi Lloyd,

> On Jan 25, 2019, at 5:49 PM, lloyd.wood=40yahoo.co.uk@dmarc.ietf.org wrote:
> 
> +1 to Bob's unanswered question. and why is this new list ietf-and-github and not ietf-and-git?

Mailing lists are cheap. If people felt that creating a separate one for ietf-and-git would be worthwhile, it wouldn’t be hard to do. As it stands both GitHub and git get discussed on the existing list, and that’s not a problem IMO.

Before initiating chartering of the GIT WG [1] I asked on the ietf-and-github list if people wanted separate lists for the WG and for more general discussion. There was one comment in favor of using ietf-and-github for the WG. That is the current plan.

Alissa

[1] https://datatracker.ietf.org/doc/charter-ietf-git/

> github is but one provider, backed by a proven monopolist... and that was the choice? that's a question suitable for this general list. So, on this thread topic, what viable alternatives are there?
> 
> it also strikes me that setting up a mailing list to discuss use of github is not really entering into the spirit of the thing, or showing github's strengths and weaknesses. it's very much the nice face of the idea.
> 
> Create a textfile with the mailing list charter, commit it to github, and then have discussions in the commit comments as everyone commits added trailing spaces to that file. if you're going to embrace github in discussions, do it properly...
> 
> 
> Lloyd Wood
> lloyd.wood@yahoo.co.uk
> 
> learn git? if I wanted to learn terse unmemorable commands that do arcane things, I'd learn unix.
> 
> On Friday, January 25, 2019, 3:44 am, Bob Hinden <bob.hinden@gmail.com> wrote:
> 
> Matthew,
> 
> Please explain why this discussion shouldn’t be happening on the IETF list?  Seems relevant to me.
> 
> Bob
> 
> 
> > On Jan 24, 2019, at 7:53 AM, Matthew A. Miller <linuxwolf+ietf@outer-planes.net <mailto:ietf@outer-planes.net>> wrote:
> > 
> > All,
> > 
> > Please direct all further discussion on using GitHub to <
> > ietf-and-github@ietf.org <mailto:ietf-and-github@ietf.org> >.
> > 
> > 
> > Thank you,
> > 
> > -
> > Matthew A. Miller
> > IETF Sergeant-at-arms
> > 
> > On 19/01/24 08:23, Fernando Gont wrote:
> >> On 22/1/19 20:31, Hector Santos wrote:
> >>> My opinion.
> >>> 
> >>> My only concern is the perception that the IETF is now "requiring" to
> >>> learn a new suite of 3rd party tools for a single purpose - RFC Draft
> >>> submissions publishing.  For people doing this all the time, and
> >>> probably also using the same tools for other parts of their career, I
> >>> can understand it would be productive, but not for the occasional author.
> >>> 
> >>> After several decades, I believe an application level IETF online RFC
> >>> publishing tool should be available.  In the past, I used XML2RFC (a
> >>> java app) to outline, produce and publish my drafts. Isn't this
> >>> available any more?  I would think a HTML5 version would be doable
> >>> today, and of course, some vcs would be integrated at the backend.
> >>> 
> >>> I personally don't want wish to be learning git details and all the
> >>> other scripting tools and text formats for a single purpose.  I would if
> >>> I have to at some top level rudimentary level just to get the job, but
> >>> it is not desirable, and certainly not a career requirement for me.
> >> 
> >> Don't worry: https://xkcd.com/1597/  <https://xkcd.com/1597/>(yes, there's a lot of truth to it
> >> :-) )
> >> 
> >> Thanks,
> >> 
> >