| [20:12:57] | * trentf has quit (Remote host closed the connection) |
| [21:22:44] | * JustTB has joined #farmos |
| [22:16:39] | * JustTB has quit (Quit: Leaving.) |
| [15:54:38] | * Fosten has joined #farmos |
| [16:45:10] | <mstenta> | Hi Fosten |
| [16:45:26] | <Fosten> | mstenta: hello |
| [16:45:36] | <mstenta> | mind if i just copy+paste our conversation from PMs so it gets stored for posterity? |
| [16:45:44] | <Fosten> | go for it |
| [16:45:44] | <mstenta> | (farmBOT logs this channel) |
| [16:45:52] | <mstenta> | k standby for big text.. :-) |
| [16:46:00] | <mstenta> | <Fosten> hey michael, its brian from pa, i stop by the calls sometime. have you ever considered adding a kanban board into farmOS? |
| [16:46:01] | <mstenta> | <mstenta> Hi Brian! |
| [16:46:01] | <mstenta> | <mstenta> I haven't considered it - but it's a cool idea! |
| [16:46:01] | <mstenta> | <Fosten> it would really make that dashboard slick if you could move those logs into columns like "not yet started", "in planning", "in progress", "waiting/verification", etc. the only module i found was https://www.drupal.org/project/kanban but the last commit was 2 years ago |
| [16:46:02] | <mstenta> | <mstenta> I could see "Logs" having different status (other than just done and not done) perhaps - and a UI for dragging them from state to state - that would essentially be a kanban board I think. |
| [16:46:05] | <mstenta> | <mstenta> Yea exactly :-) |
| [16:46:07] | <mstenta> | <mstenta> Neat - I haven't seen that module. |
| [16:46:09] | <mstenta> | <mstenta> I bet there are some simple Javascript libraries out there too - maybe we could just roll our own UI |
| [16:46:12] | <mstenta> | <Fosten> yes, could just be additional option to "done" and "not done" |
| [16:46:14] | <mstenta> | <Fosten> you have the ingredients there already |
| [16:46:16] | <mstenta> | <Fosten> now that winters here, i have time to dig at farmOS, ha |
| [16:46:18] | <mstenta> | <Fosten> you mention not exporting and re-importing via csv. so if i setup a new instance on a new machine, i would just backup db and reconnect mysql? |
| [16:46:21] | <mstenta> | <Fosten> re kanban there's this https://www.drupal.org/project/openlucius_board but i dont know what openlucius is, sounds like unnecessary bloat |
| [16:46:26] | <mstenta> | <Fosten> ya like you said, it might be easy to javascript some moveable boxes. use log types as rows, states as columns. |
| [16:46:29] | <mstenta> | <Fosten> so i keep all my farm/garden tasks on a google calendar. it would be cool if there way to import gcal to create all my logs in one click. i should vent these thoughts to the issue tracker. |
| [16:46:32] | <mstenta> | <Fosten> or if they synced bi-directionally so i could create logs in farmos and they'd show up on my gcal |
| [16:46:34] | <mstenta> | <mstenta> Oops sorry - got distracted and didn't hear my IRC client beep |
| [16:46:36] | <mstenta> | <mstenta> Yes - all the records are stored in the database, so you can just migrate that like any other MySQL dump |
| [16:46:39] | <mstenta> | <mstenta> Haha yea - add some feature requests! These are great ideas! |
| [16:46:41] | <mstenta> | <mstenta> We just recently added a "Calendar" feature which displays logs in a calendar view |
| [16:46:43] | <mstenta> | <Fosten> ya i saw that was new |
| [16:46:45] | <mstenta> | <Fosten> i like it |
| [16:46:47] | <mstenta> | <mstenta> One of the next steps is to add an iCal export so you can display that in your other calendar software |
| [16:46:50] | <mstenta> | <Fosten> how about reoccurring events? |
| [16:46:52] | <mstenta> | <mstenta> Don't have that yet, but I think there's a feature request for it somewhere |
| [16:46:56] | <mstenta> | <mstenta> We do have a "Clone" button for logs, so you can make a copy in the future |
| [16:46:58] | <mstenta> | <Fosten> right |
| [16:47:00] | <mstenta> | <mstenta> That's sort of just an interim solution though |
| [16:47:02] | <mstenta> | <mstenta> The key difference between farmOS logs and calendar events is that logs need to represent what actually happened |
| [16:47:05] | <mstenta> | <mstenta> that's why you mark them as done |
| [16:47:07] | <mstenta> | <mstenta> A lot of the time with calendars (at least for me) I end up adding recurring events and it serves more as a reminder, but maybe I don't actually do it |
| [16:47:10] | <mstenta> | <mstenta> But logs are meant to be very specific records of what actually happened |
| [16:47:12] | <mstenta> | <Fosten> ya, there's no "done" in gcal |
| [16:47:14] | <mstenta> | <mstenta> So my thought with recurring logs is that maybe we'll create a system that auto-creates the NEXT log ... and if you mark it "done" then it gets saved... but if not, then it disappears |
| [16:47:17] | <mstenta> | <mstenta> We don't want to have thousands of "not done" logs in the past and future |
| [16:47:19] | <mstenta> | <mstenta> If that makes sense |
| [16:47:21] | <mstenta> | <mstenta> We should move this discussion to #farmOS |
| [16:47:23] | <mstenta> | <Fosten> ha, ya |
| [16:47:27] | <mstenta> | <mstenta> If you don't mind |
| [16:47:29] | <mstenta> | Ok... :-) |
| [16:47:31] | <mstenta> | Where were we? |
| [16:47:33] | <mstenta> | Oh yea... so I could envision a "Recurring logs" UI that basically just lets you create a list of recurring events |
| [16:47:36] | <mstenta> | And that would basically serve you up a log that you could mark done if you actually do it |
| [16:47:51] | <mstenta> | And if not, it gets auto-deleted or something (maybe there's some options for how long it sticks around first - I dunno) |
| [16:50:37] | <Fosten> | so i was watching pam dawling's slideshare on garden calendaring, and she has 2 columns for "date scheduled" and "date actually completed". maybe scheduled date is created annually, but stored elsewhere, and then the log is only created when it hits kanban "in planning", "in progress", "done", etc. |
| [16:51:07] | <mstenta> | Ah yea - this is something we are talking about in the Grazing Planning module |
| [16:51:15] | <mstenta> | The need to store both the planned and the actual |
| [16:51:34] | <mstenta> | One way I'm thinking about handling this is with entity revisions in Drupal |
| [16:51:48] | <mstenta> | Each time you update a log, it would store a new revision |
| [16:51:54] | <mstenta> | So you could see the changes over time |
| [16:52:13] | <mstenta> | And maybe we could visualize that somehow specifically in farmOS - to show how plans change |
| [16:53:56] | <Fosten> | perhaps a "notification" type… you have an upcoming reoccuring event… create log and move to workflow? reschedule? cancel? |
| [16:54:34] | <mstenta> | Hmm yea - so it doesn't actually create a log until it tells you to? |
| [16:54:42] | <mstenta> | Until YOU tell it to i mean |
| [16:55:31] | <Fosten> | ya so your queue of "auto-creating logs" can be maintained |
| [16:55:43] | <mstenta> | Mmm I like that idea |
| [16:55:55] | <Fosten> | but you can still see what's ahead, without looking behind |
| [16:55:57] | <mstenta> | "Did you fertilize the tomatoes?" |
| [16:56:07] | <mstenta> | Hmm yea... some considerations there |
| [16:56:13] | <Fosten> | for sure |
| [16:56:22] | <mstenta> | Good ideas though |
| [16:57:56] | <Fosten> | my planning uses mostly kanban and calendar, so its exciting to see the possibilities here |
| [17:03:54] | <Fosten> | but i also keep a flat log, so i see the importance of keeping past, present, and future separate |
| [17:09:08] | <mstenta> | gtg - great talking! |
| [17:09:26] | <mstenta> | feel free to dump ideas into issues on Github.com/farmOS/farmOS! :-) |
| [18:23:08] | * Fosten has left #farmos () |