Maintenance meeting notes 2025-12-16

[olleolleolle]

• 🍏 Rails 8.0 branch is now building green in CI and is made ready for review. cc @matyikriszta
• We noted that some JS libraries in use in the application are not maintained. To reduce long-term risk, these can moved off of. In order to separate that work from the "general Rails upgrades" efforts, we considered writing individual Issues.
  • JS libraries we use that are packages as RubyGems are especially vulnerable to "maintenance loss". E.g. chosen-rails.
• We merged a cleanup PR about routes configuration that was ignored in 7.2, but raised deprecation warnings in 8.0.

Participants: Olle, Till, Morgan

[mroderick]

I propose that we make an effort to replace chosen with something that is maintained, and will stay maintained for longer.

I wrote such a thing years ago, and haven't done much to maintain that since. So, I'm not going to propose that we use that one.

However, I had a snoop around and found this: https://github.com/github/auto-complete-element

This looks promising to me, so I think we should do an experiment with this in a branch, and replace one instance of chosen.

Opinions?

[matyikriszta]

Would love to replace chosen-rails, it's not only unmaintained but I think the UX of using it has never been great, I always disliked that solution. Would love to test the UX of auto-complete-element, I can't see an example site in their docs. So I agree, let's install and see how it works.