Clarify and simplify the sections regarding publication and process 2021
@frivoal がすでに取り組んでいます。
2023年9月27日 から。
評価
この issue はまだ評価されていません。
説明
I am aware that previous issues have been opened regarding this (#589, #590), but I want to further expand and discuss the possibility of completely revising this section for readability.
Background: EPUB 3 WG is planning to vote this week to move the specification to PR. As part of this, we need to make the decision as to whether we want to make EPUB3 a "living standard" in the common parlance. To support my WG, I sent an email explaining what the difference is, but to make sure I was being accurate, I decided to do a close read of most of section 6, but specifically 6.3.
I cannot emphasize this enough, I am a native english speaker with a degree in English Literature and 5+ years of experience in standards including as an editor: this section is almost completely impossible to understand. I say almost because I was able to write my summary for the working group, as to whether it's helped anyone in making a decision, I have no idea.
I am not saying this to criticize anyone, but I do think we need to look at the following issues within the text and revise according. I am willing to help with this (I joined process CG so I'm on the hook).
- Address the terminology issues raised in issue #590 - Manu provided an excellent simplification of the terminology to start from, and I had the same experience with confusion over the terminology.
- Clarify that there are 2 paths a new specification can take, and give proper naming to those (none of this "accepts new features" terminology, it's not a name).
- Create new visualizations for both pathways
- Clarify the types of changes (the levels system is actually quite clear, I think it just needs more prominence).
- Clarify revision process for older specifications that are not on the new process.
- Remove the circular references, many sections link back to each other and give the illusion of clarifying while somehow making things more confusing (related to #590).
Chairs and editors for new specifications need to be able to explain this to their WGs and implement these changes, right now it's basically impossible.
- 主要言語
- HTML
- スター
- 263
- フォーク
- 195
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
w3c/process のほかの issue
-
Type: Editorial improvements
難易度 1/5 1〜3時間 初心者へのやさしさ 76/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
-
Record meetingsオープン
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
-
Staffing commitments in charters対応中かも @jyasskin が 12 日前に担当しました。 オープン
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
-
Agenda+
難易度 5/5 1週間以上 初心者へのやさしさ 35/100