[rfc-i] Provide a way to manage source files used in generating RFC XML

Carsten Bormann cabo at tzi.org
Fri Oct 31 10:29:28 PDT 2014

Token-passing is a *powerful* way to impede progress.

Of course, you don't want two contributors to do the same work twice,
which calls for some minimal coordination, but that is not token-passing
at all.

> With modern version control and merging tools, any text-based format
> that lends itself to easy merging with existing merge tools is a boon:
> every contributor pushes their edits into their own branches and
> someone merges them.

Exactly.  If you haven't done this, you haven't seen the future.
True collaborative, concurrent editing.
(The future is already here, just not evenly distributed.)

> The markdown->xml approach may be the best for
> this, but then again, most merge tools are awful at merging prose.

If people doing edits don't insist on reformatting source paragraphs all
the time, the usual merge tools work great with markdown or other "just
write" formats.  (That little detail is the main reason why gfm is
inferior in practice to other markdown dialects.  Soft + explicit hard
line breaks rule.)

> A 3-way XML diff tool would be a good thing to have.

Shudder.  Structural merges are infinitely more difficult than
line-oriented textual ones.

Gruesse, Carsten

More information about the rfc-interest mailing list