CIP-0381 | post-merge update top level README

[rphair]

post merge #220

(BTW this also shows some removal of extraneous white space in the diff)

[rphair]

@KtorZ @SebastienGllmt - what procedure did you guys work out for editing the top level table, so as not to require an additional PR every time a CIP PR is merged? I can't remember or perhaps never noticed in the first place; though I do remember entries in this table being updated in groups... 🧐

[KtorZ]

what procedure did you guys work out for editing the top level table

I do grep with my eyes. It's cumbersome but relatively effective 😬 ... I typically do this before every bi-weekly to keep the top-level README updated. That usually takes me about 2-3 min and thus so far, I haven't felt the urge to automate this.

[rphair]

@KtorZ @crptmppt @mangelsjover @SebastienGllmt what do you think of this process: immediately before merging each CIP, we make a quick edit to the top level README in the author's branch to update the table entry?

As we talked about here (#216 (comment)) this is something we generally have to be diplomatic about, but shouldn't be a problem in this case because we're not changing the CIP author's documents.

This way, the top level table gets updated immediately, and doesn't get out of date (so doesn't need to be date-stamped) or need visual update passes periodically.

Also there was a merge conflict here yesterday during the meeting from something else updating a nearby entry in the table & so I lost my opportunity to ask someone to review this while we were all together... this would be less likely to happen if the top level README updates were always done immediately.

In any case can someone please approve this now so it can be merged? 🤓

[KtorZ]

@rphair I'll include this one as part of a bigger update.