Log file Viewer

[11:12:44] <aclark> garbas: morning

[11:12:52] <garbas> aclark: morning

[11:13:45] <garbas> aclark: https://github.com/upiq/uu.task/issues/26#issuecomment-122852078

[11:14:47] <garbas> just commeted. i'm working on get_notification_dates method, then i would close #26 and open smaller tickets for sub tasks

[11:15:58] <aclark> garbas: cool thanks

[11:16:38] <garbas> aclark: i guess my next steps should be once of those 4 points i mentioned in #26

[11:16:45] <garbas> s/once/one

[11:18:27] <garbas> but tell me if i'm wrong with the plan. or if you have something else in mind

[11:19:04] <aclark> garbas: i definitely agree; I'm going to add a comment to try and get supton to respond with any concerns

[11:19:23] <aclark> garbas: in the meantime, after schema/property he says this is 2nd most important: (2) indexing of some sort (ZCatalog or something else) that allows us to query for due and notification times by date (datetime) range (e.g. notification daemon looks for notifications due between last nofitication success and present);

[11:19:41] <aclark> garbas: and i think that is one of your 4 bullet points? so that should give you something to focus on today

[11:20:01] <garbas> perfect. looks we are all on the same page

[11:21:02] <aclark> garbas: yeah the only thing I don't know or fully understand is how strongly he feels about zope.schema and the issue you raised about it not being the best to describe data; we'll see

[11:23:35] <garbas> i'm just saying zope.schema is hard to experiment (it is expensive in time to refractor)

[11:23:43] <aclark> Right

[11:24:37] <garbas> but once we have all the functionality working, and part of it tested, i would love to add those schemas back

[11:24:44] <aclark> K

[11:25:07] <garbas> we wouldn't gain anything really. but it is better for future work on the project

[11:25:20] <aclark> If you are FT this week Wednesday would be the time to do that, 23 is deadline.

[11:25:22] <aclark> Right

[11:25:50] <garbas> FT? sry dont know the abrevation

[11:25:52] <aclark> In short, GO GO GO; I'll be jumping in as much as possible particularly on Wednesday

[11:25:55] <aclark> FT == full time

[11:26:14] <garbas> ah yes, i'll add extra time until wed

[11:26:23] <aclark> cool

[11:49:47] <garbas> aclark: do we add our own start/end date fields?

[11:50:10] <garbas> or we try to use it from p.a.event?

[11:51:40] <garbas> aclark: https://github.com/plone/plone.app.event/blob/master/plone/app/event/dx/behaviors.py#L76

[11:54:38] <aclark> garbas: p.a.event is fine if you can make it work, i think

[11:54:53] <aclark> if it's too much trouble, we need our own :-)

[11:55:41] <garbas> aclark: ok. will add it as a dep and then i'll see how much trouble it gives us

[11:57:26] <aclark> garbas: FYI I ran into some "bad dep" trying to use Plone 5… I'll make a ticket. (I'm trying to see if we can easily support both 4 and 5, very low priority.)

[11:57:49] <aclark> i.e. during buildout some constraint failed for some front end related package

[11:59:08] <garbas> yeah, p.a.widgets and p.a.event would have to be different version for plone 4.0 and 5.0

[11:59:28] <garbas> i would rather create a working version of uu.task on 4.0

[11:59:51] <garbas> and if need we can port it to 5.0, but in a separate branch

[12:00:42] <aclark> cool np

[12:06:27] <garbas> we definetly wont make it work on 5.0 until wed

[13:18:43] <aclark> np

[17:53:52] <garbas> aclark: i'm about to create indexes for due and notification_rules fields

[17:54:04] <garbas> do we even need index for notification_rules?

[17:54:29] <garbas> how would we search notification_rules field?

[17:55:14] <garbas> i have hard time to find an index for it

[17:56:03] <garbas> if i understand correctly we need to index min and max date of notification_rules

[17:56:21] <garbas> using DateRangeIndex

[17:56:34] <garbas> so we can query for possible notification rules, right?

[17:57:42] <garbas> we need to ask our plone site: is there somebody to be notified?

[17:58:18] <garbas> ah yes, #31 explains this as well

[20:52:17] <aclark> garbas: ping

[21:20:49] <garbas> aclark: pong

[21:33:14] <aclark> garbas: hey was going to "loop you in" with supton but I think he has to leave soon; will update you in tickets, etc

[21:34:16] <garbas> ok

[21:34:35] <garbas> i'm also slowly shutting down. but did nice progress today

[21:35:06] <garbas> i sent you report what i did with todo for tomorrow

[21:35:20] <aclark> got it, thanks!

[21:39:27] <aclark> garbas: i'm going to add some unit tests, not sure about robot and/or functional but I'll find out

[21:39:39] <aclark> apparently robot framwork is a thing

[21:40:31] <garbas> well it is a nice thing, but takes quite some part of the budget usually

[21:40:59] <garbas> i think having some functional tests in python will keep us sane

[21:41:32] <garbas> and we didnt do anything special in javascript that we would need robot tests to see

[21:41:37] <garbas> if it works

[21:41:53] <garbas> aclark: is plan for tomorrow ok with you?

[21:42:27] <aclark> garbas: yes i'll email you too after I review everything supton just told me

[21:42:50] <garbas> great, i'll be still be for about an hour