...
Open Journal Systems sprints, https://docs.pkp.sfu.ca/ : Specific documentation interest group; monthly planning meeting to pick tasks; tied to new releases; biweekly writing sprints on Fridays for 1.5 hours; fo larger participant groups, there is a document leader per document; convert docs to markdown to load to GitHub; wouldn't need to convert to markdown for Confluence; use a spreadsheet to keep track of tasks with columns for participants and status; break document into chapters per participant; later have a person to read over whole thing; first writing is in Google Docs. Then move them to markdown. Google Docs is used for drafts, changes are merged in GitHub. Google Docs is good for collaboration, sharing, comments, etc.
Another possibility is to use Confluence Decisions, https://www.atlassian.com/blog/archives/introducing-confluence-decisions-decide-faster-record-forever, (pre-formatted pages, not a database), less formal than JIRA.
Documentation outline - DRAFT - DSpace 7 documentation task list
Could use Google Docs for spreadsheet of tasks plus Google Docs for the writing;
Could use Confluence for documentation writing, https://wiki.lyrasis.org/x/BAaiCw; also it has comments; could be less work than also using Google Docs for drafts and then copying to Confluence.
A spreadsheet would be simpler than using the Confluence mgmt. syste.
DSpace 6 Test Plan, https://docs.google.com/spreadsheets/d/13kc3DRxnked5h2JeargJV3T_v54FHz0dOLEHiMfsfzc/edit#gid=1725254376 - DSpace 6 JSPUI Test Plan https://wiki.lyrasis.org/display/cmtygp/2016+DSpace+6+Testathon+Testplan+Working+group
The Google Sheets could have one sheet (tab) or multiple sheets
Could create issues associated with tasks.
Let's go with a spreadsheet for now.
Let's have a review of the outline.
Call Attendees
Maureen Walsh The Ohio State University Libraries
...
Anne Lawrence Virginia Tech
Felicity Dykas U of Missouri
Apologies