Page History

...

NOTES:

1. DuraSpace-DSpace MOU

• Welcome to Heather Greer Klein – New Project Manager
• Later in the evening, a smaller group will meet to finalise the MoU, the LG input will be taken into consideration
• The template of the MoU was developed for Vivo and will also be used by Fedora
• Erin: The legal Name of DuraSpace is actually “FedoraCommons”, d/b/a means “doing business as”
• DSpace Community vs. DSpace Project – how to call it?
  • Erin: Both have been used in other documents, term should reflect the spirit of the governance groups;
  • John: projects often have a defined endpoint, therefore the term does not cover the “enduring” character of the DSpace community
  • Ceasar: however “project” has been used more often (see definition on website)
  • John: and “project” is also used for Fedora and Vivo
  • Susanna: Project includes community and software, should we mention this somewhere?
  • ArchiveSpace: They speak about “community”, probably DuraSpace will be a community within Lyrasis
• John notes that some details are stated for 2019 - Does this mean we look at the MoU every year? Erin: Yes. Budgeting process at Lyrasis happens every year.
• Erin re. termination: DuraSpace is a charitable organisation. If DSpace wanted to leave, they would need to identify another NPO in US where DuraSpace could transfer assets to. This is due to articles of incorporation which a.o. state that assets cannot be transferred outside of the US. This mainly refers to trademarks and membership dollars, DSpace source code is free.
• Lieven re. termination: 90 days are a quite short period. An extension clause would be good. Erin agrees. Ultimately agreements should be over 3-4 years, not yearly. We could add language re. extension will be granted if the new organisation is not yet incoroporated.
• Lieven: Are there any aspects or characteristics of the project that are currently not covered by “responsibilities”?
• Erin: We also need to add language about Lyrasis merger in the termination section. Or create a new “assignment” section. John: “Assignment” section would be more appropriate.
• Susanna: a general language about assignements is better than a direct mention to a specific event (such as the merger with Lyrasis)
• Tim: Should we mention Heather's new role?
• Lieven: some aspects are very specific, e.g. 90% of a DuraSpace FTE for technical coordination 
• John: That was the background to his question above: Why is the budget in the MoU? This is very specific for a MoU
• Erin: That’s why details are in the appendix
• Erin to Lieven: if we want to include potential new roles, we could add change management language to cover this
• Pascal: thinks that the MoU misses to make clear that the strategic decisions are taken by the governance of the project. Also, the responsibilities of the governance should be defined in more detail.
• Erin: This could be covered in the Project Responsibilites section.
• Lieven: As an example, what happens if the Governance is not happy with the person that DuraSpace assigns as a tech lead?
• Erin: We could e.g. add that governance can provide performance evaluation assessment
• Salwa: To put this in more general terms, the MoU should deinfe the feedback mechanism for things we are not happy with
• Erin: Language re. escalation process can be added
• Erin: The MoU is really a combination of a classic MoU and some more detailed sections. It includes change management and escalation process, which would normally be part of a project plan, but since we don't have such document, it makes sense to add these topics to the MoU.

2. DuraSpace Summit

Who will attend? John. Tim, Erin

Usually there is a governance meeting on the summit

Michele will circulate a google doc to identify topics we would like to talk about

Possibility to join remotely might be arranged, members appreciate

Report out to the community is also required (last year, next year), Mic can put together some slides

3. DSpace Github security vulnerability notifications

Call for volunteers

NYU have received notifications from GitHub, they realeased a feature where they scan every project for security problems, known issues in third party tools popped up, quick analysis showed that most are probably false positives. The feature only looks at third party vulnerabilities. Might not have impact on DSpace. E.g. real vulnerability, but without impact on DSpace. NYU is still concerned, no staff for detailed analysis currently availbale. Volunteers to look into this welcome.

Lieven and Salwa and John will reach out to their teams about help

Some of the analysis requires knowledge of DSpace. Therefore developers needed, not sysadmins.

4. Wrap up and next steps

Salwa attended DuraSpace Board meeting. International membership was a big topic. There will be a press release soon.

Salwa was reassured, DSpace is important to them.

Jyrki: Leadership has now access to the meeting notes of Steering https://wiki.duraspace.org/display/dspacesteering/DSpace+Steering+Home

Pascal: German DSpace Anwendertreffen programm has been released

-          GDPR WG will have its first meeting on Friday

Tim: DSpace 7 dev. Schedule – good summary in last months steering group meeting minutes

https://wiki.duraspace.org/display/dspacesteering/2019-02-20+DSpace+Steering+Group+Meeting

Mic: working with users groups and Google Scholar for country specific webinars re. indexing in GS, Brazil, Pero, Mexiko, Germany

Mic: New DuraSpace registered service provider from China

Pascal: DSpace and Docker webinar was recorded, webinar had 55 attendees