| [02:33:48] | * JustTB has quit (Ping timeout: 246 seconds) |
| [02:48:27] | * JustTB has joined #farmos |
| [05:46:55] | * f2tmg[m] has joined #farmos |
| [06:25:51] | <skipper_is[m]> | I guess it is because they all have different formats, so you wouldn't need a manufacturer column for animals |
| [06:32:48] | * JustTB has quit (Quit: Leaving.) |
| [07:23:58] | * JustTB has joined #farmos |
| [10:46:25] | * ludwa6 has quit (Quit: ludwa6) |
| [10:47:41] | * ludwa6 has joined #farmos |
| [11:06:51] | <ludwa6> | g’day room: trying to get a current dump of all my Asset records -absent the Search and CSV features requested yesterday in this room, and since they in Github Issues tracker (https://github.com/farmOS/farmOS/issues/216 and …217), is this something i could pull by running a get request on the API, i wonder? |
| [11:08:10] | <ludwa6> | I am currently able to pull Sensor data, using API key that @donblair set up for me... |
| [11:08:58] | <ludwa6> | … but i don’t know how to hack that URL to pull all Asset data (and i don’t have a clue about CURL scripting :-) |
| [11:17:33] | <mstenta[m]> | Yes! Go to /farm_asset.json |
| [11:17:44] | <mstenta[m]> | That is the asset API endpoint |
| [11:18:02] | <mstenta[m]> | See the API docs on farmOS.org for filtering options |
| [11:18:32] | <mstenta[m]> | https://farmos.org/development/api/#requesting-records |
| [11:19:04] | <mstenta[m]> | That is the most complete way to get records. The CSV exports do not include everything |
| [11:19:16] | <ludwa6> | mstenta: got it, thanks. wow: that is a fine mess of ascii to parse! |
| [11:19:31] | <mstenta[m]> | If you're familiar with Python there is a library that makes it easier to work with |
| [11:19:54] | <mstenta[m]> | https://github.com/farmOS/farmOS.py |
| [11:22:59] | <ludwa6> | i have messed around with Python some in a former life, but it’s been awhile. may give it a try. meanwhile: why are the uri’s in this .json dump so weird? e.g. after http: , instead of // , there’s a \/\/ preceeding the domain address. is that normal in .json? |
| [11:24:10] | <ludwa6> | also: the fact i didn’t pass any primary key would seem to mean that anybody can access this API endpoint unauthorized -yes? |
| [11:24:21] | <ludwa6> | i mean private key. |
| [11:24:48] | <mstenta[m]> | Yea I think that's normal. Just escaping the slashes so they don't cause issues when being parsed by a script |
| [11:24:57] | <mstenta[m]> | No. It uses the same authentication as the rest of farmOS |
| [11:25:21] | <mstenta[m]> | You have a cookie stored in your browser which is used for both |
| [11:25:24] | <mstenta[m]> | So yes, if you use the script you'll be to auth |
| [11:25:35] | <ludwa6> | ah, so… OK, cool. |
| [11:26:44] | <ludwa6> | in fact i don’t care about having read-only access wide-open (we’re all about transparency on my farm :-)… |
| [11:26:57] | <mstenta[m]> | So yea... The record API works a bit differently than the sensor data API in that regard |
| [11:27:13] | <mstenta[m]> | The sensor API uses a public and private jet |
| [11:27:14] | <ludwa6> | oh? how is it different? |
| [11:27:17] | <mstenta[m]> | Key* |
| [11:27:31] | <mstenta[m]> | Haha private jet ✈️ |
| [11:27:39] | <mstenta[m]> | (autocorrect on my phone) |
| [11:28:05] | <ludwa6> | i hope you don’t use that phone to code farmOS :-) |
| [11:29:29] | <ludwa6> | Speaking of enabling read-only access to the world… I’ve asked about this recently, and you suggested setting up a gateway page with the login and password on it, which strikes me as a good idea. |
| [11:31:05] | <ludwa6> | And to do that in the best way, i’d like to be transparent to the user… Which would mean that the gateway page should look exactly like the login page at vdl.farmos.net. Any problem with setting up a copy of that page as gateway on my web server, from your perspective? |
| [11:31:51] | <mstenta[m]> | <ludwa6 "i hope you don’t use that phone "> Haha no. I tried that and it wasn't fun |
| [11:32:18] | <ludwa6> | i can well imagine! |
| [11:32:28] | <mstenta[m]> | You could probably embed it in an IFRAME on your side |
| [11:32:36] | <mstenta[m]> | Site* |
| [11:33:07] | <ludwa6> | sounds good to me. will propose it to our webmaster. |
| [11:39:59] | <mstenta[m]> | I think I mentioned already but: in the future I'd like to add the option to make things "public", which wouldn't require a login at all |
| [11:42:15] | <ludwa6> | yes -clearly preferable, for me. And i should think that would be drop-dead simple in Drupal, since that is the default config for many such sites, i believe. Is this more of a policy issue than a tech one? i.e. how to avoid the political problem (such as what plagues Facebook) of people “opening the kimono” out of ignorance, when they never really intended to? |
| [11:51:06] | <cloaz> | hi guys, i want to leave the city and live in the country any advice |
| [12:10:09] | <mstenta[m]> | @ludwa6:matrix.org: yea it won't be too difficult because it's Drupal. The main thing is we need to make a unified setting to make it easy to automatically configure all the necessary permissions for unauthenticated visitors |
| [12:10:20] | <mstenta[m]> | And there may be more details to figure out |
| [12:10:25] | <mstenta[m]> | Like selectively publishing |
| [12:10:31] | <mstenta[m]> | But all very doable |
| [12:10:40] | <mstenta[m]> | Just needs some dedicated thought |
| [12:11:09] | * ayushj_[m] has quit (*.net *.split) |
| [12:11:10] | * munjoma[m] has quit (*.net *.split) |
| [12:11:18] | <ludwa6> | @mstenta: no biggie, but a nice-to-have, next time you are working in that code neighborhood |
| [12:12:24] | * ayushj_[m] has joined #farmos |
| [12:12:24] | * munjoma[m] has joined #farmos |
| [12:12:25] | <ludwa6> | is there a development RoadMap somewhere published, i wonder? |
| [12:42:52] | <mstenta[m]> | Not really a unified one, no. But @jgaehring:matrix.org and @paul121:matrix.org and I were talking about the need for one |
| [13:00:33] | <paul121[m]> | I'm curious ludwa6 what development roadmaps you have seen that might be a good example? |
| [13:01:06] | <paul121[m]> | I this this Vuejs github roadmap is nice: https://github.com/vuejs/vue/projects/6 |
| [13:01:35] | <paul121[m]> | But probably isn't best for non-developers |
| [13:01:53] | <mstenta[m]> | One of the challenges with a roadmap for farmOS is often individual features are prioritized via sponsorship |
| [13:02:18] | <mstenta[m]> | But it would still be useful to have a broad strokes overview |
| [13:02:37] | <mstenta[m]> | It would help to show dependencies and order of operations too |
| [13:03:43] | <ludwa6> | Yes. Not to get too detailed -tho that kanban board you point to, @paul121, is nice… |
| [13:03:59] | <paul121[m]> | Yeah good things to keep in mind |
| [13:04:46] | <ludwa6> | … But when you are doing release planning, i think you need a map. |
| [13:04:54] | <mstenta[m]> | As it stands now, we don't have a "roadmap" but we do have a "big pool of potential next steps" ;-) |
| [13:05:08] | <paul121[m]> | In GH you could prepend projects/tasks with [Sponsorship] or [Core] or [etc]. Just an idea |
| [13:05:13] | <ludwa6> | For example: isn’t the upgrade to Drupal 8 going to be a major release for farmOS? |
| [13:05:26] | <paul121[m]> | Hahah yea. We gotta prioritize the pool of ideas |
| [13:06:31] | <mstenta[m]> | Yes yes we do have a roadmap coming together specifically for that |
| [13:07:09] | <mstenta[m]> | I hope to publish that this month |
| [13:08:10] | <mstenta[m]> | That will include some new feature development (just because some things will be easier to do during the transition) but for the most part it will just be aiming at feature parity with an automated migration |
| [13:08:37] | <paul121[m]> | 🥳 |
| [13:08:59] | <mstenta[m]> | A more general project roadmap will probably focus more on features |
| [13:10:54] | <ludwa6> | paul121: to answer earlier question; I used to participate (as a user & sponsor) in development of the Plone CMS… And, as that software was part of a stack (built on Zope and Python) , it was important to try and syncronise development RoadMaps of all 3 code bases. |
| [13:11:47] | <ludwa6> | I’ve been out of that world for many moons now, but it looks like they still do it that way, per https://plone.org/roadmap/2019-plone-roadmap |
| [13:12:16] | <mstenta[m]> | Talk to you all later... Headed out with the kids. Might get a Christmas tree :-) |
| [13:12:51] | <paul121[m]> | Good luck mstenta ! |
| [13:12:59] | <ludwa6> | have fun, mate. try not to pick a loser (like Charlie Brown :-) |
| [13:13:40] | <paul121[m]> | haha |
| [13:14:52] | <paul121[m]> | Thats neat ludwa6 ! The 3 code bases definitely make that a bit more challenging to coordinate |
| [13:15:48] | <paul121[m]> | jgaehring had mentioned generating a visual "timeline" of the roadmap that is generated from Markdown |
| [13:16:26] | <paul121[m]> | So maybe the raw detailed roadmap is a nicely formatted Markdown, but the headers with dates could be pulled out into a timeline |
| [13:16:37] | <paul121[m]> | Maybe define dependencies in there |
| [13:16:50] | <paul121[m]> | That would be a fun project to hack on :-) |
| [13:17:08] | <ludwa6> | dependencies are key. otherwise: KISS, i guess; simplest thing that could possibly work. |
| [13:18:22] | <paul121[m]> | What's KISS? |
| [13:18:41] | <ludwa6> | oh, sorry; Keep It Simple and Straighforward |
| [13:19:15] | <ludwa6> | easy as possible for devs to maintain, in this case. |
| [13:19:27] | <paul121[m]> | Ahh. Cool. Yes |
| [13:20:01] | <ludwa6> | dunno what tools you guys use; Trello is probalby the most popbular tool for Kanban-style project management these days. |
| [13:20:33] | <ludwa6> | more popular in business than software probably. but here’s a SW example: http://martinknapic.com/types-roadmaps-within-software-product-developme... |
| [13:22:52] | <jgaehring[m]> | > oh, sorry; Keep It Simple and Straighforward |
| [13:22:52] | <jgaehring[m]> | oh I thought it was Keep It Simple, Stupid |
| [13:22:59] | <jgaehring[m]> | 😛 |
| [13:23:04] | <ludwa6> | that too :-) |
| [13:23:30] | <ludwa6> | Trello can be as simple or complex as you like. |
| [13:24:10] | <paul121[m]> | I like the Google long term roadmap that's listed there. Communicates to users pretty clearly what the plan is. For farmOS it would demonstrate to someone who lands on the website and knows nothing, that the project has a plant & path |
| [13:24:26] | <jgaehring[m]> | > ...generating a visual "timeline" of the roadmap that is generated from Markdown |
| [13:24:26] | <jgaehring[m]> | yea, that would be fun to hack on... I think part of that would be contingent on migrating farmos.org from mkdocs to Gatsby though |
| [13:25:04] | <paul121[m]> | Yea thats right. Another project!! haha |
| [13:26:00] | <paul121[m]> | I think the GH project board could work well for dev side of stuff. It's less overhead than learning and committing to Trello |
| [13:26:40] | <jgaehring[m]> | yea, I've been itching to start a Gatsby version of the web page... think I would make that my project if we ever did a volunteer day like we talked about |
| [13:27:10] | <jgaehring[m]> | > I think the GH project board could work well for dev side of stuff. It's less overhead than learning and committing to Trello |
| [13:27:10] | <jgaehring[m]> | +1 |
| [13:27:41] | <ludwa6> | sure -too much overlap between Trello and Github; you’d wind up w/ redundancy problems |
| [13:27:50] | <paul121[m]> | > if we ever did a volunteer day like we talked about |
| [13:27:50] | <paul121[m]> | Yea! Wish we could be in person more often to hack :D |
| [13:28:03] | <jgaehring[m]> | oh yea, totally! |
| [13:28:57] | <ludwa6> | well: nigh on suppertime here in GMT; guess i’ll be off to the feed trough :-) |
| [13:29:15] | <ludwa6> | ACTION eats |
| [13:29:51] | <paul121[m]> | Hahah I gtg too. Talk later |