Simplify the section Member Submissions#936
Conversation
Co-authored-by: fantasai <[email protected]>
| One of the [=Submitters=], | ||
| copying the [=Advisory Committee representatives=] of the other [=Submitters=] (if any), | ||
| sends a request to the Team to acknowledge the Submission request. | ||
| The [=Team=] and [=Submitter=](s) communicate to ensure that the [=Member Submission=] is complete. |
There was a problem hiding this comment.
This might call for an edit of the dfn to add the submitter(s) synonym.
| The [=Team=] and [=Submitter=](s) communicate to ensure that the [=Member Submission=] is complete. | |
| The [=Team=] and [=Submitter(s)=] communicate to ensure that the [=Member Submission=] is complete. |
|
|
||
| <ul> | ||
| <li> | ||
| The [=Submitter=](s) |
There was a problem hiding this comment.
I guess this might also call for a document-wide search-and-replace. (Reason is that [=Submitter=](s) renders poorly; [=Submitter(s)=] renders better.)
| The [=Submitter=](s) | |
| The [=Submitter(s)=] |
| <li>If <dfn>rejected</dfn>, | ||
| <li> | ||
| If <dfn>rejected</dfn>, | ||
| the [=Team=] <em class=rfc2119>must</em> inform the [=Advisory Committee representative=](s) of the [=Submitter=](s), |
There was a problem hiding this comment.
[=Advisory Committee representative(s)=] synonym also needed.
| the [=Team=] <em class=rfc2119>must</em> inform the [=Advisory Committee representative=](s) of the [=Submitter=](s), | |
| the [=Team=] <em class=rfc2119>must</em> inform the [=Advisory Committee representative(s)=] of the [=Submitter(s)=], |
There was a problem hiding this comment.
Filed speced/bikeshed#2948. If/when bikeshed addresses that, I'm happy to go along with your suggestion, but until then, that seems like too much work for not enough benefit.
| and <em class=rfc2119>must</em> provide rationale if requested by the [=Submitter=](s). | ||
| The [=Submitter=](s) <em class=rfc2119>may</em> initiate a [=Submission Appeal=]. |
There was a problem hiding this comment.
| and <em class=rfc2119>must</em> provide rationale if requested by the [=Submitter=](s). | |
| The [=Submitter=](s) <em class=rfc2119>may</em> initiate a [=Submission Appeal=]. | |
| and <em class=rfc2119>must</em> provide rationale if requested by the [=Submitter(s)=]. | |
| The [=Submitter(s)=] <em class=rfc2119>may</em> initiate a [=Submission Appeal=]. |
Co-authored-by: Ted Thibodeau Jr <[email protected]>
|
I'm fine to merge this PR without my plural tweaks. A new issue on process or bikeshed or wherever makes sense to you would be welcomed. |
Cuts down the Process part of Member Submissions to the bare minimum, with the expectation that all the detailed requirements and guidance will be shifted to /Guide.
Addresses #648, #421
Preview | Diff