IRC logs for #farmOS, 2018-03-01 (GMT)

2018-02-28
2018-03-02
TimeNickMessage
[20:13:44]* christinesu[m] has joined #farmos
[21:39:28]* JustTB has quit (Quit: Leaving.)
[21:46:41]* JustTB has joined #farmos
[22:22:51]* JustTB has quit (Ping timeout: 256 seconds)
[01:11:58]* plaasio[m] has joined #farmos
[05:40:08]* JustTB has joined #farmos
[06:24:33]* JustTB1 has joined #farmos
[06:25:36]* JustTB has quit (Quit: Leaving.)
[08:23:31]<dornawcox[m]>Discussion with LandPKS is leading toward much tighter integration with FarmOS and expanding landpks function as a mobile app "FarmOS light"
[08:25:28]<mstenta[m]>Oh interesting!
[08:25:32]<dornawcox[m]>LandPKS is particularly interested in coordinating with the mobile version of grazing module. Perhaps invite Jeff to dev conversation soon?
[08:25:46]<mstenta[m]>We should really coordinate - because we're already starting work on the mobile app.
[08:26:05]<mstenta[m]>And that's exactly what the plan is: a "farmOS light"
[08:26:12]<mstenta[m]>My vision is that farmOS (as it is now) will become the "farmOS Advanced" version
[08:26:46]<mstenta[m]>And the offline app (which will also be the native app) will offer simpler features to cover the main use-cases, and can be extended in the same way as current farmOS can via modules.
[08:28:02]<mstenta[m]>(Sent an invite to Jamie and Alex, who are spearheading that initiative)
[08:34:22]<dornawcox[m]>Excellent! If they can roll landpks as a observation app module together we will be well on our way!
[08:35:33]<mstenta[m]>It's entirely possible - if they've got resources to make that transition. LandPKS does a lot - so it would be a fair bit of work to migrate it all. But if they are really looking to rebase themselves onto farmOS then it makes a lot of sense!
[08:36:06]<mstenta[m]>Either that, or just leave their app as-is (separate app) with the same frontend, but change the backend to store data in farmOS.
[08:36:28]<mstenta[m]>The nice thing about farmOS-as-a-backend-db is that many apps could potentially be built that use it as a remote database.
[08:36:43]<mstenta[m]>All just using the REST API
[08:47:22]<dornawcox[m]>I expect the plan would, at first, keep the landpks front-end but overtime as new modules are added(they have a list) that it all be native FarmOS. Jeff was imagining an app/play store like setup for module selection to customize each farm.
[08:47:46]* cpm has joined #farmos
[08:48:30]<mstenta[m]>Cool!
[08:52:56]<cpm>so,
[08:53:00]<cpm>the annouce-list ?
[08:53:06]<cpm>just you and me.
[08:53:38]<cpm>FWIW, I'm migrating to a new email ecosystem. It will basically be the same, except with much stronger cryto and modern software. :)
[09:36:17]<mstenta[m]>Haha well that makes sense - we didn't really publicize it.
[09:37:07]<mstenta[m]>We may not really need a mailing list system yet anyway - most discussion takes place in Github, Drupal.org, and these chats anyway
[10:49:44]<cpm>well, back in the days of sourceforge, the nice bit there was the project lists *were* email lists, IE, they had a listserve interface. But like so many 'web based' communities, , they just don't get the activity. I put a lot of that on the back of the very excellent UIs of 'social media' apps. Folks spend the time they used to put into 'contributing' to following twitter/etc.
[12:25:04]* JustTB1 has quit (Remote host closed the connection)
[12:35:24]* JustTB has joined #farmos
[13:43:26]* trentf has quit (Quit: Leaving.)
[14:03:52]* trentf has joined #farmos
[14:35:35]* cpm has quit (Remote host closed the connection)
[15:06:42]* permakai[m] has joined #farmos