Page History

...

• (15 mins) 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.
• (30 mins) General Discussion Topics
  1. Updates on 7.0 Release Schedule from Leadership & Steering
     1. Working to ramp down DSpace 7 Entities Working Group by Jan 1.  Seems likely that most of the Entities / OpenAIRE work (if not all) will be completed or "in code review" by end of December anyhow.
        1. Andrea Bollini (4Science) noted that this don't seem inline with the direction of a managed schedule of dspace 7 where Entities eventually are in lowest priority for DSpace 7.  He notes that speedup this work in December mean subtract time to other task in higher priority and require other to review work not in the immediate todo list or give up to other. He point out to a coming PR that seems too large to be reviewed properly: https://github.com/DSpace/dspace-angular/pull/531
     2. As of Jan 1, we'll be one working group (this one).  Working Group will start to work more in a "sprint-like" fashion.
     3. Goal is to work together to release a new updated "beta" per month (starting in Feb).  These Betas will be layering on new features each month, until we hit 7.0 Final.  Releases will be simple (like was done for "7.0 Preview") – just cut a tag, and push release via Docker. (I.e. this will NOT be a full Maven release process, as these Betas are simply for early community testing & feedback.)
        1. Tim will post more info on each "Beta" soon (by next week).
     4. Leadership & Steering will be looking to align paid development resources to help with these Beta sprints (to help ensure we have consistent development resources).  That said, volunteer-based development will continue to be welcome, as it will help us move even faster.  More info will be coming.
  2. (Ongoing Topic) High priority REST Authorization efforts (and upcoming PR from Andrea Bollini (4Science) ).  Any questions or concerns needing discussion?
  3. Take decision about CORS headers, Shibboleth and "withCredentials" issue: 

     Jira
     server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-4396

• (15 mins) Planning for next week
  
  • Assigning PRs for Review
  • Next tasks from Development Planning Spreadsheet

...