Note: You can propose changes using the forum below.
Under the requirements tab there should be a link that reads: "Request design work".Change History:
This link should lead to a special subproject creation page for work that is intended to refine or add to the parent project's requirements (as opposed to coding up a requirement that was already specified in the parent project). For example, mockups, UML diagrams, content flow diagrams and API specs, etc. all fall under such a subproject (the subproject page should mention this at the top of the page).
If the subproject creator is not the parent PL (project lead), then the creator should be given the choice of whether to be the PL of the new subproject.
Once the subproject is created and a submission is made and accepted, a requirements change request must be automatically posted to the parent project's requirements forum. The change request should consist of a new paragraph added to the end of the requirements, requiring that the design element be adhered to. The subproject PL, when accepting the submission should be given the opportunity to edit the wording of the new paragraph.
As with any requirements change request, the parent project's PL will then decide to accept it or reject it. (As an added convenience, if both the parent and subproject have the same PL, then the acceptance should be automatic.)