On 2021-09-16, at 10:53, Mark Nottingham <mnot@xxxxxxxx> wrote: > >> On 16 Sep 2021, at 6:34 pm, Carsten Bormann <cabo@xxxxxxx> wrote: >> >> On 2021-09-16, at 10:31, Mark Nottingham <mnot@xxxxxxxx> wrote: >>> >>> We already have a large number of places that people need to look for data. Adding another is not optimal, especially when the purpose of the tool is collaborative editing, NOT long-term reference. >> >> Sure. I just don’t know how crippling notes.ietf.org will help with Google docs, hackmd.io, and all these other places. Actually, it will drive people back to those. > > I have so many questions :) … and that is completely OK, because different WGs have different ways to do work, so this all may not be obvious. > Why is it an issue that people use those other services for scratch documents? It is not an issue; it is a missed opportunity. I wrote: >> Collecting notes in our own service (as opposed to hackmd.io or Google docs) gives us more control. >> Another benefit of having a common service is that, after a while, everybody knows how to use it and we can integrate it into other tools. > If temporary documents aren't appropriate, what guarantees do you need regarding archival storage, reliability, availability, etc? Reasonable care. The point is not that this needs to be protected against nuclear attacks, but that we keep some basic level of service that is not intentionally throwing away other people’s work. > Why does the IETF have to run this service, instead of relying on a third party? See above. It doesn’t “have” to run this service; it just historically has done so and it turned out to be useful (much more useful after the switch to CodiMD/Hedgedoc). > How do these now long-lived documents interact with RFCs, Internet-Drafts, Datatracker and meeting proceedings (the various sources of truth we currently have)? In particular, when someone references a document there and presumes it's IETF-sanctioned? Then they are wrong. But they already can do that with Internet-Drafts. If that helps, add an obnoxious disclaimer at the top. > Who determines that it's worth the cost of providing such a long-lived service? I don’t know the cost, but it seemed to be limited. (Etherpad was available for a long time, but was having availability problems. Kudos to Robert for “creating” this problem in the first place by switching to a more reliable software base.) Who determines the value? The users. I think we have a clear result there (maybe not in your quarters of the IETF). Grüße, Carsten
