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
from 14:00-15:00 UTC
Location: https://lyrasis.zoom.us/my/dspace (Meeting ID: 502 527 3040).
- More connection options available at DSpace Meeting Room
Beta 4 Sprint : July 13-24
- Beta 4 active development
- See board at https://github.com/orgs/DSpace/projects/3
Agenda
(BEFORE MEETING IN #dev-sprint) Developer Stand Up - Developers give brief updates on their effort (or their team's effort).
- Update/see "Current Work" section below based on your status. Please feel free to update prior to meeting.
- Please highlight any new work (needing reviews/testing), any blockers (for you), and any discussion topics you may have.
- (20 mins) General Discussion Topics
- New GitHub Issues Workflow walkthrough for team
- New Issues Templates for either "Bug report" or "Feature Request". For example: https://github.com/DSpace/DSpace/issues/new/choose
- Either option will label the new issue as `needs triage`.
- New GitHub Action/Workflow (issue_opened.yml) will automatically add any newly created issue labeled `needs triage` (or unlabeled) to our DSpace Backlog board.
- NOTE: A second GitHub Action/Workflow (pull_request_opened.yml) automatically assigns newly created PRs to the creator. This is just for easier filtering on Project Boards (in general)...so that you can filter by "assignee" to see all PRs and Issues assigned to the same person.
- These same actions/settings have been copied to all DSpace 7 projects (DSpace, dspace-angular and Rest7Contract)
- New Issues Templates for either "Bug report" or "Feature Request". For example: https://github.com/DSpace/DSpace/issues/new/choose
- New Estimate labels
- Appear like (
e/2)
for an estimate of 2 hours. - Chrome extension will total up the hours in a column: https://chrome.google.com/webstore/detail/issues-hub/gjpcbkmnpfnpmghmiohfcbhckigmloic
- Appear like (
- A brief reminder
- NOTICE: all DSpace GitHub repos have the
master
branch renamed to main. See announcement on dspace-devel
- NOTICE: all DSpace GitHub repos have the
- New GitHub Issues Workflow walkthrough for team
- (30 mins) Planning for next week
- Review of our Beta 4 Project Board
Attendees
7.0 Release Goals
These resources define the prioritization and general schedule we are working towards
- DSpace 7 Release Goals : overview of goals/timelines & beta release process
- DSpace 7 Release Plan spreadsheet: our planning spreadsheet which details which features are scheduled for each Beta release.
Current Work
Project Board
DSpace 7.0 Beta 4 Project Board: https://github.com/orgs/DSpace/projects/3
To quickly find PRs assigned to you for review, visit https://github.com/pulls/review-requested (This is also available in the GitHub header under "Pull Requests → Review Requests"
Delayed / Needs Discussion
- Finalize / approve the initial list of all authorization features which we should implement for the /api/authz/features REST endpoint. This list of features should be limited to only features which are required to enable/disable User Interface functionality. (In other words, we can always add more features in the future. We just need to approve the list necessary for 7.0)
- Review current spreadsheet (from Andrea Bollini (4Science) ) : https://docs.google.com/spreadsheets/d/1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing
- Art Lowel (Atmire) : I don't see any immediate issues with the current set of features, but I would prefer a consistent naming scheme. I'd use canDoSomething for everything
- Tim Donohue added possible renames of these features based on Art's idea (see cell comments in spreadsheet). I like the "can[DoSomething]" naming scheme as well.
- Review current spreadsheet (from Andrea Bollini (4Science) ) : https://docs.google.com/spreadsheets/d/1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing
- Proposal from Art Lowel (Atmire)on enhancing object cache in Angular UI.
- Initial Performance Testing from Chris. Needs revisiting / retesting prior to 7.0.
- https://cwilper.github.io/dspace-perftest/
- These performance tests were run prior to the work on "projections" (to limit the data returned by the REST API). Therefore, it is likely performance is much improved, but needs verification testing.
- (REST Contract) Edit Homepage News: https://github.com/DSpace/Rest7Contract/pull/45
- Delayed. General agreement (in meeting on March 21, 2019) that storing HTML in metadata fields is not really ideal behavior. Metadata (from a librarian standpoint) tends to be free of format-related markup (as that allows for easier sharing, understanding of metadata. Currently Community & Collection homepage information is HTML-based and is stored in metadata that is appropriate for a minor subset of information (like the title) but it is better to move large/rich text to bitstreams.
- Proposal here is to consider storing HTML-based markup (for Site, Community & Collection homepages) in Bitstream(s) associated with the object in question. May allow for more CMS-lite behavior in the future
- Timeline for this is uncertain. Possibly in 7 or 8. May depend on how/whether it can be scoped.