Time/Place
This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Audio/Video Conference Link: https://lyrasis.zoom.us/j/396037251
- Meeting ID: 396 037 251
- Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia
Join fedora-project.slack.com on the "tech" channel
- Self-register at: http://slack.fcrepo.org/
Attendees
- Danny Bernstein
- Andrew Woods
- David Wilcox
- Jared Whiklo
- Peter Winckles
- Ben Cail
- Calvin Xu
- Daniel Lamb
- Ben Pennell
- Thomas Bernhart
Agenda
- Announcements
- fcrepo-migration-validator Sprint underway
- finished design, hopefully ready Friday
- Today is the last meeting of the year
- Reminder: Fedora-related proposals for Code4Lib in March (deadline: Dec 21st)
- contact David for info, need to present the proposal in 10-15min presentation
- Leaders meeting update
- discussed beta requisite
- discussion around data-gathering provision from fedora installations (eg. institution emails, name, etc using fedora)
- autoversioning vs on-demand object versioning
- Danny Bernstein will create a Jira ticket per object versioning
- immutable heads PR issue: Andrew suggest more documentation needed at different level such as wiki and README
- fcrepo-migration-validator Sprint underway
- Alpha 2 release starts at 1pm eastern
- final release of 2020, congratulation to everyone for their hard work and dedication
- user reported testing 10x speed faster than MariaDB and MySQL on fedora6, planning looking into on bring MariaDB and MySQL up to speed
- 120 tickets in the Prioritized list of issues.
- everything in red is slated for beta
- Do we need to prioritize the blue tickets (ie for 6.0.0 or post-6.0.0)
- do the prioritization of blue ticket after Beta
- Beta release sprint in Q1 of 2021?
- either early January or mid-late February depend on team's availability, propose two week sprint and followed by another sprint focused on documentation
- Consensus on weeks of Feb 8 and Feb 15th
- Pilot updates
- What else can we be doing with GitHub Actions?
Tickets
In Review
Expand Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Notes
Actions
- Danny Bernstein will create a Jira ticket per object versioning
- Andrew Woods will Andrew create documentation needed at different level such as wiki and README for the immutable head PR issue
- Prioritization of blue tickets after Beta release