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

Why can AC comments on CR be ignored? #339

Closed
fantasai opened this issue Nov 4, 2019 · 10 comments
Closed

Why can AC comments on CR be ignored? #339

fantasai opened this issue Nov 4, 2019 · 10 comments
Assignees
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion
Milestone

Comments

@fantasai
Copy link
Collaborator

fantasai commented Nov 4, 2019

must show that all issues raised during the Candidate Recommendation review period other than by Advisory Committee representatives acting in their formal AC representative role have been formally addressed,

Why are the AC rep's comments during the CR review period not required to be formally addressed alongside everyone else's comments?

@dwsinger
Copy link
Contributor

dwsinger commented Nov 6, 2019

I think the sense might (?) have been that the requirement to address AC comments is stated elsewhere. Maybe. This appeared in the major re-write of 2014, and does not seem to be in 2005

[2005] https://www.w3.org/2005/10/Process-20051014/
[2014] https://www.w3.org/2014/Process-20140801/

@chaals ?

@chaals
Copy link
Contributor

chaals commented Feb 17, 2020

Comments based on the review role of AC reps are addressed by the Director (and in principle should not be technical comments since those should be made by someone acting in the role a a Working Group participant, or a reviewer). So the Working Group may choose to ignore them, since they will be reviewed subsequently.

This was inherited from section 7.3 in the 2005 process - https://www.w3.org/2005/10/Process-20051014/tr.html#doc-reviews

There is a risk that AC reps promise a formal objection at PR if some technical objection is not resolved the way they want, and that the Working Group is cowed into making a bad decision instead of passing it to the Director to deal with the question. There is a risk that the Working Group can be delayed for a long time dealing with an issue that properly belongs to the Director's review, instead of completing their technical work.

I expect groups will talk to the Director about how to handle such issues if they arise and I have seen it happen in practice.

I think the exception is vaguely useful (if the Director tells a group that he considers a given AC objection unlikely to change his mind, it's probably better for them to focus on dealing with technical issues than getting sidetracked), but I also think we could survive without it.

@dwsinger
Copy link
Contributor

so, do we need a parenthesis in the quoted statement? like this?

must show that all issues raised during the Candidate Recommendation review period other than by Advisory Committee representatives acting in their formal AC representative role

(which are addressed by the Director, possibly in consultation with the working group)

have been formally addressed,

@chaals
Copy link
Contributor

chaals commented Feb 18, 2020

I don't think we need anything. Given that "we decided against acting on this" is one way for the Working Group to address an issue, and if the commenter is not satisfied that information has to get to the Director, I don't think we need the exception clause either, although my very slight preference is to keep it.

@frivoal frivoal added this to the Deferred milestone Mar 11, 2020
@frivoal
Copy link
Collaborator

frivoal commented Mar 11, 2020

I agree with @chaals we don't strictly need it, and since people these days are looking for ways to make the process shorter / simpler, my inclination would be to drop the exception.

@jeffjaffe
Copy link

Since there is some controversy here (i.e. Chaals would like to keep the exception) and we should only make pure editorial changes at this point, I would recommend we defer to P2021.

@frivoal
Copy link
Collaborator

frivoal commented Mar 11, 2020

I would recommend we defer to P2021.

Of course. I commented on this issue as I was triaging things and ran into it, but I consider it already deferred to P2021 (or later) based on the last process CG call.

@chaals
Copy link
Contributor

chaals commented Mar 11, 2020

Rather than postpone I think we could resolve this. I don't see controversy, I see mildly divergent preferences - i.e. no very strong objections being generated to whatever we decide. Which makes deciding more valuable.

@dwsinger
Copy link
Contributor

we suggest deleting "other than by Advisory Committee representatives acting in their formal AC representative role" as we like earlier reports rather than later

frivoal added a commit to frivoal/w3process that referenced this issue Aug 12, 2021
Comments made during the CR phase, by AC reps acting in their formal capacity,
could until now be ignored by the WG, since they could be caught by the
Director at a later stage during the transition request.

Assuming either an exhaustive disposition of comments, or that the AC
Rep remembers to file a Formal Objection, such comments would indeed not be lost.

However, it is generally preferable to deal with issues early rather
than late. This commit makes it so that AC Rep comments deserve a WG
response as much as anyone else's.

See w3c#339
frivoal added a commit that referenced this issue Sep 22, 2021
Comments made during the CR phase, by AC reps acting in their formal capacity,
could until now be ignored by the WG, since they could be caught by the
Director at a later stage during the transition request.

Assuming either an exhaustive disposition of comments, or that the AC
Rep remembers to file a Formal Objection, such comments would indeed not be lost.

However, it is generally preferable to deal with issues early rather
than late. This commit makes it so that AC Rep comments deserve a WG
response as much as anyone else's.

See #339
@frivoal frivoal modified the milestones: Deferred, Process 2022 Sep 22, 2021
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed P2022 Proposed to address labels Sep 22, 2021
@frivoal
Copy link
Collaborator

frivoal commented Sep 22, 2021

Solved by #563

@frivoal frivoal closed this as completed Sep 22, 2021
@frivoal frivoal added Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice and removed Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice labels Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion
Projects
None yet
Development

No branches or pull requests

5 participants