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

Requirements change process when do we need AD consultation? #46

Closed
mwullink opened this issue Nov 23, 2024 · 2 comments
Closed

Requirements change process when do we need AD consultation? #46

mwullink opened this issue Nov 23, 2024 · 2 comments

Comments

@mwullink
Copy link
Contributor

Do we need to involve the AD for each (small) change of the requirements when there is wg consensus about the proposed change?

I'm concerned about having a too elaborate process for potential many small requirement changes that may come up during the design process.

Maybe change the charter text to say that involving the AD is optional for small changes and that it is up to the chairs to determine if a larger requires consultation with the AD?

proposed new txt:

"Once established, these requirements may be changed through explicit working group consensus and, when the chairs determine it to be a major change, in consultation with the group’s responsible Area Director."

@anewton1998
Copy link
Collaborator

I agree. Grammar and spelling mistakes and things of that magnitude should not require the AD. I'll incorporate this into the current PR>

@anewton1998
Copy link
Collaborator

Addressed in #45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants