00:09:46	Craig McNally:	What ever happened to the MOU initiative?
00:10:05	Craig McNally:	IIRC that included language about maintenance
00:11:35	Christie Thomas (she/her):	That is probably where I got the idea, then.
00:25:12	Christie Thomas (she/her):	Thank you for that. This helps me to understand the process.
00:25:54	Wayne Schneider:	Grails stack was original to FOLIO, it predated TC entirely IIRC
00:26:01	Maccabee Levine:	Reacted to Grails stack was ori... with "👍"
00:26:15	Maccabee Levine:	Reacted to Thank you for that. ... with "👍"
00:26:31	Ingolf Kuss:	sorry, I had lost connection . Now back again.
00:27:34	Maccabee Levine:	For example I included a CC member on the licensing subgroup...
00:29:29	Craig McNally:	Replying to "Grails stack was ori..."

Note that K-int has indicated that they intend to adopt/migrate to using micronaut... I don't know if they plan to run that by the TC to get it on the OST
00:30:36	Christie Thomas (she/her):	Replying to "Grails stack was ori..."

What are the implications if a developer adopts a technology not on the OST or that is not approved by the TC?
00:34:14	Craig McNally:	Replying to "Grails stack was ori..."

In theory, if it's in a new module, the TCR evaluation criteria would fail, and the TC would need to make an explicit decision on whether to accept the module anyway, or not.
00:35:02	Wayne Schneider:	Gradle
00:35:15	Craig McNally:	Replying to "Grails stack was ori..."

 if it's in an existing module, the situation is different... We are starting to trial doing evaluations of existing modules... It isn't clear what would happen if a module which has been around for along time fails a criteria like that during their eval
00:36:33	Christie Thomas (she/her):	Replying to "Grails stack was ori..."

Thank you.
00:36:37	Craig McNally:	Reacted to "Thank you." with 👍