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

Merge sandhawke/spec-labels-min #29

Closed
jyasskin opened this issue May 10, 2017 · 5 comments
Closed

Merge sandhawke/spec-labels-min #29

jyasskin opened this issue May 10, 2017 · 5 comments
Assignees

Comments

@jyasskin
Copy link
Member

Per #27 (comment), we should try to merge @sandhawke's proposed spec labels into this repository. I'm in favor of rewriting them to lowercase-with-dashes per #25 in the process.

@tripu
Copy link
Member

tripu commented Aug 29, 2017

Do @jyasskin or @sandhawke want to give it a go at merging their respective suggested label and colour sets, so that we can close #25, #27 and this one?

@plehegar plehegar self-assigned this Oct 5, 2017
@plehegar
Copy link
Member

plehegar commented Oct 6, 2017

@tmichel07 , can you send a proposal that merges what ttml is doing and what Sandro did?

@tmichel07
Copy link
Contributor

The Timed Text WG has also elaborated labels to track Wide Review comments for TTML2 spec
Here is our proposal for Wide Review labels in github (Proposed Github labels are written into square brakets)

1- Processing comment within the TTWG
1.1- Comment received, not yet processed by the TTWG [WR-open]
1.2- Discussed but pending TTWG resolution, [WR-pending]
1.3- Done - TTWG resolution, (approved by WG) [WR-resolved]
1.4- Done - TTWG resolution and spec update [WR-spec-updated]
1.5- Done with Partial TTWG resolution (partially approved by WG), [WR-resolved-partial]
1.6- Done with Partial TTWG resolution and spec update [WR-spec-updated-partial]
1.7- Done but comment Rejected [WR-rejected]

For each comment, the WG also fill a"type" :
a-typo, b-editorial, c-substantive, d-general, e-undefined.

Once the TTWG has processed all comments, the next steps are to get approval from the commenter
2.1- Response drafted by WG [WR-response-drafted]
2.2- Response send to commenter [WR-response-sent]
2.3- Response agreed by commenter [WR-commenter-agreed]
2.4- Response rejected by commenter (need more discussion - back to step 1.5 or closing) [WR-commenter-rejected]
2.6- Response partially agreed by commenter (need more discussion - back to step 1.5 or closing) [WR-commenter-agreed-partial]
2.7- No Response received from commenter within the stated period [WR-commenter-noresponse]

For more information see ou wiki page
https://www.w3.org/wiki/TimedText/TTML2_Wide_Review

@tripu
Copy link
Member

tripu commented Nov 23, 2017

I personally find these labels used by the TT WG too {complex, specific, verbose}.

Given that we have by now a large set of well-defined labels, I'd stick with those and close this issue.

@plehegar
Copy link
Member

The current set is a good start. Let's see later if we need to extend them.

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

No branches or pull requests

4 participants