Hi all,
During our experiments with markdown, the RPC has tested the following
modifications to our editing and AUTH48 processes:
o Edit in markdown and focus only on content, not format.
o Present the markdown at the beginning of AUTH48 and
ask the authors to answer any questions we may have and
to approve the copy edits.
o Once the authors have approved the copy edits, we convert
the file to RFCXML and make formatting updates.
o We ask the authors to review and approve the XML file
and the HTML, text, and PDF outputs.
This splits the RPC edit passes into two: copy editing and formatting,
which is what Ekr is requesting below. We have received positive
feedback from authors who have participated in our experiments that this
has made AUTH48 easier for them, even without RPC use of GitHub repos.
Best regards,
Jean
On 4/16/25 5:39 PM, Eric Rescorla wrote:
On Wed, Apr 16, 2025 at 3:34 PM Jay Daley <exec-direc...@ietf.org
<mailto:exec-direc...@ietf.org>> wrote:
> On 17 Apr 2025, at 10:28, Eric Rescorla <e...@rtfm.com
<mailto:e...@rtfm.com>> wrote:
>
> As I said in my original message, I think the focus on GitHub for
this change
> is a mistake. The actual ask is to separate out content changes
from format
> changes, which can be done with or without GitHub.
I understand - my point here is that the commit feature of git
allows us to add a level of granularity to the edits that then makes
it easier to see what is going on, in the current process.
Yes, of course, but my concern here is that the desire to have
this kind of fine granulity not get in the way of having the kind
of coarse granularity described above, which provides most
of the value.
-Ekr
_______________________________________________
rfc-interest mailing list -- rfc-interest@rfc-editor.org
To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
_______________________________________________
rfc-interest mailing list -- rfc-interest@rfc-editor.org
To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
