- Date: //date
- Time: 9:00 ET
- Location: nraozoom04
- Sprint Calendar
Agenda:
- Section 3.5.1 point 9 of System Description and Section 4 point 4 – implementation consequences, so is this still desired (Mark F)
- tar file containing all of the individualProposalPDF files
Save and Resubmit buttons"if you submit a proposal, make some changes (title, abstract, etc.) on the author copy, and without hitting save first you click Re-submit, the changes you just made aren't saved. What behavior would be ideal here? If you click re-submit, you auto-save before resubmitting, you have to click save first before re-submit is enabled, etc.?"
- Name of the Proposal Processes - OSR, PPR?
- Parking Lot Items
Proposal validation at submission and at will requirements.
Title, Allocation Request, Capability Request, etc.
Logging source of proposal edits?
Grace period - proposals go to In Review state at deadline + grace period.
When does the review get normalized?
What are the review phases?
What is the gate for each phase? Manual or automatic?
Does the software need to keep track of what has been vetted?
Agree on semantics for consensus and individual review uploads.
What is the list of tasks TTA Group Members can do? (Solution to TTA Group Member can do everything problem.)
Notification details, subsystem doc or system description?
Collect notification references in system description and use them to form a table.
- RID watching
Jira server DMS JIRA jqlQuery filter=14704 serverId eb2e750b-a83a-387e-8345-36eee8a98f01
Open Actions:
Task report | ||
---|---|---|
|