| [22:30:35] | * JustTB1 has quit (Ping timeout: 246 seconds) |
| [22:45:20] | * JustTB has joined #farmos |
| [01:50:19] | <MockingbirdConsu> | A question about contributing - should I be using the code and issue trackers from drupal.org or github.com? I searched the site but couldn't find a definitive answer? |
| [04:57:15] | * ludwa6 has joined #farmos |
| [07:02:39] | <mstenta[m]> | Mockingbird Consulting: I generally use the drupal.org issue tracker for farmOS core development, but GitHub is a good starting place for discussion etc before I create an official issue on d.o |
| [07:03:07] | <mstenta[m]> | GitHub is used for the mobile app, and farmOS libraries |
| [07:03:24] | <mstenta[m]> | So depends on what you're working on... |
| [07:04:22] | <MockingbirdConsu> | ok, thanks. I'm going to brush up on my PHP and see what I can do about the sensor data issues I logged the other day. It might take me a while, I just want to know which repo to clone from to work on farmos itself! |
| [07:04:31] | <mstenta[m]> | Historically it all started on d.o, but more people are familiar with GitHub, so whatever works :-) |
| [07:04:45] | <mstenta[m]> | Awesome! |
| [07:05:28] | <MockingbirdConsu> | heh, I've got code spread across bitbucket, github, gitlab, and a load of "in-house" git servers only accessible via a dedicated VPN for each client, so I have no preference ;) |
| [07:06:07] | <mstenta[m]> | Well if you work in a new module you can do it in a new GitHub repo if you want |
| [07:06:25] | <mstenta[m]> | That might be a good way of experimenting |
| [07:09:43] | <MockingbirdConsu> | ok, cool, I'll have a look at that then :) |
| [07:12:39] | <MockingbirdConsu> | like I say, the last time I used PHP was just as it moved from v4 to v5, and I've been pretty much pure python since then, so it might take a while to get back up to speed, but as soon as I've got something I'll let you know! |
| [07:13:17] | <mstenta[m]> | Awesome! Well if you need examples let me know |
| [07:13:27] | <mstenta[m]> | I can point to places in the farmOS codebase |
| [07:13:37] | <mstenta[m]> | If that helps |
| [07:14:00] | <MockingbirdConsu> | It definitely will, let me re-learn PHP first though! :D Is there a good "crash course" you can recommend? |
| [07:14:25] | <mstenta[m]> | It will probably be more of a process of learning Drupal |
| [07:14:36] | <mstenta[m]> | For better or worse :-) |
| [10:21:11] | <ludwa6> | g’day room. Anyone got a min or few to help a n00b get to first base with setting up a simple planting in farmOS? |
| [10:22:02] | <mstenta[m]> | ludwa6: I'm on the road right now, but have you seen the planting quick form? |
| [10:22:17] | <mstenta[m]> | Go to /farm/quick |
| [10:22:22] | <mstenta[m]> | You might need to enable it |
| [10:22:49] | <ludwa6> | just did |
| [10:23:26] | <ludwa6> | cool. this looks much simpler than the form i was working with. it has all the essentials, and nothing but. |
| [10:24:03] | <mstenta[m]> | Great! Yea it's meant to cover the most common use case |
| [10:24:24] | <mstenta[m]> | And generate the seeding and/transplanting and/or harvest logs at the same time |
| [12:29:32] | <ludwa6> | Am starting to understand the taxonomy and mandatory relations about Planting -which involves a particular instance of a Crop being introduced to a Field in a particular Season, IIRC- but does this same logic apply in case of perennial plantations, such as an orchard or vineyard? Should i set them up that way (retroactively, because my orchards and vineyards are many years old), and then just do operations on the same Planting, year |
| [12:29:33] | <ludwa6> | after year? Or do i create a new Planting (even tho it’s the same plants) after each fruit harvest, so that subsequent operations (e.g. pruning that follows soon after fruit harvest) is considered as related to the next crop (oops: Crop means species/ variety, i gather) of fruit? |
| [13:39:45] | * JustTB has left #farmos () |
| [13:48:12] | <mstenta[m]> | ludwa6: yea! You can use a planting asset to represent a perennial |
| [13:48:42] | <mstenta[m]> | Crop/variety is the "type" of planting... So to speak |
| [13:49:19] | <mstenta[m]> | So for example: you might have a Crop/variety called Strawberries |
| [13:49:32] | <mstenta[m]> | And a planting called South Garden Strawberries |
| [13:50:21] | <mstenta[m]> | Which references the Crop/variety "Strawberries" as it's type, and is located in "South Garden" (area) |
| [13:50:25] | * JustTB has joined #farmos |
| [13:50:48] | <mstenta[m]> | Then each year, you can record harvests from that planting |
| [13:51:04] | <mstenta[m]> | As "Harvest" logs |
| [14:10:15] | <ludwa6> | ok -so you would keep it as one Planting for as many years as the plant survives? i wonder if that compromises any details that might be important -for example in the case of wine grapes. The harvest of 2019 will be very different from that of 2018 (i hope! :-), depending on many factors, including the pruning of vines, treatments, weather of that year, etc. Are all those factors correlated with that particular Harvest somehow? |
| [14:14:46] | <mstenta[m]> | Yea I would still track it as the same planting |
| [14:15:43] | <mstenta[m]> | So that you can get a record of the yield of those vines over their whole lifetime |
| [14:16:11] | <mstenta[m]> | If you have harvest logs over many years, but you just want to see one year's, you can filter logs by date |
| [14:16:34] | <mstenta[m]> | But: it's up to you! |
| [14:16:56] | <mstenta[m]> | If you'd rather have one asset per year, you could do that too |
| [14:17:49] | <mstenta[m]> | I'm not sure that would be helpful, but nothing is stopping you from doing that, so if it helps you to organize things go for it! |
| [14:22:50] | <ludwa6> | nooo… i am way to clueless about how this software works to go using it in strange ways. i’m just looking for best practices to follow. |
| [14:30:45] | <mstenta[m]> | Haha fair enough |
| [14:35:02] | <ludwa6> | i’m looking right now at a pretty interesting implementation at https://perma-ledger.com |
| [14:35:50] | <ludwa6> | they seem to have a couple of extra datatypes in their Log list, that could be very useful in my case: Purchases and Sales. |
| [14:36:18] | <ludwa6> | is that a custom thing, i wonder? |
| [14:37:50] | <mstenta[m]> | Oh yea! Perma Ledger is maintained by another Mike :-) |
| [14:37:55] | <mstenta[m]> | Not sure if he's in this chat |
| [14:38:16] | <mstenta[m]> | But the Sale and Purchase logs are available in core farmOS |
| [14:38:37] | <mstenta[m]> | You just need to enable the Farm Ledger module for them to be available |
| [14:41:28] | <ludwa6> | so how does one enable Farm Ledger module? does that add much complexity? looks like a simple datatype - and if i could log purchases and sales, and export as .CSV periodically, that could make this a much more practical solution for me. |
| [15:15:55] | <mstenta[m]> | I forget are you self-hosting? Or Farmier? |
| [15:20:18] | <ludwa6> | farmier |
| [15:21:01] | <ludwa6> | 8 days left in trial :-) |
| [15:21:58] | <mstenta[m]> | Ok I can turn it on for you next time I'm at my computer |
| [15:23:18] | * farmBOT has joined #farmos |
| [15:23:20] | <ludwa6> | cool! will do, Mike, thanks a heap. |
| [15:26:23] | <ludwa6> | ACTION breaks for dinner |