Thanks, @justinwb.

No objection to the PR as such, but I think the entire notion of Editors has gone off track (#78 (comment)). It seems to have become a Title with a Privilege, whereas it should simply answer the question who is responsible for ensuring that a specific document is up to the right level. I might have created that confusion myself through the open wording of solid/specification#2, but what I really mean is solid/specification#2 (comment) and solid/specification#2 (comment). So editor with a lowercase "e", really.

As far as I'm concerned, people are just editors of a specific document, so people's editorial duties should be scoped to the documents they are the editor of. For instance, we could just add them as editors to individual documents of https://github.com/solid/specification/ (like here https://github.com/solid/specification/blob/0036fc08145add6007f7767722193c5b34b3e1cc/main/index.bs#L10).

As it currently stands, I don't see a strong reason/motivation for myself to be on editors.md; I don't think it serves a purpose. My editorship should come from concrete actions such as solid/specification#13, and could eventually be reflected on top of that document. I'm not in need of other privileges or duties beyond being able to contribute to that one document (or perhaps other relevant ones in the future, which I can decide on a per-document basis).

Of course, that's just my opinion, so take it with a grain of salt, but at the same time please consider it as a signal coming from the bottom up on how we'd want to work (since the process should serve us, not the other way round).

I'm 👎 on this, for reasons explained in #36. I do think that editors.md has a clear purpose, explained there, but that areas of focus is given by the panels, not the editorial board.

This pull request has been succeeded by #95. The changes included in this pull are no longer relevant, so there was no need to merge. Closing this pull request and deleting the branch.