| Current projects | All | - Initial grouping spreadsheet: https://docs.google.com/spreadsheets/d/1a2b1nxnKk6wcZnY2OtsG0kFa4r4UJe-WpuAg2CUEqjI/edit?gid=1717710204#gid=1717710204
- what is useful to work on next with this?
- way to realize some of the initial vision of being extensible via apps, as an ideal future state
- domains in blue, applications in yellow
- right now we have mega applications, over time want to split up. meanwhile any new development get started as applications instead of adding to existing mega applications
- platform minimal, full, then added consortial then adding maybe bibframe etc applications
- will this help communicate how inventory for example should be split out?
- there is technical decoupling work that has to be done in order to actually split these things out into applications, which will take development effort to realize
- some of the current dependencies came about because of expedience more than long term strategy
- including the domains might just make this more confusing, might be better to produce without it
- multiple groupings of modules into applications could be confusing and add overhead but it doesn't keep hosting providers from writing their own application descriptors, but it will be on them to maintain their boutique descriptors
- definition of applications in the RFC
- have to sort out dependencies
- Wayne Schneider can generate a dependency graph from Okapi, possibly by area
- Draft summary document: https://docs.google.com/document/d/1rc4xgJQsNFlXoHW6lAI7MbF8MzaWDb9QW2eryiiyNTo/edit
- WolfCon planning
- Tracking TC/Sysops work
|