Good day everyone!

As discussed in our Thursday meeting, here are some additional (some are time-sensitive) items to be included in our work backlog.  They are not listed in any particular order, but we will probably need to get into the habit of regularly prioritizing our backlog and ensure it is visible to the rest of the community:

• Repo management
  • Process for triaging issues and assigning PR ownership with turnaround expectations (SLAs?)

  • Process for end of lifing a repo when there is no point in maintaining it


Unmaintained repo (now removed from stripes-smart-components):
https://github.com/folio-org/react-githubish-mentions/pull/4

Experiment module (can this go somewhere else than the folio-org?):
https://github.com/folio-org/ui-datasets/pull/1

Deprecated repos, that contain other deprecations:
https://github.com/folio-org/ui-okapi-console
https://github.com/folio-org/ui-items
https://github.com/folio-org/ui-scan
https://github.com/folio-org/stripes-redux
https://github.com/folio-org/stripes-loader

Code rot hanging around in stripes-core:
https://github.com/folio-org/stripes-core/pull/332

• Review of the Stripes architecture

• Stripes testing -- updating the Definition Of Done (e.g., ensuring that stripes tests are developed)

• Making changes to the PR process by running a simple build on the PR
(prob to be included in the Definition of Done)
• CI builds: Travis vs Jenkins

-- 

Mark Veksler

Director, FOLIO Development - EBSCO Information Services

mveksler@ebsco.com | +1-978-356-6500 x2349 (O) | +1-617-470-5453 (m)