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

Any charter can be subject to "extended review" #74

Closed
wants to merge 2 commits into from

Conversation

chaals
Copy link
Contributor

@chaals chaals commented Aug 30, 2017

Fix #33
Apply to all charters, not just those that continue existing work.

Fix #33
Apply to all charters, not just those that continue existing work.
@dwsinger
Copy link
Contributor

I can't tell but this PR doesn't seem to contain the text proposed by Virginia and accepted by the Process CG. Can we simply add that text? (Yes, we'll flag it for discussion in TPAC)

@chaals
Copy link
Contributor Author

chaals commented Aug 30, 2017

Sure, just revert #72 (there's a button there to do so), ignore this, and make a different PR.

As editor I didn't copy the text directly because:

  1. It needed to change to account for the comment being in AC review rather than email
  2. It takes 2 paragraphs to say the same thing as this PR added to Fix #33 allow for extended review #72, repeating the bulky phrase in each of them
  3. It is the general style in the Process to set a minimum time after trigger A for event B, rather than the "between (a) something and (b) something else" style used in Virginia's text.

I assert that my proposed text has the same effect, of requiring the Director to ensure a minimum 60-day gap between charter review starting and call for participation, any time an AC rep requests that as part of a charter review. If not, it does need fixing...

@vfournier17
Copy link

I can't seem to locate Charles' proposed text. Would you please post again? Also, the extended 60-day review is intended to cover both situations; i.e., new charters and rechartering charters (for example) adding new deliverables. The reason for the proposal is that some members may look at a charter that is in one of their technology sweet spots and say, "Oh, no - this patent review is going to take more than 30 days." This way, the review period could be extended when a member needs more time for a patent review (for any new deliverables), but would not be imposed in every case.

@vfournier17
Copy link

This is the most recent language I can parse together:
"With respect to any new or substantively modified Working Group charter, any Advisory Committee representative may request that there be at least 60 days between (a) the Call for Review, and (b) the Call for Participation for such a group (an “Extended Review Period”).

An Extended Review Period request must be submitted as part of a Member's comments submitted during the Call for Review. Upon receipt of such request, the Director must ensure that there are 60 days between the Call for Review and the Call for Participation. The request for an Extended Review Period must be made prior to the end of the Call for Review period."

@chaals
Copy link
Contributor Author

chaals commented Sep 21, 2017

overtaken by #93 so closing

@chaals chaals closed this Sep 21, 2017
@frivoal frivoal deleted the extend-all-charter-reviews-33 branch November 16, 2018 05:45
@frivoal frivoal added Closed: Rejected DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) labels Dec 9, 2018
@frivoal frivoal added this to the Process 2018 milestone Feb 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Rejected DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants