The following list outlines the main farmOS project Git repositories and their associated issue queues. If you have a feature request or bug report, and you know what project it belongs in, feel free to create a new GitHub.com or Drupal.org issue in the appropriate queue. Otherwise, start a forum post or a GitHub issue in https://github.com/farmOS/farmOS/issues and the maintainers will help it find its place.
farmOS
This is the main farmOS project, which is the server-side code that stores records and provides UI for managing them.
The Drupal.org issue queue is the original and primary queue for farmOS. The GitHub queue is secondary, and serves as a starting place for some discussions before they are ultimately turned into official roadmap issues in Drupal.org.
farmOS Field Kit
This is the offline/mobile app that is packaged as a native Android/iOS app, and is also available as a progressive web app (PWA) on https://farmOS.app
Note that the above list does not include add-on modules for farmOS. A list of all farmOS core and community modules, see: https://farmos.org/development/projects/
Each of those will have its own repository and issue queue for feature requests and bug reports. If you are not sure where to submit new ideas/bugs, start a forum post, or create an issue in https://github.com/farmOS/farmOS/issues
@mstenta … you are the maintainer for the Bee module. So, you are a beekeeper, too?
That one is not listed as part of the distribution. Does that mean I would need a local installation to use and, possibly in the future, develop on it?
I did have some hives, but they did not survive last winter, sadly. I would like to again in the future!
That one is not listed as part of the distribution. Does that mean I would need a local installation to use and, possibly in the future, develop on it?
Do you have a farmOS instance on Farmier? If so I can enable the bee module on there for you. I just need to know your farmOS URL.
I just ran across your project today (thanks to the Red Had plug). It’s precisely project I have been dreaming of starting up. I was considering hacking on ERPNext but, this looks to be moving more in the ag direction. So, I’m all in. Winter is here so there should be time, now. Any direction you can point me to get up to speed would be helpful.
I’m an IT geek (Computer and Information Science degree) who knows how to do light programming. I started homesteading 8 years ago. I keep bees, raise broilers (Salatin style) and, of course, have egg layers. Pigs and dairy goats are on the list for next year. It’s my goal to retire from corporate life to the homestead. It would be great to bring my geek skills to it, too.
@samrose No it does not. But that would be a great thing to think about in the new version that @jgaehring is working on for farmOS 2.x. Or as a dedicated field module for inventory management perhaps.
Hi @samrose! Sorry I didn’t get back to this sooner, but I’ve been trying to get syncing working with 2.x for ages now, and been sitting on a ton of changes I hadn’t committed until today. It’s still super unstable, and the edit screens are still not working, but a lot of the internals are worked out. I’ll be updating my fork until an alpha is ready. It’s all on the v2-alpha branch for now:
Mike mentioned Field Modules, which will be the best way for you to extend Field Kit in the future. We put development of that module system on hold to get ready for farmOS 2.0, but it should be ready when Field Kit 2.0 is released. These docs are totally outdated, and the API will look very different, but you can get a sense of how it will work here:
I would like to again in the future!