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

May need to rethink organization of Requirements section, now that we have more content #111

Open
SpencerDawkins opened this issue Sep 5, 2023 · 0 comments
Assignees
Labels
AfterNextMeeting Not ready to propose text until after next meeting

Comments

@SpencerDawkins
Copy link
Collaborator

SpencerDawkins commented Sep 5, 2023

One option would be requirements at a broad level that affect the deployability of MOQ systems, and rely on functions of MOQ components that would be defined in detail in chartered deliverables. So, for example, something that a relay does, that relies on something in a catalog.

@SpencerDawkins SpencerDawkins added the Deferred for now We need other issues to be resolved first label Sep 28, 2023
@SpencerDawkins SpencerDawkins added NextInterim Target PR text for next interim and removed Deferred for now We need other issues to be resolved first labels Nov 20, 2023
@SpencerDawkins SpencerDawkins self-assigned this Nov 20, 2023
@SpencerDawkins SpencerDawkins added AfterNextMeeting Not ready to propose text until after next meeting and removed NextInterim Target PR text for next interim labels Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AfterNextMeeting Not ready to propose text until after next meeting
Projects
None yet
Development

No branches or pull requests

1 participant