What needs to change
Designating application
Fit and design has been excluded previously, so why would we have it for applications?
Scale up module
Dev teams could debate where the module should live - in what application
Partitioning of stuff already reflects the teams and will probably continue to
Modules were original unit of composition for FOLIO, now we either have two units of composition or modules are just a technical thing and applications become unit of composition
Should the TC accept applications or only modules?
Soon flower releases will be defined by applications
Take module requirement wording and add version for applications
But not weigh in on what module goes in which application
Application:
valid descriptor- evaluators need to know how to validate
is the application new? if a module that is part of that application that is approved does that mean the application is approved or does the application have to get approved first?
how do we indicate an application is included in a flower release?
where modules get bundled together into functionality, which may be more in the PC realm
technical requirements of application descriptors are in support of the functionality bundle
Modules
Might be good to enumerate the roles and responsibilities we have questions about and figure out where those responsibilities practically/actually live, related to future review of our charter
Are application reviews redundant when we are already reviewing the modules?
In order for the module to get in, an application that hosts it has to be in as well
Before this PC were evaluating an "app"
What should PC/TC evaluate?
What about when we have an application that is in FOLIO and new module is added to it and we haven't accepted it then what happens to it?
Future discussion:
Permissions - teams had to adjust to new naming conventions so there are guidelines there - should they go into the criteria? at least point to them - links are already in the criteria
System users - new modules should follow new approach of declaring system user and privs in the module descriptor rather than including logic to create system users
pub sub has been deprecated and is on the way out (eventually), in criteria say that we shouldn't add new pub sub stuff, use kafka directly instead (alignment with OST instead?)