| [13:38:20] | <tool172[m]> | mstenta: should I fork or contribute to the grazing plan module? I am going to flip it to build the data without forcing the end and auto inputting the end on a movement to a new location and marking it done in quick forms with some other data like Time in area, etc, that will draw up averages with Animal units etc. What's the proper method these days? |
| [13:38:30] | <tool172[m]> | I also went ahead and took care of the dashed line and color selection custom/module that is done. |
| [13:38:54] | <tool172[m]> | adds two options stored with the aset for js styling |
| [14:09:45] | <mstenta[m]> | tool172: The first step of contributing to a module is forking the repo - so go ahead and fork! |
| [14:10:11] | <mstenta[m]> | Then you can work on your changes, and if you want to contribute anything back you can open a pull request. |
| [14:10:12] | <tool172[m]> | mstenta[m]: cool |
| [14:10:20] | <mstenta[m]> | Pull requests should be small and focused on on change at a time |
| [14:10:25] | <mstenta[m]> | one* |
| [14:10:53] | <mstenta[m]> | You can also choose to just go off on your own path with it, and not contribute back if you start making big changes and it just makes sense to stay separate |
| [14:11:08] | <mstenta[m]> | Just know that you will stop losing the maintenance benefit of the original |
| [14:11:26] | <tool172[m]> | ok |
| [14:11:26] | <mstenta[m]> | (eg: if I update new versions you'll need to figure out how to merge those changes into your fork) |
| [14:11:43] | <tool172[m]> | all my stuff is 4.0x right now ready and doesn't overwrite FarmOS core |
| [14:11:53] | <mstenta[m]> | great |