[Docs] Separate elections folders and accelerate reviews for simpler staff edits

[justaugustus]

Some recent PRs gave me a cleanup idea: #517, #518, #520

Elections subdirectories

There is a variety of content regarding elections that does not change frequently, but the process, forms used, etc. may change yearly, so we should consider having:

• slow-moving content in a top-level folder
• subdirectories that are specific to the election year

This also ensures anyone can reflect on election content at any point in time without having to scan through git commits.

Here's an example of how the Kubernetes project organizing this:

• https://github.com/kubernetes/community/tree/master/elections
• https://github.com/kubernetes/community/tree/master/elections/steering

Separate elections CODEOWNERS

There are several simpler edits that may happen at the staff level and do not necessarily require TAC review (see the aforementioned PRs). If we add some additional CODEOWNERS entries, we can have staff update that content without falling into the TAC review flow.

---

@ossf/tac @kj-powell — what do you think?

Happy to help with this reorganization if people like the idea.

[marcelamelara]

Thanks @justaugustus ! I'm all for changes that make the organization of this repo clearer and more manageable, so I quite like this proposal.

[justaugustus]

Thanks Marcela! 🚀
I spoke to @kj-powell on Tuesday and she's going to think through how she'd like to organize things and get back to me to help with implementation.

[lehors]

Thanks Marcela! 🚀 I spoke to @kj-powell on Tuesday and she's going to think through how she'd like to organize things and get back to me to help with implementation.

Sounds good to me. Thanks.