Re: [OPS-AREA] Q: Why no open yang-discuss@ietf.org mailing list ?
Toerless Eckert <tte@cs.fau.de> Fri, 25 June 2021 19:02 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ops-area@ietfa.amsl.com
Delivered-To: ops-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D22D43A0896; Fri, 25 Jun 2021 12:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.871
X-Spam-Level:
X-Spam-Status: No, score=-0.871 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 YndFl6DN9VOn; Fri, 25 Jun 2021 12:02:26 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 408A73A08C6; Fri, 25 Jun 2021 12:02:19 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 2C29B54806D; Fri, 25 Jun 2021 21:02:08 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 245874E7879; Fri, 25 Jun 2021 21:02:08 +0200 (CEST)
Date: Fri, 25 Jun 2021 21:02:08 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Andy Bierman <andy@yumaworks.com>
Cc: ops-ads@ietf.org, ops-area <ops-area@ietf.org>, benoit.claise@huawei.com
Message-ID: <20210625190208.GK5057@faui48e.informatik.uni-erlangen.de>
References: <20210625180557.GJ5057@faui48e.informatik.uni-erlangen.de> <CABCOCHTua2zxVwpYcKwK7DqUkrOWLsHH+01Kev_+KZ3ctuQDeQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CABCOCHTua2zxVwpYcKwK7DqUkrOWLsHH+01Kev_+KZ3ctuQDeQ@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ops-area/YZiE-GaN13Q8_Fe_sXUiBDwyZ7U>
Subject: Re: [OPS-AREA] Q: Why no open yang-discuss@ietf.org mailing list ?
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ops-area/>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2021 19:02:31 -0000
Thanks, Andy, inline On Fri, Jun 25, 2021 at 11:25:04AM -0700, Andy Bierman wrote: > IMO email is not the greatest way to help people figure out YANG. Thats probably true for many if not most IETF technologies. I was only claiming it would be extremely helpful to have instead of not having it. In-person discussions or online meeting calls for example are often btter too ;-) > I remember discussing the idea with the ADs in the past about moving > RFC 8407 online, and updating it often as needed. (As opposed to recording > another yang-next issue and forgetting about it). No reason not to start such an effort yourself. Alas, our tooling is not ideal to make it easy. I wouldn' recommend codimd as it does not allow to asily undo changes, which leaves our trac wiki, which is ok, but just a good amount of work to convert the rfc first into the format and be somewhat diligent on having a good changelog. > Maybe an online IETF YANG FAQ would help. This one ? https://trac.ietf.org/trac/netmod/wiki/YANG_FAQ Neith of these type of wiki pages are IMHO a good reason to NOT have a mailing list though. > FYI... > I posted this email to yang-doctors on May 5 and got no response... > > Hi, > > I know Benoit tried very hard to make the IETF proactive and > engage the user and tools community. He actually used to do > the stuff below in f2f meetings on Sunday sessions at the IETF > > I notice that the YANG doctor review process is very heavyweight, > scarce resources, and very official. Sure. WHich is exactly why i suggested to add the simple options which _may_ help mor with self-help. > What if we proactively headed off bad YANG usage before it got to the YD > review? > > What if we had a FAQ on good YANG usage, and a WEB site so people > could submit questions to the YANG doctors about their modules. > Each question becomes another entry in the FAQ. Sure. For both of this we need easy options for more participants to contribute and help each other. Did i say mailing list ? > It should be open to any YANG developer, even vendors, not just all SDOs. > Sponsors should get a small logo on the Sponsors tab. > If it cannot be hosted by the IETF than maybe a new WEB site can be created > for it. There is nothing in our IETF processes that would prohibit anyone to participate. > Is there any interest in such a project? > > I have found that if you steer people into good design and > don't make them start over then they will just do it. > Now if we could only get people to design the data model before they start > writing it.... ;-) Cheers Toerless > Cheers > > Toerless > > > > > Andy > > > > > > > _______________________________________________ > > OPS-AREA mailing list > > OPS-AREA@ietf.org > > https://www.ietf.org/mailman/listinfo/ops-area > > -- --- tte@cs.fau.de
- [OPS-AREA] Q: Why no open yang-discuss@ietf.org m… Toerless Eckert
- Re: [OPS-AREA] Q: Why no open yang-discuss@ietf.o… Andy Bierman
- Re: [OPS-AREA] Q: Why no open yang-discuss@ietf.o… Toerless Eckert