2025-02-26 Comms for TCR Process Changes

We need to devise a plan for communicating recently changes to the TCR process/criteria/etc.  

See https://github.com/folio-org/tech-council/pulls?q=is%3Apr+is%3Aclosed+label%3A%22READY+TO+MERGE%22

Apparently these have been merged already.  Wasn't the idea to wait for this comms. plan?

Notes: Reviewing merged TCR process comms changes.

Use ASF 3rd Party License Policy for module evaluation : asking the devs to do something new, so should involve some additional discussion at a later time.

Split and expand criterium for consumed APIs; mention requires/okapiInterfaces/… : Devs (Should) know to do this. This change is to really help the evaluators with what/where to check.

Need to write up these specific changes into a slack message and send out?  Changes to the policy/process can/will be made going forward, how do we communicate that consistently going forward. Previously we put out a video, or no comms were made. Slack seems like a good candidate maybe with 1 video that generally shows what the process is, and then bullet points with changes.

Which slack channels are appropriate: product-owners, development, tech-council, release-management-stakeholder, stripes-updates, product-council.

Link to this page: New Module Technical Evaluations which we updated in order to be more generic and streamlined going forward. Need to add a section for policy/process updates and what would cause us to update the policy/process. Discussion about whether to specify when/how policy/process changes go into effect. Maybe generally plan to update it between releases after a release has been closed and the evaluations complete for that release? We need to avoid making a moving target for the developers.

Jenn Colt will draft a message and send it out to the aforementioned slack channels.