Page History

...

• (30 mins) General Discussion Topics
  
  1. 7.5 Planning
     1. Rough schedule above, loosely based on 7.4 schedule. (NEW: "Documentation week")
     2. Step through Tiers & assign features in Tier 2 and Tier 3.  See DSpace Release 7.0 Status
  2. Updates / Brainstorms about improving initial response speed of DSpace 7 UI ?  See DSpace 7 UI Optimization Analysis 
     1. Possible performance issues Tim has found in Angular UI:
        1. Some libraries we use are quite large & take up a lot of space in main.js.  Some fixes already (which decrease main.js by ~81KB gzipped):
           1. https://github.com/DSpace/dspace-angular/pull/1903 (Replace momentjs, saving 66KB)
           2. https://github.com/DSpace/dspace-angular/pull/1908 (Shrink Klaro by translating it ourselves, saving 15KB)
        2. "Shared" module (/src/app/shared) is massive (151KB gzipped) and is all included in main.js.  It likely needs to be broken up into many smaller "shared" modules which can be lazy loaded where needed.
        3. Not always lazy-loading or delaying download of larger features, resulting in larger initial download before the page is drawn.  For instance, it'd be ideal to lazy load Klaro (which is a large library) after the initial page loads. (It's recommended by Klaro to use deferred loading)
        4. Main.js could potentially be shrunk to only include code & dependencies needed on all pages (e.g. header/footer, core modules, core dependencies, etc).  It's 877KB gzipped and it really should be half that size or less.
           1. All other modules should be lazy-loaded on the pages where they are used. 
  3. (Other topics?)
• (30 mins) Planning for next week
  • Review the Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
  • Review the 7.5 Project Board - Assign tickets to developers & assign PRs to reviewers.
    • Paid (by DSpace project) developers must keep in mind priority. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.
    • Volunteer developers are allowed to work on tickets regardless of priority, but ideally will review code in priority order

...