Page History
...
# | Time | Item | Information | Who | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 5 min | Welcome |
| Kristi Park | ||||||||||||||||||||||||||
| 2 | 25 min | DSpace 7.0
| Update on the current status of DSpace 7 development and the forthcoming beta versions.
| Tim Donohue Maureen Walsh | ||||||||||||||||||||||||||
| 3 | 15 min | Working and Interest Group Reports | Brief updates/Q&A from Working and Interest Group representatives.
| Kristi Park (chair, Governance Working Group) Scott Hanrath (chair, Product Visioning Working Group) Jenn Bielewski (chair, Marketing Interest Group) | ||||||||||||||||||||||||||
| 4 | 5 min | Quarterly Financial Report | Quarterly financial report distributed via listserv. Reflects info as of 3/31/21 Variances
3/31 report does not include 7.0 beta 5 development costs as those are not yet invoiced. Approximately $74,000 to be billed soon. 7.0 Development Costs
| Laurie Arp | ||||||||||||||||||||||||||
| 5 | 15 min | DSpace-LYRASIS MOU | DSpace Steering recommends adoption of a revised MOU developed by the Governance Working Group. Clean copy of MOU: DSpaceLYRASISMOU20210217-cleancopy.doc Version of MOU showing all changes: DSpaceLYRASISMOU all changes 20210222rev.doc | Kristi Park | ||||||||||||||||||||||||||
| 6 | 10 min | DSpace 7.1 and 7.2 feature prioritization | Review results of prioritization survey, which asked Leadership members to select features remaining in the backlog after 7.0 that they feel are most essential to prioritize for version 7.1. Survey results:
Open time for questions from Leadership about the survey and results. | Kristi Park | ||||||||||||||||||||||||||
| 7 | 40 min | Breakout discussions: Prioritization of features for DSpace 7.1 | Leaders will break into 4-5 randomly assigned groups to further discuss the prioritization of features for DSpace 7.1. We will take 25 minutes for breakout discussions and then return for 15 minutes to report out and discuss with the whole group. Guide for breakout discussions:
You can take notes in a Google doc that matches your Breakout Room number, linked to here: | Kristi Park, all | ||||||||||||||||||||||||||
| 6 | 5 min | Any other business |
|
Notes:
Welcome
- Kristi thanks everybody for taking the survey re. feedback about the last Leadership meeting
- Another survey will be sent out after this meeting
- Two new members to Leadership Group:
- Lautaro Matas from la Referencia
- Cesar Olivares left the group because he left his current position, Andres Andrés Melgar replaces him
- Sarah Swantz has left her position as well, it is still open who will replace her
...
- Time gives an update on the current status of DSpace 7 development and the forthcoming beta versions
- Dev team currently working on release of beta 5, should be released tomorrow, testathon starts next week
- Beta 5 is feature-complete. Timing for final release (7.0) depends on feedback/bug reports from testathon. Maybe one or two month after the testathon.
- Still looking for volunteers for security testing. Looking for 1-2 institutions to do an external audit to give a different perspective to what the dev team has already done in this area. See Security Testing
- Third party (deque) will do an accessibility audit during the testathon. Co-funded by Lyrasis and TDL
- Kristi: Congratulations to the dev team on the progress.
- Maureen gives an introduction to the testathon:
- Testathon begins Monday. Everyone is encouraged to participate.
- Please watch the videos on the information page. People can also add test definitions. See test plan. There are instructions on how to use the different test status on the “Summary” tab of the test plan. User personas are also described in the summary. Every feature needs to be tested, even those that have already been tested by Bram in March/April.
- Maureen does a demo of doing a test: Open demo repository via link, do the testing, report the result.
- If a test has already been done, the next tester should overwrite the last test result, no matter what the status of the previous test was. There will be small improvements during the testathon, so it makes sense to retest tests that had reported bugs previously.
- Lieven ask whether there is deadline/date for the release of 7.0? Community members have mentioned to him that it is a problem that there is not even a target date. What does the rest of the group think?
- Tim: No target date because it depends on output of testathon
- Susanna: The date depends more on the number of bugs that are found (unknow number), than on the dev resources (known number). Prefers to wait after the testathon before communicating a date for DSpace 7.0.
Pascal: Of course everybody is waiting for a date. Should be ok to wait until after the testathon before communicating a date. Date should be before OR 2021. It could happen that we find a major bug when testing, it is not a good idea to communicate a date now.
Tal: A target date could help institutions in budget planning
Lieven: We need a target date to push work forward.
Kristi: Move this discussion to breakout groups, DSpace 7 WG and Stearing Steering Group.
Working and Interest Group Reports
...
- Apart from MOU topic (see below), questions re. timing of governance year were discussed, will be discussed with stearing Steering and brought to leadership group
...
- Estimated: $ 300,000
- Raised: $ 153,227
- Allocated: $ 284,000 (includes pending invoices for Beta 5)
- Not yet using line of credit
Discussion:
- Kristi: Stearing Steering authorized funded development through 7.1. Have to make decisions on how to manage that.
- Jyrki: Will there be another round of fundraising this year? There might be institutions willing to contribute again.
- Kristi: End of fiscal year is coming in US, if there are funds that could go to DSpace 7.1 development, please consider doing so.
- Robert: Are people more optimistic going into the next budget cycle? Mixed answers from the group.
...
Overview
Content Tools