On 17/09/2021 03:32, Mark Nottingham wrote:
Carsten,
It has been an informal tool for some time. I (along with others, apparently) am concerned about it becoming a formal dependency by stealth, consuming resources and causing confusion.
Mark
That is the way the IETF works; I do not think that it is a good way but
it is the way. If I want to know what resources are available, as in
supported, maintained, told when they will be withdrawn and such like, I
know of nowhere to go.
I think this is the reason why a survey earlier this year showed great
variation in how I-D are produced; there is nowhere to go to find out.
I have been pointed at, or stumbled across, ways of getting work done in
the IETF and get upset when they disappear with or without warning.
I had never heard of notes.ietf.org prior to this thread. If I had, I
might have found it useful and become dependent on it:-( Go look at
tools.ietf.org with the eyes of someone who has been told the way to do
it in the IETF it to write an I-D. First thing you see is RFC
Dependency checker followed by Bibtex Citation Converter ... We do a
really bad job of encouraging people to write I-D.
Tom Petch
If you have use cases for it, that's great -- bring them up and we can have a discussion about whether they should be supported (with the corresponding dedication of resources). You haven't done that, though - you seem to be assuming that because you've used an informal tool in a particular way in the past, that will automatically be supported on an ongoing basis.
In doing so, you've now also characterised others' positions in a disparaging way and expressed cynicism about the IETF process. I understand you may be frustrated, but I don't think doing so is constructive.
Cheers,
On 17 Sep 2021, at 12:15 pm, Carsten Bormann <cabo@xxxxxxx> wrote:
On 2021-09-17, at 01:40, Joel M. Halpern <jmh@xxxxxxxxxxxxxxx> wrote:
2) If folks want to use the tools for something else, great. But that does not create an obligation on the IETF to make the tool behave differently. If there is some other use case that is needed, either use some other tool, or convince the IETF that we need a tool to support the use case you have.
Joel,
You are falling prey to an availability bias here.
You have only ever been using that tool for minutes, so you think the tool needs to be changed to more closely follow some random thinking about minutes.
I don’t care that much whether the IETF destroys its draft minutes, because I do know to back up those drafts that I’ll likely need.
But leading this discussion in complete disregard for the other uses of this tool is exactly the kind of “I don’t understand this, so let’s break it” thinking that has recently become so characteristic of IETF process discussions.
Grüße, Carsten
--
Mark Nottingham https://www.mnot.net/
.
