Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add areas of focus to editors.md #81

Closed
wants to merge 2 commits into from
Closed

Conversation

justinwb
Copy link
Member

This pull request is meant to address the subject of some debate in #36. Since we are still crystalizing how we identify and handle substantive/non-substantive changes per #57, I'm following the process being proposed for non-substantive changes, and issuing this pull for light editorial review. There has been general agreement that its contents are not considered substantive changes.

Note that if this is merged, any existing editor applications will also need to be updated to include proposed Areas of Focus.

@Mitzi-Laszlo Mitzi-Laszlo added the process proposal Process proposal to be reviewed by Solid Director label Jul 25, 2019
@RubenVerborgh
Copy link
Contributor

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).

@kjetilk
Copy link
Member

kjetilk commented Jul 31, 2019

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.

@justinwb
Copy link
Member Author

justinwb commented Aug 3, 2019

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.

@justinwb justinwb closed this Aug 3, 2019
@justinwb justinwb deleted the editor-areas-of-focus branch August 3, 2019 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
process proposal Process proposal to be reviewed by Solid Director
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants