Create an inventory of essential components

[jamesmisson]

Create an inventory of essential components (e.g. manifesto, manifold, iiif-metadata-component, iiif-gallery-component, etc.)

[demiankatz]

Here is a list of dependencies in package.json that either belong to @edsilv personally, exist as separate projects in the UV GitHub, or are part of IIIF-Commons. I think any or all of these might turn out to be in scope for steering group maintenance, since they are not guaranteed to be managed by other communities in situations where maintenance is needed (e.g. a critical security vulnerability):

• @edsilv/http-status-codes
• @edsilv/key-codes
• @edsilv/utils
• @iiif/base-component
• @iiif/iiif-av-component
• @iiif/iiif-gallery-component
• @iiif/iiif-metadata-component
• @iiif/iiif-tree-component
• @iiif/manifold
• @iiif/presentation-3
• @iiif/vocabulary
• @universalviewer/aleph
• @universalviewer/uv-ebook-components
• manifesto.js

For each of these components, we should pick one of the following:

1.) Eliminate dependency (e.g. move code back into the core project)
2.) Continue maintaining dependency separately
3.) No maintenance by steering group required

[LlGC-jop]

I think if there's something where waiting an unknown amount of time for a new release will delay updates to UV e.g. that gallery focus issue, then we need to either move it into the core, or at least fork it into the UV Github and use that, and create PRs with the changes we made so they don't get massively out of sync.

Alternatively we see about getting more members of the steering group added to the IIIF-Commons Github, although I have no idea about how that works, and I assume we'd need to commit to more than just working on and merging our own issues :)

[demiankatz]

@LlGC-jop, I can add people to the IIIF-Commons GitHub (or individual projects within it) as needed.

As long as we have the power to release dependencies, then pending component releases won't indefinitely hold up UV releases -- but it does introduce more overhead. Dependency maintenance alone is no joke -- having all these repos multiplies the rate at which technical debt accrues simply due to the passage of time. There's also a developer barrier since each project is set up slightly differently, so they increase the learning curve. But there are advantages in keeping them too, like ease of sharing, testing in isolation, etc.