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

Switch [spec] authors to "editors" in the Purpose section. #142

Merged
merged 2 commits into from
Jan 6, 2025

Conversation

jyasskin
Copy link
Contributor

This is meant to fix #141. Elsewhere we use "authors" to refer to website authors, but that doesn't fit between spec developers and (presumably) spec reviewers.

Another option might be to remove this list item entirely: editors are either meant to apply the decisions of their working groups without needing to check the EWP, or they're acting as spec developers.

cc/ @lianqi

@jyasskin jyasskin added the editorial editorial suggestion label Dec 29, 2024
Copy link
Member

@csarven csarven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to offer two suggestions.

I believe the EWP Statement should be intended for either:

  • any member of the standards development community, or
  • any member of the W3C community.

I prefer the broader scope of the first option.

I believe the broader perspective to applying the EWP to practice beyond direct contributions to charters, specifications, or similar documents is more inclusive. It should cover anyone working on a technical or community report within W3C [1]. It also indirectly supports cases where incubation occurs outside the W3C space, making the Statement available to everyone, and so fostering a shared vision for improving the web.

[1] I've created a #143 to clarify that the Statement applies to all W3C technical or community reports, updates to those reports, and new charters.

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
@jyasskin
Copy link
Contributor Author

+1 to Sarven's comment in general, but I think that might take this beyond an editorial change, which means we couldn't fix it in the Statement without AC review. I'd like to make the translation-aiding editorial corrections first, and then start on the next version.

@torgo
Copy link
Member

torgo commented Jan 2, 2025

I think the point of using "authors, reviewers" etc.. is to be clear about who we are talking about and what they do. This helps the document be more accessible to the wider community. So I would be reluctant to change it to "any member of the w3c community" or "Any member of the standards development community" as this wouldn't be as clear.

Copy link
Member

@torgo torgo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed in today's breakout and agreed to keep the changes as authors -> editors and take up the broader changes for a different PR.

index.html Outdated Show resolved Hide resolved
Copy link
Member

@hadleybeeman hadleybeeman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed in meeting

@jyasskin jyasskin merged commit 70b8ec4 into w3ctag:gh-pages Jan 6, 2025
@jyasskin jyasskin deleted the clarify-authors branch January 6, 2025 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda+ editorial editorial suggestion
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Please help to clarify "authors" in 1.1
4 participants