...
| Time | Item | Who | Notes | ||||
|---|---|---|---|---|---|---|---|
| 1 min | Scribe | All | Maccabee Levine is next, followed by Craig McNally Reminder: Please copy/paste the Zoom chat into the notes. If you miss it, this is saved along with the meeting recording, but having it here has benefits. | ||||
| 5-10 min | Liaison Updates |
| |||||
| 1 min | Upcoming Meetings | All |
| ||||
| 20 15 min | TCR Board Review | All | Today:
Last time: mod-reporting, a Go rewrite of mod-ldp, has been submitted. As Go is not yet supported it requires work regarding static code checks, code coverage automation, etc. We should first complete the existing TCR requests. Should we merge the PR that removes the snapshot criterium from our module acceptance criterium? This will solve the issue with the TCR. Depending on a SNAPSHOT version is bad practice. Maven rejects a release when trying to release a module with SNAPSHOT dependency. It is also bad practice during development because the build is not reproducible. However, as FOLIO libraries are provided as SNAPSHOT version only the modules are forced to use SNAPSHOT versions during development. When merging the PR we can appove the submitted module without explaining why we overwrite the SNAPSHOT criterium. Instead of removing the SNAPSHOT criterium it should be a requirement that can be ignored if reasonably justified. A warning not to use a SNAPSHOT dependency is in the module release documentation for maven based modules: https://dev.folio.org/guidelines/release-procedures/#prepare-and-perform-the-source-release We don't know how non-maven modules prevent SNAPSHOT dependencies. It's up to the development teams how to prevent SNAPSHOT dependencies. Go modul mod-reporting: When accepted as a module we indirectly adopt Go as a language. Should we first accept Go as a language including specific criteria regarding static code analysis, security, etc.? In the past PoCs have been used to add new stuff to FOLIO without evaluation/approval. We had been discussing the Go RfC for months. Regarding adding the Go stack we need more feedback from the community. | ||||
| 10 min | Developer advocate update | Patrick Pace (Unlicensed) | |||||
| 5 min | Technical Council Sub-Groups Updates | All | |||||
| 1 min | RFCs | All | Reminder(s)
| ||||
| 1 min | Decision Log | All | Need to log decisions for the following: (see above) | ||||
| 15 min | All | Check Recurring Calendar... We still need to transition the Sunflower page from DRAFT → ACCEPTED... ASAP. What is preventing this from happening? | * | WOLFcon recap | All | ||
| NA | Zoom Chat |
Topic Backlog | ||
| Decision Log Review | All | Review decisions that are in progress. Can any of them be accepted? rejected? |
| Translation Subgroup | All | Since we're having trouble finding volunteers for a subgroup, maybe we can make progress during a dedicated discussion session? |
| Communicating Breaking Changes | All | Currently there is a PoC, developed by Maccabee Levine, of a utility to catalog Github PRs that have been labeled with the "breaking change" label. We would like to get developer feedback on the feasibility of this label being used more often, and the usefulness of this utility. |
| Officially Supported Technologies - Upkeep | All | Previous Notes:
Stripes architecture group has some questions about the Poppy release. Zak: A handshake between developers, dev ops and the TC. Who makes that decision and how do we pass along that knowledge ? E.g. changes in Nodes and in the UI boxes. How to communicate this ? We have a large number of teams, all have to be aware of it. TC should be alerted that changes are happening. We have a couple of dedicated channels for that. Most dev ops have subscribed to these channels. How can dev ops folk raise issues to the next level of community awareness ? There hasn't been a specific piece of TC to move that along. Craig: There is a fourth group, "Capacity Planning" or "Release Planning". Slack is the de facto communication channel. There are no objections to using Slack. An example is the Java 17 RFC. Craig: The TC gets it on the agenda and we will discuss it. The TC gets the final say. Marc Johnson: We shouldn’t use the DevOps Channel. The dev ops folks have made it clear that it should only be used for support requests made to them. Jakub: Our responsibility is to avoid piling up technical debt. Marc: Some set of people have to actually make the call. Who lowers the chequered flag ? Craig: It needs to ultimately come to the TC at least for awareness. There is a missing piece. Capacity Planning needs to provide input here. Marc: Stakeholders / Capacity Planning could make that decision. Who makes the decision ? Is it the government or is it some parts of the body ? Marc: the developers community, the dev ops community and sys ops are involved. For example the Spring Framework discussion or the Java 17 discussion. But it was completely separate to the TC decision. It is a coordination and communication effort. Marc: Maybe the TC needs to let go that they are the decision makers so that they be a moderating group. Jakub: I agree with Marc. But we are not a system operating group. Dependency management should be in the responsibility of Release management. There are structures in the project for that. Jason Root: I agree with Jakub and with Marc also. Policies should drive operational/release/support aspects of Folio. Jason Root: If the idea of “support” is that frameworks are supported, then of course the project should meet that. Marc Johnson Craig: This is a topic for the next Monday session. Craig to see if Oleksii Petrenko could join us to discuss the process for updating the officially supported technologies lists. |
| Dev Documentation Visibility | All | Possible topic/activity for a Wednesday session: Discuss/brainstorm:
|
| API linting within our backend modules | All | https://folio-project.slack.com/archives/CAQ7L02PP/p1713343461518409 |
| PR Templates | All | https://folio-project.slack.com/archives/CAQ7L02PP/p1713445649504769 Hello team, Small request to consider. Regarding pr templates.
What I suggest is that, pr template shouldn't be any instructions, because most developer who are creating pr have already understand the rules. If we put just two section into template, it will encourage developers to write more about their work and that lead to knowledge sharing among developers. |
| Proposed Mod Kafka | All | https://folio-project.slack.com/archives/CAQ7L02PP/p1714471592534689 Mike Taylor Proposal. If and only if a FOLIO instance is running Kafka, it should insert and enable a module called mod-kafka, which consists entirely of a module descriptor that says it provides the interface kafka. The purpose is so that other modules can use the standard <IfInterface> and similar tools to determine whether they should attempt Kafka operations. Rationale: the FOLIO ILS depends absolutely on Kafka, but other uses of the platform will not. One such example: a dev platform that includes only mod-users, used as a source of change events for Metadb. |
...