Re: [Tools-discuss] Content at notes.ietf.org is not archival

[Carsten Bormann <[e-mail]>]

Asynchronous collaboration: git. Usually in combination with a website like gitlab or GitHub. (This is what the GitHub discussion in the IETF was about.) 
Asynchronous means not everyone had to be present at the same time. 

Synchronous collaboration: more variety. Today often hackmd/hedgedoc. Traces of Google docs and such. 
Synchronous means the focus is on groups that meet and edit at the same time, but of course hedgedoc can be “abused” for asynchronous collaboration. Since sessions end and synchronous and asynchronous phases may alternate, a good git interface would be a highly desirable element of a tool for synchronous collaboration. 

The more successful of either of these employ markdown as a storage/interchange format for textual information (text is code). 

Oh, I’m talking about how my more successful students work, but the pattern may be transferable to work in the IETF (and has been).

Sent from mobile, sorry for terse

> On 19. Sep 2021, at 07:42, Lloyd W <[e-mail]> wrote:
> 
> 
>> On 16 Sep 2021, at 18:32, Mark Nottingham <[e-mail]> wrote:
>> 
>> the purpose of the tool is collaborative editing, NOT long-term reference
> 
> I thought github was the tool that the IETF was supposed to use to do collaborative editing? See RFC8874.
> 
> Lloyd Wood
> [e-mail]
> 
> wondering what the IETF mandated editor is.