Re: [Rfced-future] Suggested text for issues #56, #57, #61, #62

[Eliot Lear <[e-mail]>]

On 23.06.21 05:06, Brian E Carpenter wrote:
> I may have missed it, but I don't there's a github issue for finalizing the role and title of the RSEA. That's where I would like to hang this comment.

There are several, one of which we just are in the process of closing.  
The title one I have deferred discussing for the moment.  We also have 
the agreed text from Issue 12:

> This person will be a senior professional with deep knowledge of 
> technical publishing.
>
> The RSE will operate by providing expert advice to the RSAWG, and if 
> requested, to the RPC, on any relevant matters. The value this 
> individual provides is an understanding of the process of technical 
> publishing. They expected to learn how the process is applied in the 
> RFC series. They will be asked to produce regular reviews of the 
> process and identify problems and opportunities for improvement. There 
> are also opportunities to spontaneously learn of these problems, 
> likely the result of interactions with day-to-day operations. The 
> person may be requested to draft documents
>
> For example, the RSE might be consulted about proposed changes to the 
> style guide, RFC formatting in general, web presence, copyright 
> matters, or archiving policy, or might of their own initiative suggest 
> such changes to the RSAWG.
>
> The RSE is expected to attend all RSAWG meetings, and to have an 
> ongoing working relationship with the RPC and tooling team.
>
https://github.com/intarchboard/program-rfced-future/blob/master/Issue12-RSE-role.md

This text needs to make its way into the draft.  That is not to say this 
text can't improve, but this was what we agreed.

Eliot