...
If you can join the call, or are willing to comment on the topics submitted via the meeting page, please add your name, institution, and repository URL to the Call Attendees section below.
Meeting notes
Plan our DSpace 7 documentation sprints.
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 with a Zoom co-writing call on Fridays for 1.5 hours; for larger participant groups, there is a document leader per document; convert Google 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 documents into chapters with chapter per participant; later have persons to read over whole document; first writing is in Google Docs, then move 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 tickets.
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; it also has comments; could be less work than using Google Docs for drafts and then copying to Confluence.
A spreadsheet would be simpler than using the Confluence management system.
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 optionally create issues associated with tasks.
Let's go with a spreadsheet for now.
Let's have a review of the Documentation outline.
First sprint 10/26-30
We could have sprint planning meetings where participants can decide on possible co-writing meetings like OJS.
Planning sprint is to plan the overall sprint workflow.
Sprint planning meeting at the start of each sprint.
Could record the sprint planning meeting or Confluence page to guide contributors for picking tasks, etc.
We need to compare our tasks to release notes.
Our documentation is text-based and user-centered.
DSpace 7 docs, https://wiki.lyrasis.org/display/DSDOC7x .
Best source are release notes for DSpace 7.
There isn't a Dspace 7 demo but these is a DSpace 7 preview for the REST-API (4Science), https://dspace7.4science.cloud/server/, and another for the user interface (Atmire), https://dspace7-demo.atmire.com/ .
Call Attendees
Maureen Walsh The Ohio State University Libraries
...
Anne Lawrence Virginia Tech
Felicity Dykas U of Missouri
Apologies