IRC logs for #farmOS, 2023-04-13 (GMT)

2023-04-12
2023-04-14
TimeNickMessage
[05:00:07]* ian_vai[m] has quit (Quit: You have been kicked for being idle)
[05:35:23]* evered[m] has quit (Read error: Connection reset by peer)
[05:35:23]* buddysbestfarm[m has quit (Read error: Connection reset by peer)
[05:35:24]* Mo[m] has quit (Read error: Connection reset by peer)
[05:35:24]* spitz234[m] has quit (Write error: Connection reset by peer)
[05:35:24]* workingjb[m] has quit (Read error: Connection reset by peer)
[05:35:26]* lordeddi[m] has quit (Read error: Connection reset by peer)
[05:35:26]* JasonJoe[m] has quit (Read error: Connection reset by peer)
[05:35:27]* threewordchant has quit (Read error: Connection reset by peer)
[05:35:27]* calbasi[m] has quit (Read error: Connection reset by peer)
[05:35:27]* jgaehring[m] has quit (Read error: Connection reset by peer)
[05:35:27]* symbioquine[m] has quit (Read error: Connection reset by peer)
[05:35:27]* wotnak[m] has quit (Read error: Connection reset by peer)
[05:35:27]* scrdcow[m] has quit (Write error: Connection reset by peer)
[05:35:27]* FarmerEd[m] has quit (Read error: Connection reset by peer)
[05:35:28]* jsoons[m] has quit (Write error: Connection reset by peer)
[05:35:28]* oswald[m] has quit (Read error: Connection reset by peer)
[05:35:28]* yahtu[m] has quit (Write error: Connection reset by peer)
[05:35:28]* paul121[m] has quit (Read error: Connection reset by peer)
[05:35:29]* mstenta[m] has quit (Read error: Connection reset by peer)
[05:39:08]* calbasi[m] has joined #farmos
[05:39:29]* calbasi[m] has quit (Remote host closed the connection)
[05:41:49]* calbasi[m] has joined #farmos
[05:50:42]* scrdcow[m] has joined #farmos
[05:50:42]* lordeddi[m] has joined #farmos
[05:50:42]* spitz234[m] has joined #farmos
[05:50:42]* jsoons[m] has joined #farmos
[05:50:42]* yahtu[m] has joined #farmos
[05:50:54]* JasonJoe[m] has joined #farmos
[05:50:54]* Mo[m] has joined #farmos
[05:50:54]* jgaehring[m] has joined #farmos
[05:50:54]* mstenta[m] has joined #farmos
[05:50:54]* wotnak[m] has joined #farmos
[05:50:54]* workingjb[m] has joined #farmos
[05:50:54]* buddysbestfarm[m has joined #farmos
[05:50:54]* evered[m] has joined #farmos
[05:50:54]* FarmerEd[m] has joined #farmos
[05:50:54]* oswald[m] has joined #farmos
[05:50:55]* toino[m] has joined #farmos
[05:50:55]* symbioquine[m] has joined #farmos
[05:50:55]* paul121[m] has joined #farmos
[05:50:55]* dazinism[m] has joined #farmos
[05:50:56]* threewordchant has joined #farmos
[06:17:01]* wotnak[m] has quit (Ping timeout: 240 seconds)
[06:17:01]* workingjb[m] has quit (Ping timeout: 240 seconds)
[06:17:08]* spitz234[m] has quit (Ping timeout: 252 seconds)
[06:17:15]* dazinism[m] has quit (Ping timeout: 248 seconds)
[06:17:15]* buddysbestfarm[m has quit (Ping timeout: 248 seconds)
[06:17:15]* evered[m] has quit (Ping timeout: 248 seconds)
[06:17:20]* JasonJoe[m] has quit (Ping timeout: 246 seconds)
[06:17:24]* toino[m] has quit (Ping timeout: 246 seconds)
[06:17:24]* scrdcow[m] has quit (Ping timeout: 246 seconds)
[06:17:24]* jsoons[m] has quit (Ping timeout: 246 seconds)
[06:17:30]* lordeddi[m] has quit (Ping timeout: 252 seconds)
[06:17:30]* calbasi[m] has quit (Ping timeout: 252 seconds)
[06:17:30]* yahtu[m] has quit (Ping timeout: 252 seconds)
[06:17:43]* threewordchant has quit (Ping timeout: 265 seconds)
[06:17:43]* Mo[m] has quit (Ping timeout: 265 seconds)
[06:17:46]* FarmerEd[m] has quit (Ping timeout: 265 seconds)
[06:17:46]* oswald[m] has quit (Ping timeout: 265 seconds)
[06:17:47]* symbioquine[m] has quit (Ping timeout: 256 seconds)
[06:17:47]* paul121[m] has quit (Ping timeout: 256 seconds)
[06:17:47]* jgaehring[m] has quit (Ping timeout: 256 seconds)
[06:17:47]* mstenta[m] has quit (Ping timeout: 256 seconds)
[06:23:06]* threewordchant has joined #farmos
[06:23:24]* jsoons[m] has joined #farmos
[06:36:20]* spitz234[m] has joined #farmos
[06:41:23]* workingjb[m] has joined #farmos
[06:41:32]* wotnak[m] has joined #farmos
[06:44:03]* evered[m] has joined #farmos
[06:44:24]* buddysbestfarm[m has joined #farmos
[06:44:49]* dazinism[m] has joined #farmos
[06:53:33]* JasonJoe[m] has joined #farmos
[06:57:04]* toino[m] has joined #farmos
[06:57:40]* scrdcow[m] has joined #farmos
[07:00:28]* Mo[m] has joined #farmos
[07:01:37]* calbasi[m] has joined #farmos
[07:02:39]* oswald[m] has joined #farmos
[07:02:40]* FarmerEd[m] has joined #farmos
[07:04:14]* paul121[m] has joined #farmos
[07:04:20]* jgaehring[m] has joined #farmos
[07:04:20]* symbioquine[m] has joined #farmos
[07:05:12]* mstenta[m] has joined #farmos
[07:11:39]* yahtu[m] has joined #farmos
[07:13:09]* lordeddi[m] has joined #farmos
[07:32:19]* lordeddi[m] has quit (Read error: Connection reset by peer)
[07:32:19]* spitz234[m] has quit (Write error: Connection reset by peer)
[07:32:19]* workingjb[m] has quit (Read error: Connection reset by peer)
[07:32:19]* calbasi[m] has quit (Read error: Connection reset by peer)
[07:32:20]* yahtu[m] has quit (Write error: Connection reset by peer)
[07:32:20]* symbioquine[m] has quit (Read error: Connection reset by peer)
[07:32:21]* FarmerEd[m] has quit (Remote host closed the connection)
[07:32:21]* paul121[m] has quit (Remote host closed the connection)
[07:32:21]* jgaehring[m] has quit (Read error: Connection reset by peer)
[07:32:22]* buddysbestfarm[m has quit (Remote host closed the connection)
[07:32:22]* wotnak[m] has quit (Remote host closed the connection)
[07:32:22]* mstenta[m] has quit (Write error: Connection reset by peer)
[07:32:23]* evered[m] has quit (Remote host closed the connection)
[07:32:23]* toino[m] has quit (Remote host closed the connection)
[07:32:23]* JasonJoe[m] has quit (Remote host closed the connection)
[07:32:23]* dazinism[m] has quit (Remote host closed the connection)
[07:32:23]* oswald[m] has quit (Remote host closed the connection)
[07:32:23]* scrdcow[m] has quit (Read error: Connection reset by peer)
[07:32:23]* Mo[m] has quit (Read error: Connection reset by peer)
[07:32:23]* threewordchant has quit (Read error: Connection reset by peer)
[07:32:23]* jsoons[m] has quit (Read error: Connection reset by peer)
[07:35:29]* calbasi[m] has joined #farmos
[07:44:22]* scrdcow[m] has joined #farmos
[07:44:22]* lordeddi[m] has joined #farmos
[07:44:22]* spitz234[m] has joined #farmos
[07:44:22]* jsoons[m] has joined #farmos
[07:44:22]* yahtu[m] has joined #farmos
[07:44:34]* JasonJoe[m] has joined #farmos
[07:44:34]* oswald[m] has joined #farmos
[07:44:34]* wotnak[m] has joined #farmos
[07:44:34]* mstenta[m] has joined #farmos
[07:44:34]* paul121[m] has joined #farmos
[07:44:34]* evered[m] has joined #farmos
[07:44:34]* FarmerEd[m] has joined #farmos
[07:44:34]* jgaehring[m] has joined #farmos
[07:44:35]* toino[m] has joined #farmos
[07:44:35]* Mo[m] has joined #farmos
[07:44:35]* buddysbestfarm[m has joined #farmos
[07:44:35]* workingjb[m] has joined #farmos
[07:44:35]* symbioquine[m] has joined #farmos
[07:44:36]* dazinism[m] has joined #farmos
[07:44:36]* threewordchant has joined #farmos
[09:02:56]<evered[m]>Yay team!!!
[09:03:16]<evered[m]>Good morning left coast of the USA
[09:17:25]<toino[m]>Hello everyone, I installed farm a year ago and tried it for a bit just on my own but I was never able to proxy it using the nginx proxy manager I already had installed in my server, from what I found I had to change some config somewhere but I never ended up figuring it out.... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/0b302b0227...)
[09:17:41]<toino[m]>s/farm/Farmos/
[09:18:26]<mstenta[m]>toino: You could try searching for "Drupal behind Nginx proxy" for more generic tutorials
[09:18:39]<mstenta[m]>farmOS is just a distribution of Drupal, so all the same considerations apply
[09:26:54]<toino[m]><mstenta[m]> "toino: You could try searching..." <- Thanks, I remembered, the problem I was having was I couldn't find the settings.php file to make the changes, it was a while ago and I was a complete noob using docker.
[09:26:54]<toino[m]>Going to try installing it again this week when I have time.
[09:28:33]<mstenta[m]>Cool! Well feel free to check back in and ask questions as you're getting into it again :-)
[11:04:31]<lordeddi[m]>Hi, will be missing this dev-call, i'm way too busy. Hope to be back soon! keep up the great work.
[11:09:11]<mstenta[m]>Sounds good lordeddi - see you another time! :-)
[11:55:08]<mstenta[m]>Dev call in ~5 minutes - all are welcome! https://meet.jit.si/farmos-dev
[13:17:07]<mstenta[m]>After the discussion on the dev call, I'm leaning towards maybe making the comment module in contrib instead of core as a first step
[13:17:22]<mstenta[m]>Curious your thoughts symbioquine because you expressed interest in it earlier
[13:17:41]<mstenta[m]>The main motivation for working on it was because Rothamsted wanted comments in their experiment plans
[13:17:51]<mstenta[m]>But they may not necessarily need/want them on assets/logs
[13:18:06]<mstenta[m]>So it might make more sense to just implement their stuff independently
[13:18:20]<mstenta[m]>And give it more thought for assets/logs in core
[13:22:10]<symbioquine[m]>mstenta[m]: Makes sense to me
[13:22:25]<symbioquine[m]>I think the main use-case for us would be on logs since on assets you can always make an observation log and put the comments in the notes...
[13:23:36]<mstenta[m]>And is the main usefulness of comments on logs the fact that you can capture the author nor granularly?
[14:00:58]<symbioquine[m]>I think time/author are pretty useful
[14:02:29]<symbioquine[m]>e.g. a log created for planning purposes that we later make some notes about - if those notes go into the log's notes field, then you'd have to look at the revisions to figure out who did it and what was added/changed/removed
[14:03:17]<symbioquine[m]>comments could provide a pretty well understood mechanism for purely adding information chronologically to a log
[14:04:20]<symbioquine[m]>It also has clearer semantics for concurrent contributions from multiple people
[14:04:38]<symbioquine[m]>i.e. two people can't edit a log at the same time, but there's not problem with two people posting comments at the same time
[14:05:13]<paul121[m]>(maybe we need a "quick log" UI, similar to comment UI, for quickly making observation logs for an asset)
[14:05:14]<symbioquine[m]>s/not/no/
[14:05:15]<symbioquine[m]> * i.e. two people can't edit a log at the same time, but there's no problem with two people posting comments at the same time (presumably)
[14:05:42]<symbioquine[m]>And showing them inline somehow?
[14:05:51]<paul121[m]>is there not any use-case for comments on an asset?
[14:06:40]<paul121[m]>I feel like you might ask a "question" about the tractor, leave a comment, and keep the history there
[14:07:29]<symbioquine[m]>Yeah, but the expectations about the life-cycle of such comments isn't very clear...
[14:07:52]<symbioquine[m]>How long is that question useful? Will it show up for the whole time the tractor exists?
[14:08:50]<mstenta[m]>Maybe allowing for comments to be "archived" or something... which just collapses them in the UI
[14:08:57]<mstenta[m]>Similar to Github issues
[14:09:13]<mstenta[m]>Or PR reviews I mean
[14:10:18]<mstenta[m]>I think its important to frame comments as useful for *discussions*, not management data
[14:17:50]<mstenta[m]>> After the discussion on the dev call, I'm leaning towards maybe making the comment module in contrib instead of core as a first step
[14:17:50]<mstenta[m]>Another option is add it to core, but don't "open" comments on all assets and logs by default. We could add configuration for the default (eg: allow admin to say "sure open comments on all assets/logs by default"). And either way they can be opened/closed on individual assets/logs
[14:18:29]<mstenta[m]>Could even make it configurable on a per-bundle basis
[14:18:30]<mstenta[m]>So you could open comments on all activity logs by default, but not harvest... or whatever you want
[14:19:01]<mstenta[m]>that would be sort of a "soft enable" strategy...
[14:19:06]<symbioquine[m]>How would that look from the API?
[14:19:25]<mstenta[m]>so eg: Rothamsted (who wants comments but doesn't necessarily want them on assets/logs) can add them to their own entity types
[14:20:10]<mstenta[m]>from the API, basically every asset and log will have a new comment base field on them, which is either 0 (hidden), 1 (comments closed), or 2 (comments open)
[14:20:35]<mstenta[m]>my branch currently just sets the default to 2 for assets and logs
[14:20:41]<mstenta[m]>(open comments as soon as you enable the module)
[14:20:54]<mstenta[m]>but we could make that more nuanced, is what i'm saying
[14:21:31]<symbioquine[m]>mstenta[m]: Beautiful
[14:21:48]<symbioquine[m]>... and I assume you then query comment entities if you want to see the existing comments?
[14:21:51]<mstenta[m]>that's just the core Drupal comment module behavior basically
[14:22:03]<mstenta[m]>yes exactly. comments are their own entity
[14:22:24]<mstenta[m]>i assume the comment entity references the entity they are attached to
[14:22:30]<mstenta[m]>but i haven't looked at that closely
[14:23:06]<paul121[m]>it's a reverse entity reference, yea?
[14:26:02]<mstenta[m]>https://git.drupalcode.org/project/drupal/-/blob/10.1.x/core/modules/com...
[14:26:16]<mstenta[m]>looks like just a normal entity reference field on the comment, pointed to the entity
[14:27:46]<mstenta[m]>Opened a draft PR: https://github.com/farmOS/farmOS/pull/668
[14:27:54]<paul121[m]>oh right. but in the context of our entities it is reverse :-)
[14:27:54]<mstenta[m]>This is VERY mvp
[14:28:23]<mstenta[m]>paul121: works basically the same way logs do... they reference assets :-)
[14:30:31]<paul121[m]>yeaaa I just think of "comments being apart of asset" much more than "log being a part of asset"
[14:30:42]<mstenta[m]>right yea that's true...
[14:30:47]<mstenta[m]>and a log can reference multiple assets
[14:30:51]<paul121[m]>but it makes sense, I think it is better in this case
[14:30:51]<mstenta[m]>so not exactly the same thing
[14:32:03]<paul121[m]>this starts to get into where our data model maybe includes "application specific" things that wouldn't be a part of a larger "standard data model". so in that regard it's nice & cleaner that comments are as nested inside the `relationships`
[14:32:28]<mstenta[m]>are they?
[14:32:59]<mstenta[m]>i haven't looked at that
[14:33:15]<mstenta[m]>there is a comment in attributes which is just whether or not comments are enabled
[14:33:15]<paul121[m]>oh
[14:33:15]<mstenta[m]>not sure about relationships...
[14:33:16]<paul121[m]>I was assuming
[14:33:28]<paul121[m]>I would be surprised. Because that would be another field
[14:48:47]<mstenta[m]>> > After the discussion on the dev call, I'm leaning towards maybe making the comment module in contrib instead of core as a first step
[14:48:47]<mstenta[m]>>
[14:48:47]<mstenta[m]>> Another option is add it to core, but don't "open" comments on all assets and logs by default. We could add configuration for the default (eg: allow admin to say "sure open comments on all assets/logs by default"). And either way they can be opened/closed on individual assets/logs
[14:48:47]<mstenta[m]>Quick sketch of what I meant by this:
[14:48:56]<mstenta[m]>ACTION uploaded an image: (125KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/sbjCMuBtyNw... >
[14:50:00]<mstenta[m]>And maybe they are all unchecked by default. So enabling the farm_comment module wouldn't actually change anything in the UI by default. Then an admin could change the default behavior on a per-type basis using this form OR users could open comments on individual assets/logs as desired.
[15:35:26]<mstenta[m]>Hmm actually that may be more complicated than it's worth...
[15:41:33]<mstenta[m]>This is doable though:
[15:41:41]<mstenta[m]>ACTION uploaded an image: (85KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/xSDhFzSKEmD... >
[15:41:55]<mstenta[m]>(needs some word-smithing... but you get the idea)
[15:43:22]<mstenta[m]>Hmm although it will require a cache rebuild on save... ๐Ÿค”
[15:44:10]<toino[m]>Happy to report back i got the reverse proxy working within 15 minutes with the help of chatgpt, way better at showing me only what is needed to do.
[15:44:10]<toino[m]>Any downsides to using the SQLite DB instead of the Postgres one?
[15:44:21]<mstenta[m]>haha awesome toino
[15:45:25]<mstenta[m]>I haven't used SQLite db backend much myself, so I'm not really sure. Probably some performance differences, but I don't know how noticeable that will be.
[15:45:28]<toino[m]>One more thing any way to import cattle with excel/csv files?
[15:45:47]<mstenta[m]>Not via the UI, but you could build a CSV importer Python script
[15:45:54]<mstenta[m]>https://farmos.org/blog/2023/quick-intro-to-python-scripting
[15:46:07]<toino[m]>mstenta[m]: Way above my pay grade๐Ÿ˜‚
[15:46:24]<mstenta[m]>this example sounds like what you're looking for: https://farmos.org/blog/2023/quick-intro-to-python-scripting#importing-data
[15:46:31]<toino[m]>Thanks anyway, just testing/having fun
[15:47:06]<mstenta[m]>I'd love to offer some flexible CSV importers in the UI eventually... we had those in farmOS v1, but it's a big dev effort to do it right
[15:47:16]<toino[m]>mstenta[m]: Well now that looks doable with my pay grade
[15:47:49]<mstenta[m]>Awesome! Just make sure you test it thoroughly on a non-production database first
[15:47:58]<toino[m]>I wanted to ask another thing but i forgot
[15:48:02]<mstenta[m]>Spin up two instances and use one for testing
[15:48:39]<toino[m]>This is nothing critical so no problem with it, if it brake i will reinstall it again.
[15:49:40]<FarmerEd[m]>I've some Node-Red flows for importing cattle from CSV if you want to explore that.
[15:49:57]<toino[m]>ACTION uploaded an image: (60KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/hCcnqxhbPyJ... >
[15:49:59]<toino[m]>Just remembered i noticed the PT-pt translation is only at 97% and the main Tabs are all still in english is this something that can't be changed or do you just needs someone that can translate stuff?
[15:50:54]<toino[m]>Im not the best with english as you can see by my typing but still good enought to translate it to Portguese on my free time
[15:52:22]<toino[m]>FarmerEd[m]: Never used Node-Red but i think i heard about it, is it the visual programming thing for IOT or am i mistaken?
[15:54:15]<mstenta[m]>> Just remembered i noticed the PT-pt translation is only at 97% and the main Tabs are all still in english is this something that can't be changed or do you just needs someone that can translate stuff?
[15:54:15]<mstenta[m]>we'd love help with translations!
[15:54:30]<mstenta[m]>it's essentially a process of contributing translations to localize.drupal.org
[15:54:47]<mstenta[m]>so it doesn't actually require any work from the core farmOS maintainers
[15:55:21]<mstenta[m]>but it does require work from you to make a user account on localize.drupal.org, join the group for your language, contribute translations, and get them approved by an admin of that language group
[15:55:35]<mstenta[m]>but once that happens, they will download automatically into any instance that uses that language
[15:56:15]<toino[m]>mstenta[m]: Thats not that bad, only problem is that website doesn't load
[15:56:32]<toino[m]>it took a while
[15:56:37]<mstenta[m]>https://localize.drupal.org/translate/languages/pt-pt/translate?project=...
[15:57:39]<FarmerEd[m]><toino[m]> "Never used Node-Red but i..." <- Yes, a visual/ low code programing thing commonly used for IOT but also useful for interacting with API's
[15:57:46]<mstenta[m]>doing it through the localize.drupal.org site is a little more direct... but there's a LOT of strings in there... so might be worth jumping back and forth between that and your instance and searching for the strings that are most important to you
[15:58:23]<mstenta[m]>there's also modules you can use to translate directly in the farmOS UI... but i don't have much experience with that, and i don't have a great understanding of the flow to localize.drupal.org
[15:58:38]<toino[m]>Just noticed that some translations were right but later overwriten with english text, do you know why?
[15:58:39]<toino[m]>ACTION uploaded an image: (8KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/kAyTgtNOFiS... >
[15:58:45]<mstenta[m]>anything you do in your instance only benefits you... so i always try to encouraging helping the wider community when possible :-)
[15:59:35]<mstenta[m]>i don't know - i'm not entirely familiar with the process on localize.drupal.org
[16:00:28]<mstenta[m]>ACTION uploaded an image: (19KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/lzLcMbbnpkc... >
[16:00:59]<mstenta[m]>looks like ricardoamaro did that...
[16:01:00]<mstenta[m]>on 2/24/2023
[16:01:03]<mstenta[m]>demoted the correct one and imported+approved the english one...
[16:02:41]<mstenta[m]>if you want to pursue it, i would ask in Drupal Slack #multilingual channel https://app.slack.com/client/T06GX3JTS/C55J600UX
[16:02:48]<toino[m]>mstenta[m]: It makes no sense, translations are supposed to help those who can't understand english, why change something in Portuguese to English
[16:03:36]<mstenta[m]>localize.drupal.org is a volunteer effort... someone probably made ricardoamaro and admin and then they did that... which was wrong
[16:03:36]<mstenta[m]>maybe you can ask to be an admin and fix it
[16:03:40]<toino[m]>mstenta[m]: Will do for sure, even if i only do the main stuff it will help someone for sure
[16:04:06]<mstenta[m]>i'm not sure what the process of becoming and admin is... you probably need to prove that you aren't a malicious actor somehow...
[16:04:28]<toino[m]>Trust me bro rule ๐Ÿ˜‚
[16:04:56]<mstenta[m]>i remember another farmOS user helped translate to german... they basically submitted a bunch of translations, and then opened an issue for a german admin to review them - and it went pretty smoothly!
[16:05:02]<toino[m]>Probably need to translate a couple of stuff correctly before giving me admin
[16:05:05]<mstenta[m]>i'll see if i can find that issue so you can see what it looked like
[16:05:54]<mstenta[m]>https://www.drupal.org/project/de/issues/3261927
[16:07:41]<toino[m]>Thanks i will check it later.
[16:18:11]<toino[m]>Any known reason why i can login without any problems on the website but when I try it in the field kit farmos.app i get a error Request failed with status code 500ร—
[16:18:30]<mstenta[m]>couple of things...
[16:18:41]<mstenta[m]>you need to enable the field kit module in farmOS
[16:19:12]<mstenta[m]>but more broadly... field kit is still in development and there aren't any field modules included yet
[16:19:22]<mstenta[m]>so you're in experimental territory :-)
[16:19:57]<toino[m]>field kit module enabled i think, atleast i enabled it in the inicial setup
[16:21:55]<mstenta[m]>ah ok - maybe you need SSL? i forget - it's been a long time since i helped with field kit testing
[16:22:28]<mstenta[m]>status code 500 is a good clue though
[16:22:39]<toino[m]>Already using ssl and https
[16:22:39]<mstenta[m]>usually those get logged in /admin/reports/dblog
[16:22:43]<mstenta[m]>so you might get more detail there
[17:49:31]<mstenta[m]>symbioquine: new idea... talking with paul121 about comments...
[17:51:03]<mstenta[m]>we make two main modules (and one lower-level dependency module): "Asset comments" (`farm_comment_asset`) and "Log comments" (`farm_comment_log`) which depend on `farm_comment` (provides helpers and general comment glue stuff)
[17:51:21]<mstenta[m]>this way, users would choose whether to enable comments on Assets, Logs, or both by enabling either/both module
[17:52:07]<mstenta[m]>and other modules (like Rothamsted) could enable comments on their own entity types using the same helpers from farm_comment (without necessarily enabling them on assets/logs)
[17:52:24]<mstenta[m]>seems like the easiest way to juggle these things