rudimusmaximus
Describe Phase II deliverables and how we will publish them
add a working list in table view using md
- [ ] Finalize list of deliverables to update or add in Phase II
- [ ] For each, formalize where they are stored and how included in repository
- [ ] Draft Template shells for each and inlcude an issue for each with links to the files
- Each deliverable will have it's own issue to track completion
- It will be stored on RCM Drive Space as a G Suite doc
- Finished versions will be 'snapshoted as pdf' and also linked (and versioned inside the doc/sheet/slide etc)
- Also, pdfs will be posted to project page as deliverables
- Videos where applicable will be posted in drive with link embed to project site
- The documents will continue as living documents in Phase II and ongoing
here is an attempt at creating a table in MD for tracking deliverables:
| Deliverable | Issue Number | Description | TOC | Completed (y/n) | Snapshot PDF (y/n) |
|---|---|---|---|---|---|
see this helpful MD generator for tables: https://www.tablesgenerator.com/markdown_tables
| Deliverable | Issue Number | Due Date | Description | TOC | Completed (y/n) | Snapshot PDF (y/n) |
|---|---|---|---|---|---|---|
| Template for Q&A Question | 35 | 5/12/2018 | Provides template format for questions, filed as issues. | https://github.com/rudimusmaximus/DevFlow/issues/35 | Y | N |
| Template for a DevFlow Issue that's code related | 43 | 5/14/2018 | Provides default issue template to be used for code issues. | https://github.com/rudimusmaximus/DevFlow/issues/43 | Y | N |
That works. change Description to purpose and review our private doc here to brainstorm what we need; i took a pass at highlighting row 1 and column E for candidates. we can work out of that and as we flush out the details move them to the table you have here and create issues with their design info to include what's on our private inventory. If you have time to review the sheet items that were highlighted; prob need to add field for snapshot links and section for such on those items that link to drive files. Two heads better than one. Thanks. @RobGoelz
mabye change your TOC to Link (repo if issue only, repo and drive if also); we can drop issue and include it with hot links in Link(s) where we could also include "PDF Snapshot yy.mm.dd"
If tracking due date, add [delivered date]. not convinced we need as we might add an issue for master schedule? as a table like this.
How's this?
- We can merge a status and completion indicator in the one Due Date column.
- Status in italics can be
Not Started,Work In Progress,On Hold,Canceled; Completed items get a date also in italics. - Link(s) are to Issues, Deliverable on drive, and PDF Snapshots.
| Deliverable Short Title | Due Date [Delivered or Status] | Purpose | Comments | Link(s) |
|---|---|---|---|---|
| Template for Q&A Question | 5/12/2018 [5/9/2018] | Provides template format for questions, filed as issues. | Issue only | Issue 35, No PDF 2018.05.21 |
| Template for a DevFlow Issue that's code related | 5/14/2018 [completed add date] | Provides default issue template to be used for code issues created in a Glo board. | Issue only | Issue 43, No PDF 2018.05.21 |
| Example only | 5/21/2018 [5/21/2018] | Example | Issue, Lucid Chart Diagram, Keynote Presentation, | Issue tbd , Deliverable, PDF 2018.mm.dd |
| Deliverables List | mm/dd/yyyy [not started] | List the deliverables for phase II | Issue Only | Issue 33 |
| tbd | mm/dd/yyyy [not started] | tbd | Issue tbd , Deliverable, PDF 2018.mm.dd | |
| tbd | mm/dd/yyyy [not started] | tbd | Issue tbd , Deliverable, PDF 2018.mm.dd | |
| tbd | mm/dd/yyyy [not started] | tbd | Issue tbd , Deliverable, PDF 2018.mm.dd | |
| tbd | mm/dd/yyyy [not started] | tbd | Issue tbd , Deliverable, PDF 2018.mm.dd | |
| tbd | mm/dd/yyyy [not started] | tbd | Issue tbd , Deliverable, PDF 2018.mm.dd |
not sure if multiple links in a single cell is an issue, but here's this for comment. see you wed.
- [ ] let's update this to the q&a format, add link to new version of sheet just for this purpose.