| [03:05:16] | * farmBOT has joined #farmos |
| [10:01:02] | * MatthewHansen[m] has joined #farmos |
| [10:30:11] | <mstenta[m]> | symbioquine: I just thought of another farm organization constraint we probably want to add... it's currently possible to create a log that references assets that are in different farms |
| [10:30:44] | <mstenta[m]> | in the interest of keeping those relationships simple, I think we should prevent that. at least initially (like we did with the other constraints) |
| [10:33:46] | <symbioquine[m]> | I guess I need to re-familiarize myself with the existing constraints. I remember having all that discussion, just not a ton of the details. 😅 |
| [10:34:19] | <mstenta[m]> | Yea... the tl;dr is we decided to lock things down as much as possible so that there was no cross-farm references |
| [10:34:30] | <mstenta[m]> | But we missed this one |
| [10:44:45] | <symbioquine[m]> | I guess that makes sense... 🤔 |
| [10:45:22] | <symbioquine[m]> | It's a little less clear to me than the locations/groups scenarios though |
| [10:46:55] | <symbioquine[m]> | I mean in both of those cases we're talking about having cross-farm persistent relationships (cross-farm groups or cross-farm locations) but the plain log reference scenario just lets you have a log that's making note of something about those assets... |
| [12:29:58] | <mstenta[m]> | Yes, but we use the relationship to assets to determine whether or not a log is related to a farm |
| [12:30:14] | <mstenta[m]> | So in the "Logs by Farm" View, the log would show up in multiple farms. |
| [12:30:43] | <mstenta[m]> | There are definitely valid use-cases for that, but if we want to be mindful about "opening up" those use cases intentionally then we need to prevent that now |
| [12:32:44] | <mstenta[m]> | And access/permission implications of it are a bit ambiguous... if a log is associated with assets in multiple farms, and we are restricting access based on farm, that log will be visible and maybe editable in both farms. That would mean that someone in one farm would be able to affect a log in another farm. |
| [12:51:34] | <mstenta[m]> | @room I just opened a PR for a draft community blog post announcing the (upcoming) release of farmOS v4 - please review! https://github.com/farmOS/farmOS-community-blog/pull/32 |
| [12:51:54] | <mstenta[m]> | I am thinking of aiming for the first day of Spring (March 20th) to tag 4.0.0 and publish this blog post. If anyone has thoughts on that timeline, please share them! |