Contribute to the DSpace Development Fund
The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.
Date
11:00 am-1:00 pm EST (Eastern Standard Time)
Zoom: Link in calendar invite
Leadership Group Members
- Bridget Almas Lyrasis* (Ex-officio, Lyrasis seat)
Anne Aubert, Food and Agriculture Organization of the UN- Isabel Bernal Spanish National Research Council CSIC
- Andrea Bollini 4Science*
- Bill Branan Johns Hopkins University
- Kimberly Chapman University of Arizona Libraries
- Maggie Dickson Duke University
- Lieven Droogmans Atmire*
Kent Gerber University of Minnesota†John Gostick University of Cambridge- Gültekin Gürdal Izmir Institute of Technology**
Barbara Hirschmann ETH Zurich- Jyrki Ilva National Library of Finland
Erica Johns (Vice Chair) Cornell University*- Colin Lukens Harvard Library**
Lautaro Matas LA Referencia***- Rachel Molina Indiana University Indianapolis
- Erik Moore (Chair) University of Minnesota*
- Kristi Park Texas Digital Library*
- Małgorzata Paszkowska PCG Academia
- Beate Rajski DSpace-Konsortium Deutschland
Julien Sicot EPFLPaschal Ssemaganda World Bank Group- Carolyn Sullivan University of Ottawa
- Ianthe Sutherland University of Edinburgh
- Maureen Walsh, The Ohio State University Libraries*
DSpace staff attendees
- Tim Donohue
- Holger Lenz
- Michele Mennielli
The represents who will be taking notes for a given meeting. It rotates after each meeting to the next person in the attendee list.
* Members of DSpace Steering Group
** Community At Large Representative
*** Ex-officio member nominated by the Leadership Group as representative of the community at large. Ex-officio members do not have voting rights
† DSpace Community Advisory Team (DCAT) Chair, ex-officio, non-voting
Agenda
| Item | Information / Description | Who | Time | Actions Needed | |||||||||
| 1 | Welcome, Notetaker | Welcome Notetaker: Maggie | Erik | 5 mins | N/A | ||||||||
| 2 | Consent Agenda | 2026-27 DSpace Membership Updates:
Development & DSpace-DSpace-CRIS Merger:
DCAT:
Outreach and Engagement:
Partnerships: LA Referencia and UbuntuNET initiatives are still providing the latest numbers. An update will be shared shortly via email
Org Home
| Erik | 5 mins | N/A | ||||||||
| 3 | Q4/FY26 Financials | Overall DSpace had a strong year financially, positive to budget and a continued trend of year-over-year growth in revenue. This has enabled the program to build up its Reserve Fund, while the Lyrasis CST Growth Fund has facilitated the expansion of the staff. Revenue and Expense Summary The main factors in the revenue variance were greater than budgeted interest income and membership dues, which offset slightly under budget service provider fees. The main reason for the expense variance was the conservative budgeting for a full year of the new Technical Support Engineer position that wasn’t filled until January. Travel expenses were also under budget due primarily to Open Repositories being held virtually. Grants and Other Investments Net Assets
The majority of the funds in the Development Fund have now been spent on Accessibility improvements. | Bridget | 10 mins | N/A | ||||||||
| 4 | Wiki Update | Update on current wiki, recommendations for future wiki use | Bridget | 5 mins | N/A | ||||||||
| 5 | Elections Updates | Vacant Steering Seat:
3 Steering Seats becoming vacant as of Nov 1:
Regular Election for Leadership Group:
Community-at-large:
| Erik | 10 mins | N/A | ||||||||
| 6 | AI Contributor Policy | Review and discussion of AI Contribution Policy Document Review and discussion of DSpace Program Value Proposition (relating to the AI Contributor Policy) | Tim, Holger | 5 mins | N/A | ||||||||
| 7 | Marketing and Outreach | DSpace 25 Year Anniversary – Ideas? Development Fund – Ideas? Other? | Erik, everyone | 10 mins | N/A | ||||||||
| 8 | All Other Business | Consent agenda items that need additional discussion Other topics? | 5 mins | ||||||||||
| 9 | Break | N/A | N/A | 5 mins | N/A | ||||||||
| 10 | AI Workshop | Session Outline:
| Bridget | 60 mins | Next steps to develop an action plan for DSpace and AI |
Notes
Compiled by Maggie Dickson
Notes
- Welcome - this is the last leadership group meeting of the year
- Consent Agenda
- Reviewed; no comments or additions
- Q4/FY26 Financials (Bridget)
- Nice YoY growth; very positive year end for Dspace
- Over budget due to m'ship growth, interest growth. Offset small increase in LSP.
- Spent less on travel (OR was virtual), computer supplies, salary savings
- Dev fund is nearly depleted at this point due to accessibility work
- Tech support engineer position is largely subsidized by growth fund; at end of allocated 3 years we will need to determine whether we can take on the additional expense
- Wiki update (Bridget)
- Wiki is hosted in Lyrasis Confluence hosted by a 3rd party - Atlassian is deprecating 3rd party hosting so we are proactively migrating our wiki. Currently we're part of a big Lyrasis wiki that is an unmanageably large group of users. The new cloud wiki will be DSpace only
- Large part of the effort of migrating is decisions on what to migrate, what to archive. Decisions about migrating users. All detailed in the document Bridget has prepared: Wiki Migration Notes for Governance
- We need to designate a representative(s) to work with Bridget to work on this project.
- Plan is also described in document.
- Atlassian will provide a mapping file for existing links so that should continue to work, but that will be part of testing.
- If folks have had experience migrating wikis, your input would be greatly appreciated. Ideally a couple of people would be helpful - respond to Erik's email if you want to participate.
- Question: Is leadership membership required for participation?
- Up to us to decide but should be someone with a vested interest in the community. Would be helpful to have someone from Governance participating.
- Steering will be charging the group. They meet on Sept 9 so we need to have names for them to review by that time.
- Election updates (Erik)
- Vacant steering seat. There were some questions re: balloting so that has caused a bit of a delay. Erik is going to meet with Governance separately to get things moving, make sure the election is run in alignment with the operations manual guidance.
- 3 Steering seats available Nov 1 - Steering is composed of 9 elected individuals, 3 year terms. Membership is not required for election. Erik is getting nominations, will send out ballots.
- Leadership is a 1 year term. Platinum - guaranteed seat, Gold - 1 for every 2, Silver - 1 for every 4, Bronze - 1 for every 8.
- More nominees than seats for Gold & Silver so we will need elections
- Last year we were in a similar position but went ahead and seated everyone as the extra seats from Gold & Silver filled vacant Bronze seats.
- Elections will happen before this Leadership term ends, likely in mid-September.
- Votes for Steering will happen after new Leadership members are seated so they can participate in the Steering nomination process
- Community at large nomination is in place until Sept 7
- AI Contributor Policy (Tim)
- Purpose is to allow devs & committers to manage/set guardrails around contributions that appear to be either entirely AI generated or greatly contributed to by AI.
- Tim, Holger, & Lia drafted this policy and they have been circulating it for feedback.
- Drafted based on policies from other open source projects (eg Apache Foundation, Mastodon, Fedora Linux) as well as collaboration within Lyrasis.
- Policy refers to values statement is in attendant document, which is also under review before it is incorporated into the policy doc.
- High-level policy: AI contributions are allowed but humans must always be accountable, and humans must disclose use/scope of use of AI
- Copyright & legal section is designed to protect Dspace; still under development
- Would like any feedback. Want this policy to be as clear and understandable as possible.
- Questions
- Code review bottleneck is already a problem; this could make that problem even larger? Need to address this
- Yes, a human must do the review. Policy goal is to address the onslaught of AI slop coming their way but they could fine tune it eventually to determine how best to use AI in code review.
- Idea - identify criteria that AI could use to weigh CRs against.
- Conceptually seems reasonable but will need to figure out how to make that work on a day-to-day basis.
- General agreement that it is a good idea to use AI to simplify process.
- Potentially murky area around the use of AI to generate issue description.
- They will work on clarifying that but they are trying to address how verbose the AI-generated descriptions at issue & PR levels
- Steering will review/discuss on Sept 9
- Marketing and Outreach (Erik)
- Celebrating DSpace's 25th anniversary
- There is a little funding for this
- Small planning group to think about where/how to celebrate & promote DSpace, also gather data and update registries
- Reach out to Erik if you are interested in participating; Steering will
- Ideas
- Settle on what to call it so we can have branding - 25 years of DSpace in a tagline
- For development fund - quantifying contributions (?)
- Infographic for what has been accomplished over the 25 years, translate it into multiple languages. Get testimonies from user communities
- Could be a way to get the DSpace registry updated, learn more about current user community
- Quantify the number of items available online globally
- Talk to very early DSpace contributors/adopters
- session/panel on history of DSpace
- Showcasing particular DSpace instances
- Example: an institution recently updated from v1 to v8 - that's impressive
- upgrade-a-thon, providing some help to institutions still stuck on older versions
- progression over time
- DSpace logo made from a collage of homepage screenshots from different DSpace implementations
- DSpace chatbot for wiki
- Where in the World is DSpace? Like Where in the world is Carmen SanDiego, but we highlight all the places around the world that use it
- Make it an open celebration, collecting and publishing stories, projects, accomplishments..a sort of OA week website but focused on the DSpace community
- Celebrating DSpace's 25th anniversary
- Code review bottleneck is already a problem; this could make that problem even larger? Need to address this
No notes taken for AI workshop section...