Re: [Emo-dir] quick-start guides

I strongly agree with Mirja here. The problem we were discussing last week was how to help people get started... quickly... without overwhelming them with options and choices. I think we need a very limited set of choices in this instance. At the end of the short quick start guides... we can point to more information and detailed instructions elsewhere.

Remember this can always evolve as we learn more. Done is better than perfect.

Karen
________________________________
From: Emo-dir <emo-dir-bounces@ietf.org> on behalf of Mirja Kuehlewind <ietf@kuehlewind.net>
Sent: Tuesday, February 1, 2022 3:03 PM
To: Carsten Bormann <cabo@tzi.org>
Cc: Salz, Rich <rsalz@akamai.com>; Lars Eggert <lars@eggert.org>; Alice Russo <arusso@amsl.com>; Jay Daley <exec-director@ietf.org>; emo-dir@ietf.org <emo-dir@ietf.org>
Subject: Re: [Emo-dir] quick-start guides

Not disagreeing with your point but the problem we discussed that the last meeting is that there is currently just too much choice and we need a quick start guide for those who actually just want A (simple) way to submit a draft….

> On 1. Feb 2022, at 20:41, Carsten Bormann <cabo@tzi.org> wrote:
>
> On 1. Feb 2022, at 19:02, Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
>>
>> I believe her numbers were on publish RFCs, not Internet-Drafts, and the assumption was already that the number is higher (and likely) increasing for drafts. Thanks for providing this number!
>
> Then I’m not sure what that number expresses.
> I write all my IETF documents in kramdown-rfc.
> I never give anything but the generated XML to the RFC editor (well, they could extract the markdown if they wanted to, but I know that their processes center around XML).
> Am I in the 10 % or the 90 %?
>
> I think the draft submission percentage indicates where people do their authoring work.
>
>> However, for the quick start guide for me the more important questions is what find people easier to use when they are starting as newcomers in the IETF for their very first (and in some cases even only) draft. For sure people likely don’t start by installing software on their device, so what they need is an actual template file, a (text) editor, and an online tool for conversion.
>
> I’m not sure newness in the IETF correlates with the level of affinity to software production techniques.
> There will be IETF newbs who will be put off by an environment that favors pure Web tools over locally installable tools that are amenable to source control, Makefiles etc.
> (And, conversely, there are old hands who like Web tools a lot.)
>
> The only thing that is true over the IETF as a whole is that different pockets are different.
> So, as I’d recommend in general, design for choice.
> (But not unreasonable levels of choice.)
>
> Grüße, Carsten
>
> _______________________________________________
> Emo-dir mailing list
> Emo-dir@ietf.org
> https://www.ietf.org/mailman/listinfo/emo-dir

_______________________________________________
Emo-dir mailing list
Emo-dir@ietf.org
https://www.ietf.org/mailman/listinfo/emo-dir