Skip to content

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

@SpencerDawkins

Description

@SpencerDawkins

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.

Metadata

Metadata

Labels

AfterNextMeetingNot ready to propose text until after next meeting

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions