| [06:09:11] | <mstenta[m]> | farmOS 4.x has been updated to Drupal 11! 🎉 https://github.com/farmOS/farmOS/pull/967 |
| [08:02:02] | <farmBOT> | @farmOS@fosstodon.org => #farmOS 4.x has been updated to #Drupal 11! 🎉 https://github.com/farmOS/farmOS/pull/967 => https://fosstodon.org/@farmOS/114590576041992844 |
| [09:02:24] | * ander[m] has joined #farmos |
| [10:35:21] | <mstenta[m]> | @room We need one more approval of https://github.com/farmOS/farmOS-community-blog/pull/31 in order to publish it. |
| [11:03:53] | <farmBOT> | @farmOS@fosstodon.org => New community blog post! #farmOS and Coffee: Tracking Animals, Data, and Sanity https://farmos.org/blog/2025/farmOS-and-coffee-tracking-animals-data-san... => https://fosstodon.org/@farmOS/114591696672550855 |
| [12:00:08] | <symbioquine[m]> | farmOS weekly dev call on now - all are welcome! https://meet.jit.si/farmos-dev |
| [12:04:51] | <mstenta[m]> | oh wow that time already! |
| [13:19:37] | <mstenta[m]> | paul121: https://github.com/farmOS/farmOS/pull/970 |
| [13:48:57] | <mstenta[m]> | paul121 symbioquine : Hmm... just realizing... with regard to the "base modules" idea (moving them to `farm.info.yml`... one of the side-effects of that is they will be installed in all functional tests... which we probably don't want (we have a hacky workaround to prevent that in functional tests currently, which I was hoping to remove) |
| [14:15:07] | <paul121[m]> | hmm |
| [14:15:55] | <mstenta[m]> | yea... thinking about it... we might need to stick with what we have, at least with regard to installing the base modules in an install task |
| [14:16:06] | <paul121[m]> | do they cause conflicts or is it just to try and keep tests as minimal and fast as possible? |
| [14:16:09] | <mstenta[m]> | we could still remove the module installation form from install tasks |
| [14:16:19] | <mstenta[m]> | both i think |
| [14:16:56] | <mstenta[m]> | https://www.drupal.org/project/farm/issues/3183739 |
| [14:17:07] | <paul121[m]> | ah yea. I assume we can have an install task that doesn't expose a form? it's just hard-coded? |
| [14:17:17] | <mstenta[m]> | yep |
| [14:17:24] | <mstenta[m]> | we have one already for other config |
| [14:18:03] | <paul121[m]> | oh interesting |
| [14:18:10] | <paul121[m]> | I see |
| [14:19:45] | <mstenta[m]> | it means we'll still need to use $GLOBALS['farm_test'] to detect that we're in the context of a functional test... i was hoping to remove that, but maybe we can't |