| [19:00:19] | <farmBOT> | @farmOS@fosstodon.org => #farmOS 3.3.2 has been released! https://github.com/farmOS/farmOS/releases/3.3.2 => https://fosstodon.org/@farmOS/113517858291218955 |
| [07:30:14] | <mstenta[m]> | symbioquine: I was just dusting off some old issues and found this again https://www.drupal.org/project/farm/issues/3196844 |
| [07:30:44] | <mstenta[m]> | I wonder if Asset Link might be a place to test out some UI for "clocking in/out" on a task? 🤔 |
| [08:07:11] | <symbioquine[m]> | It certainly could be... |
| [08:08:01] | <symbioquine[m]> | I guess my main question is how would we know what logs that UI should appear for? |
| [08:09:06] | <symbioquine[m]> | Ideally there would be some mechanism/heuristic for only showing the clocking in/out UI for the "right kind" of logs 🤔 (So as to not clutter the UI for the rest of them) |
| [08:49:17] | <mstenta[m]> | Maybe it's a little unobtrusive icon that opens a separate page/view with more options? My assumption is that the farm_quantity_time module would be optional and only enabled if time tracking is desired. But beyond that I think it's hard to predict which types of logs users will want to track time on (unless we add a setting for that 🤔). |
| [08:49:37] | <mstenta[m]> | In either case, I think the bigger question is: do we want to merge that time quantity type without any supporting UI in farmOS itself? |
| [08:49:52] | <mstenta[m]> | The lack of UI is what's blocking it now |
| [08:50:52] | <mstenta[m]> | (Specifically, "clocking in" would create a quantity of type time which references the user ID that clocked in, and when "clocking out" it saves the total time spent to the quantity) |
| [08:51:35] | <mstenta[m]> | This feature hasn't come up recently, so it isn't something I'm prioritizing right now... I was just reviewing old issues and that one stuck out as one that's relatively close |
| [08:53:39] | <symbioquine[m]> | mstenta[m]: I'm in favor of merging it once we're happy with the data model bits themselves. |
| [08:54:09] | <symbioquine[m]> | Especially if we're considering experimenting in contrib-land with the UI |
| [08:54:38] | <mstenta[m]> | Cool - well I think the data model bits are ready |
| [08:54:58] | <mstenta[m]> | We could add the experimental flag to it to make it clear that it's not necessarily ready for wide use |
| [08:55:00] | <symbioquine[m]> | mstenta[m]: I've actually been waiting for this since I have some small engines that I use a time-tracking app for tracking hours on - that really should be in farmOS. |
| [08:55:29] | <mstenta[m]> | Oh cool |
| [08:56:07] | <mstenta[m]> | I'm realizing that there are a few "merge requests" on drupal.org issues that have slipped between the cracks, since we mostly use Github PRs... so maybe worth converting them to PRs |
| [08:56:13] | <mstenta[m]> | We could consider lining this one up for 3.4.0 |
| [10:21:28] | <symbioquine[m]> | Sadly I'll be missing the dev call today 😮💨 |
| [10:23:35] | <mstenta[m]> | You will be missed symbioquine ! |
| [13:03:12] | * melioristicmarie[m] has joined #farmos |
| [17:01:15] | * Juliet[m] has joined #farmos |
| [17:03:28] | <Juliet[m]> | hey farmOS chat :) |
| [17:03:28] | <Juliet[m]> | I'm here because i'm having a forum issue. I have to post notes from today's convention call to the forum, but I'm a "new" poster and can't get more than 2 links in. |
| [17:04:04] | <Juliet[m]> | Is there a setting that can bypass this? or should I try to pull out my links? |
| [17:29:30] | <mstenta[m]> | Juliet: Ah! I can probably fix that by raising your trust level! |
| [17:29:59] | <mstenta[m]> | Unfortunately I'm out and don't have forum log in on my phone :-( |
| [18:38:15] | <mstenta[m]> | Give it a try now Juliet :-) |