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

Decide on a process for editing this specification #1

Closed
RubenVerborgh opened this issue May 14, 2019 · 7 comments
Closed

Decide on a process for editing this specification #1

RubenVerborgh opened this issue May 14, 2019 · 7 comments

Comments

@RubenVerborgh
Copy link
Contributor

No description provided.

@Mitzi-Laszlo
Copy link
Contributor

@Mitzi-Laszlo
Copy link
Contributor

Mitzi-Laszlo commented May 15, 2019

Check out solid-contrib/information#138 and make suggestions to improve the decision making process

@RubenVerborgh
Copy link
Contributor Author

RubenVerborgh commented May 15, 2019

Suggestion from my side: I would use https://github.com/solid/information/blob/master/decision-making-processes.md to make a decision on what process to use for spec writing, but not adopt that process directly as the spec writing process itself.

From experience, having 2–3 dedicated editors on a spec is a good mechanism. (To be decided then: PRs, authors, etc.)

@Mitzi-Laszlo
Copy link
Contributor

Mitzi-Laszlo commented May 17, 2019

Ok, sounds good although needs more detail. For example, how are the editors appointed? What are their responsibilities? How would the editors resolve differences of opinion that inevitably arise between them?

The reason I'm asking these questions is that the editors need respected authority to be able to carry out their work. It needs to be clear what that work is and where and on what external individuals can comment and how to expect those comments to be handled.

@RubenVerborgh
Copy link
Contributor Author

For example, how are the editors appointed?

Some people step up, usually it's a mutual agreement and a group forms. It's rare that elections have to be held 🙂

What are their responsibilities?

Delivering a clear, consistent, readable, implementable spec.

How would the editors resolve differences of opinion that inevitably arise between them?

That is rarer than you might think. Editors generally just facilitate the translation of a consensus into a text.

When there would be difference, we discuss with the group, and a common solution is derived.

The reason I'm asking these questions is that the editors need respected authority to be able to carry out their work.

There's less authority than we might assume. They are not deciders; they are people who write down what all/most of us want. The community needs to trust them as skilled and dedicated writers, not necessarily as leaders.

It needs to be clear what that work is and where and on what external individuals can comment and how to expect those comments to be handled.

Editors are the ones moving input to the text; but the inputs themselves can be given by anyone, and anyone can comment on them. Editors usually don't decide on yes or no; they decide when a topic has been sufficiently discussed and then move it to the text. When there is insufficient discussion, they moderate.

To summarize: editors facilitate technical discussion and translate the resulting consensus into a text, that's it.

@Mitzi-Laszlo
Copy link
Contributor

Here is a proposal for the creation of the Solid spec v1 which would need to be approved by the Solid Leader.

@RubenVerborgh
Copy link
Contributor Author

Deferred to solid/process#6 and its follow-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants