- 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.
- Dana will add an appendix to the system description to capture this information.
Logging source of proposal edits?
- The answer to this is no (pending response from Tony).
Grace period - proposals go to In Review state at deadline + grace period.
When does the review get normalized?
- This happens once the consensus review for a panel is certified.
- One button that certifies the consensus is complete, either the TTA Member or Chair can hit the button.
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.
- This is a todo
What is the list of tasks TTA Group Members can do? (Solution to TTA Group Member can do everything problem.)
- Tracked in STT-907
Notification details, subsystem doc or system description?
Collect notification references in system description and use them to form a table.
- Dana to add a section to the system description to capture the notification in a singe area.
RID
watchingProgress:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Open Actions:
| Task report | ||
|---|---|---|
|