Should appeal request be shared with the Membership?
https://www.w3.org/2021/Process-20211102/#ACAppeal only requires that
An Advisory Committee representative initiates an appeal by sending a request to the Team.
But since that request needs to be shared with the Membership during the process, it would be make more sense if that appeal request be sent to the team but in a member-visible space.
Makes sense to me. I recently filed such an appeal, and would have happily done so in a Member-visible way if the instructions had said to.
I think we should make it clear that the person filing the appeal, if willing, is allowed and encouraged to share their appeal request and its reasoning with the AC. Need to draft a pull request to do that, feel free to beat me to it.
@dontcallmedom I've made a pull request for this, let us know if this is what you meant: #676
The Revising W3C Process CG just discussed Member-visible AC Appeals, and agreed to the following:
-
RESOLVED: Merge #676
The full IRC log of that discussion
<fantasai> Subtopic: Member-visible AC Appeals<fantasai> github: https://github.com/w3c/w3process/issues/603
<fantasai> -> https://github.com/w3c/w3process/pull/676
<fantasai> florian: We wanted to add language to encourage members to share their appeal request with membership, not just the Team
<fantasai> ... agreed on concept last time, but were blocked on specific phrasing
<fantasai> ... because the process does not explicitly refer to AC Forum, it is abstract about how you are supposed to contact the AC
<fantasai> ... so wanted to rephrase to make it clearer how to contact this
<fantasai> ... solved this by having plh write a /Guide article, which gives an email template and says where to send it
<plh> --> https://www.w3.org/Guide/process/ac-appeal Appealing a W3C Decision
<fantasai> ... so now the Process itself, we can just link to the Guide
<cwilso> +1 to merging
<fantasai> ... and just say who you're supposed to contact, and point to /Guide for how
<fantasai> plh: Objections to merge?
<fantasai> RESOLVED: Merge #676