[rfc-i] Soliciting feedback: starting a satisfaction survey for the RFC Production Center and Publisher
bob.hinden at gmail.com
Wed Jan 16 14:44:28 PST 2019
Overall, I think this is a good idea and support it. Two comment below.
> On Jan 16, 2019, at 7:21 AM, Heather Flanagan <rse at rfc-editor.org> wrote:
> Hello community,
> In order to get a better sense of how well the RFC Production Center and Publisher are serving the needs of authors, I would like to start sending out a short survey to authors immediately after the publication of their RFC starting on February 1, 2019. Participation in the survey is entirely optional, but the expectation is that requesting feedback immediately after publication will be more effective than the current process of randomly selecting a percentage of authors who have published in the previous year and asking them to recollect what did and did not work for them.
> The proposed questions in the survey are:
> • Did the editing service provided by the RFC Editor improve the quality of your document? [Yes|No]
Suggest you also allow for free form text on this beside indicating Y/N, especially for the “No” answer.
> • What one thing would make the editing process easier or more effective? [Free form text]
Perhaps allowing more than one thing :-) For example:
What things would make the editing process….
> • May we contact you to discuss your suggestions or concerns further? [Yes|No]
> The RSE (me) will review the feedback and include aggregated results in my reports published during IETF meetings. This fits with the expectations of the RSE role as described in RFC 6635 (see Section 2.1.1. "Strategic Leadership and Management of the Publication and Production Functions")
> The survey will be handled via SurveyMonkey initially, though this may change in the future if we decide to either take it in-house or use a different service.
> If you have any questions, comments, or suggestions regarding this activity, please let me know!
> Heather Flanagan, RSE
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: Message signed with OpenPGP
More information about the rfc-interest