Re: Call for Consensus to request transition of DAPT to Candidate Recommendation

Hi Atsushi,

You can query GitHub using something like https://github.com/w3c/dapt/pulls?q=is%3Apr+merged%3A%3E2023-04-25+-label%3Aeditorial+-label%3Aci to get the PRs merged since FPWD that are not marked as editorial or as CI - I just went through them all checking that the labels are correct.

Hope that helps,

Nigel


On 18/10/2024, 12:15, "Atsushi Shimono (W3C Team)" <atsushi@w3.org <mailto:atsushi@w3.org>> wrote:


hi Nigel,


Sorry for delay to reply this email, due to several offline appointments and
W3C events recently. (under operation around 1-1.5 weeks behind)




For HR, I was queued to make a list of delta during(?) TPAC, but have not yet
checked due to lack of working time...
Since we failed requesting HRs with dated TR version, but actually did just
with shortname. So I will try do some analysis although I cannot build the exact
list - mostly filed late July 2023, TAG and i18n Sep 2023.


One question, list of changes has IDs to issues, but is there any associated
list of PRs?




On 2024/10/10 23:19, Nigel Megitt wrote:
> TTWG,
>
> As discussed in our face to face meeting at TPAC, we believe that DAPT is ready for a transition to Candidate Recommendation.
>
> We effectively began the process of asking for a working group review during that meeting, on 27^th September, but I did not issue a formal CfC at that time. Nevertheless the reviewing has begun, and some issues and associated pull requests have been raised – thank you Andreas!
>
> So that we have a formal record, this email is a *Call for Consensus to publish DAPT as a Candidate Recommendation*.
>
> As per our Decision Policy <https://www.w3.org/2023/04/timed-text-wg-charter.html#decisions> <https://www.w3.org/2023/04/timed-text-wg-charter.html#decisions&gt;>, if we have no unresolved objections in 10 working days, i.e. by 24^th October, I will declare this to be a /Working Group Decision/.
>
> *A note about /what/ this applies to*
>
> The version for review is the current Working Draft, at https://www.w3.org/TR/2024/WD-dapt-20241010/ <https://www.w3.org/TR/2024/WD-dapt-20241010/> <https://www.w3.org/TR/2024/WD-dapt-20241010/> <https://www.w3.org/TR/2024/WD-dapt-20241010/&gt;> - this incorporates some editorial changes made more recently than our last meeting.
>
> However, there are open pull requests <https://github.com/w3c/dapt/pulls> <https://github.com/w3c/dapt/pulls&gt;> that address issues raised since 27^th September. One of those (#256 <https://github.com/w3c/dapt/pull/256> <https://github.com/w3c/dapt/pull/256&gt;>) is a substantive change.
>
> The final version for which we will request transition will be the current working draft with any approved pull requests merged, so in addition to reviewing the Working Draft, please take a look at the open pull requests and highlight any issues you see with them.
>
> *Timeline*
>
> **
>
> * 10^th October: Chair issues call for consensus (this email)
> * 10-24 October: group to review specification and raise any issues; also review pull requests
> * 24^th October: Chair to assess whether we have consensus, and if so, Editors to merge pull requests and Chair to ask Team to make the transition request
>
> *Horizontal Review updates*
>
> **
>
> As part of the preparation I prepared a substantive changes summary <https://www.w3.org/TR/dapt/substantive-changes-summary.txt> <https://www.w3.org/TR/dapt/substantive-changes-summary.txt&gt;> (since first public working draft). Looking at that list, I find it doubtful that any of the HR groups would want to re-assess DAPT since the review they already did, however it makes sense to point them to the list for information and/or a delta review, should they think it necessary.
>
> *Atsushi*, would you be able to send a pointer to the changes to the HR groups and notify them of our intent to transition to CR when this CfC has closed?
>
> Nigel (as Chair)
>

Received on Monday, 21 October 2024 13:20:01 UTC