| [19:06:15] | * Fosten has joined #farmos |
| [20:03:48] | * Fosten has quit (Quit: Leaving.) |
| [20:57:38] | * Fosten has joined #farmos |
| [00:42:05] | * Fosten has quit (Quit: Leaving.) |
| [01:04:42] | * Fosten has joined #farmos |
| [02:32:27] | * Fosten has quit (Quit: Leaving.) |
| [03:35:23] | * Fosten has joined #farmos |
| [07:24:56] | * Fosten has quit (Quit: Leaving.) |
| [08:04:41] | * Fosten has joined #farmos |
| [09:01:23] | * Fosten has quit (Quit: Leaving.) |
| [12:55:27] | <mstenta[m]> | Who wants to learn some farmOS module development? :-D |
| [12:55:52] | <mstenta[m]> | Got some pretty small improvements to the Planting Quick Form that would be great introductory tasks... |
| [12:56:05] | <mstenta[m]> | https://www.drupal.org/project/farm/issues/3023723 |
| [12:56:08] | <mstenta[m]> | https://www.drupal.org/project/farm/issues/3023724 |
| [13:43:53] | <paul121[m]> | I would be interested in that. Some of those naming issues have come to my mind as well.. |
| [13:45:27] | <paul121[m]> | Thinking from the diversified vegetable perspective having many successions. Almost need a unique ID in the name! |
| [13:47:17] | * farmBOT has joined #farmos |
| [13:47:18] | <mstenta[m]> | paul121: Oh good point! That reminds me: https://www.drupal.org/project/farm/issues/2934743 |
| [14:02:56] | <paul121[m]> | Successions! Nice. Would be great with a planner tool. Gets me thinking.. |
| [14:02:58] | <paul121[m]> | Could the succession # be autofilled as well? Seems like you could base it off of the # of previous plantings of the same crop in a given season. Auto increment by 1, or override |
| [14:09:25] | <mstenta[m]> | paul121: yea that's sort of what i was thinking in my first comment on that... |
| [14:09:27] | <mstenta[m]> | > This would be a nice step towards a more elaborate "succession planner" in the future too. The planner could auto-populate the Succession field when it generates planting assets. |
| [14:09:57] | <mstenta[m]> | The idea there would be to have something like the planting quick form, but for generating multiple plantings (multiple successions) |
| [14:10:54] | <mstenta[m]> | Ultimately, I'd love to use the new "plan" entity type to organize all the successions and enable managing them together |
| [14:11:32] | <mstenta[m]> | That's sort of the missing link between "quick forms" and "plan entities" in farmOS... but where we can take it in the future... quick forms only create new records right now, and can't be used to edit/manage existing records |
| [14:11:46] | <mstenta[m]> | But a "plan entity" is a good way to approach that... and that's what we did with the Grazing module |
| [14:12:05] | <mstenta[m]> | (For managing animals and their movement logs all under the umbrella of a single "grazing plan") |
| [14:13:06] | <mstenta[m]> | So essentially: "quick forms as a UI feature of a plan" |
| [14:58:55] | <paul121[m]> | @mstenta:matrix.org: |
| [14:58:55] | <paul121[m]> | > That's sort of the missing link between "quick forms" and "plan entities" in farmOS... but where we can take it in the future... quick forms only create new records right now, and can't be used to edit/manage existing records |
| [14:58:56] | <paul121[m]> | Makes sense. A good use case for plans, too |
| [15:03:01] | <paul121[m]> | I'm on the road travelling over the next few days but can be thinking about the quick form issues. Like you said, would be a good proj to start work on |
| [15:06:55] | <mstenta[m]> | paul121: Cool! Let me know if you need help getting set up with a dev environment. I would recommend https://farmos.org/development/docker/ |
| [15:07:25] | <mstenta[m]> | And here's where the planting quick form code resides: |
| [15:07:26] | <mstenta[m]> | https://github.com/farmOS/farmOS/blob/7.x-1.x/modules/farm/farm_crop/far... |
| [15:27:06] | <jgaehring[m]> | mstenta: if you ever have a real softball of an issue, i sure wouldn't mind taking a crack at some module dev, just to get a little better grounding in the PHP / Drupal side of things... super basic though, since my PHP experience === null |
| [15:31:09] | <mstenta[m]> | jgaehring: either of those two above are pretty easy - in the sense that they would be limited to changes in a single file, and don't require a whole lot of knowledge of Drupal/farmOS |
| [15:31:25] | <mstenta[m]> | They are mostly tweaks to the existing quick form code, which uses Drupal's Form API |
| [15:32:11] | <mstenta[m]> | It would be great to organize a collection of small issues like those, so others could easily jump in and get their feet wet |
| [15:34:42] | <jgaehring[m]> | cool, well paul121 has dibs and I certainly have enough to chew on myself at the moment |
| [15:39:42] | <jgaehring[m]> | have you seen this? https://www.firsttimersonly.com/ |
| [15:40:31] | <jgaehring[m]> | good-first-issue is a tag I see used a lot too |
| [15:43:04] | <mstenta[m]> | Cool! Yea I've seen similar labels used on Github |
| [15:45:15] | <jgaehring[m]> | https://up-for-grabs.net/#/ too |
| [15:45:28] | <jgaehring[m]> | wow, there are a lot of aggregators for those |
| [16:35:27] | <paul121[m]> | @jgaehring:matrix.org: sounds like some cool sites. Feel free to jump on either if you get the urge! @mstenta:matrix.org I agree, it would be good to do some tagging of that sort |