Add Compression Standard to db.json

[saschanaz]

Corresponding to #231.

[saschanaz]

Are spec authors expected to manage the Twitter account once it's created, or is it something automated? (I can't even open https://x.com/streamsstandard without signing in, why are we still there? 😅)

[annevk]

@domenic looks like you are in charge of the Workstream. Happy with all these deputy editors?

@saschanaz should you be an editor as well?

[annevk]

@domenic can you set this up?

[saschanaz]

should you be an editor as well?

I'm only helping this on behalf of @ricea and not really an editor. I'm open to the position though 😄

[domenic]

@domenic looks like you are in charge of the Workstream. Happy with all these deputy editors?

Yes, seems good!

[ricea]

It might be good to replace Canon Mukai with a different editor as she doesn't work on web standards nowadays. I will ask her.

[domenic]

Yeah, we seem to use the "authors" field as a mix of historical authors and current deputy editors. (The Streams Standard, HTML Standard, and URL Pattern Standards notably have some historical authors still listed.)

[ricea]

So maybe Canon should remain as an author but not as an editor? She said she was happy to be moved to "former editors".

[annevk]

I'm not sure we're consistent about that. E.g., I'm not listed for Fullscreen. I think I'd prefer it being a reflection of current editors as otherwise it would get quite unwieldy over a long period of time.

[annevk]

I've moved Canon to the Acknowledgments section of the standard. The Twitter account isn't live yet, but since the standard is I'm going to merge this.

Thanks everyone!