[00:18:01] (CR) Milimetric: "This change is cool, but I'll have to think a bit tomorrow before merging, because it changes the number of columns so the new output will" [analytics/limn-edit-data] - https://gerrit.wikimedia.org/r/237534 (owner: Jforrester) [00:19:38] James_F|Away: the top 50 by active editors works for me, if that's what you wanna use. You'll always have the old data for the other wikis to compare, and you can always add to the list if you're interested in a particular wiki. It would be available within a day of merging the change. You or neilpquinn should file a task in phab and I'll take care of it. [00:22:43] Analytics-Dashiki, Analytics-Kanban, Editing-Analysis, Editing-Department: Time selector on https://edit-analysis.wmflabs.org/compare/ is only followed (?) by the first and fifth elements {crow} [3 pts] - https://phabricator.wikimedia.org/T112183#1629168 (Milimetric) p:Triage>High a:Milimetr... [00:24:01] Analytics-Dashiki, Analytics-Kanban, Editing-Analysis, Editing-Department: Time selector on https://edit-analysis.wmflabs.org/compare/ is only followed (?) by the first and fifth elements {crow} [3 pts] - https://phabricator.wikimedia.org/T112183#1628303 (Milimetric) This is a side effect of the new... [00:42:25] milimetric: Cool, thanks! [01:09:28] Analytics-Dashiki, Analytics-Kanban, Editing-Analysis, Editing-Department: Limit wikis on https://edit-analysis.wmflabs.org/compare/ to top 50 Wikipedias - https://phabricator.wikimedia.org/T112222#1629271 (Jdforrester-WMF) NEW [09:49:37] Analytics-Dashiki, Analytics-Kanban, Editing-Analysis, Editing-Department: Limit wikis on https://edit-analysis.wmflabs.org/compare/ to top 50 Wikipedias - https://phabricator.wikimedia.org/T112222#1629860 (bmansurov) How often will this list change? Can we ping a URL to get this list or should it b... [09:52:51] Analytics-Wikistats: Adding Odia (Oriya) Wikisource to Stats Wiki - https://phabricator.wikimedia.org/T108012#1629867 (Jnanaranjan_sahu) Can we have this activated soon ? [10:16:34] Analytics-Dashiki, Analytics-Kanban, Browser-Support-Firefox: vital-signs doesn't display pageviews graph in Firefox 41, 42 {crow} [3 pts] - https://phabricator.wikimedia.org/T109693#1629925 (Nemo_bis) Great, pageviews works for me now with firefox-40.0.3-1.fc22.x86_64; will test on the other machine n... [10:52:33] (PS1) Bmansurov: Correctly show comparison descriptions in a popup [analytics/dashiki] - https://gerrit.wikimedia.org/r/237621 (https://phabricator.wikimedia.org/T104261) [12:25:04] (PS1) Bmansurov: Make the roller input easier to read [analytics/dashiki] - https://gerrit.wikimedia.org/r/237636 (https://phabricator.wikimedia.org/T104261) [13:42:27] hey ottomata :) [13:42:45] Let me know when you have a minute for ua-parser packaging [13:43:07] Also: congrats for successful EL deploy ! [13:43:12] That just rocks :) [13:47:06] woohoo! [13:47:09] joal: am here [13:47:11] wassssupp [13:47:28] Just padding on the back a bit for the good work on EL :) [13:47:33] Plus some help :) [13:47:58] Oh, and actually another question [13:48:07] grafana asked me for a password this morning :( [13:48:18] I tried my usual stuff, and it didn't work [13:48:32] is it now restricted to ops group? [13:49:51] i dunno! i saw that ori restricted it [13:49:55] let's ask! [13:50:26] ops chan I guess :) [13:51:10] email! [13:51:13] you are on list, ja? [13:51:21] Don't think so :( [13:51:48] ok will cc [13:51:58] operations@lists.wikimedia.org ? [13:52:09] yes [13:52:18] not yet on it [13:52:21] will do though [13:52:36] can be interesting (and probably flooding as well [13:54:20] actually ottoama, I can't ask for subscription to ops list, must be private [13:54:27] hm, i dont' think it is [13:54:28] Can you help on that ? [13:54:28] hm [13:54:31] dunno [13:54:36] Analytics-EventLogging, Analytics-Kanban: Handle duplicate insert error {stag} - https://phabricator.wikimedia.org/T112265#1630441 (Milimetric) NEW [13:54:36] will ask [13:54:43] :) [13:58:06] oh, ottomata, actually, found the list: it's ops, not operations [13:58:11] * joal faceplam [13:58:44] ah cool [14:00:18] ottomata: about ua-parser repos, let me know when you can help [14:02:18] holaaaa [14:02:24] Hey nuria ! [14:02:28] How early :) [14:02:53] joal: i had a short day yesterday so i will be putting up some hours today [14:03:11] joal: will check the kyro serialization to see where does the error come from [14:03:27] joal: but other than trial/error i cannot think of anything better, any ideas? [14:03:54] nuria: maybe try a very simple UDF with GenericUDF and see if it still does the same thing? [14:04:13] joal,ottomata we know it doesn't [14:04:15] as otherwise [14:04:21] ua udf will not work [14:04:33] and neither would the ones that count images [14:04:58] ottomata: there must be a piece of code that is trigerring that, will try to move stuff arround [14:05:38] nuria: will try to think of it as well [14:07:57] Analytics-Backlog, Analytics-Dashiki, Editing-Analysis, Editing-Department: Limit wikis on https://edit-analysis.wmflabs.org/compare/ to top 50 Wikipedias {lion} - https://phabricator.wikimedia.org/T112222#1630503 (Milimetric) [14:09:28] nuria: one thing to try: put the @UDFType(deterministic = true) flag [14:09:48] joal: nice, will do [14:10:26] joal: https://phabricator.wikimedia.org/T108546 [14:10:28] Another is to have your variables in UDF set private (not protected) [14:10:41] Don't why it could change, but ... [14:11:04] * joal reading [14:14:23] ok ottomata, finally managed to get in, and understand better the issues [14:14:30] sorry for bothering :S [14:14:32] np [14:15:18] Watching kafka flows is a bit like a fire: a lot of regularity, but still never the same :) [14:16:41] joal: will try that too and try to do some more reserach [14:19:36] joal: someone tells me that you should be able to access grafana with your wikitech ldap creds [14:19:59] yup, managed to da that (sorry if wasn't clear on previous message) [14:20:08] iot's actually written on the ticket :) [14:26:57] ohhh ok [14:26:57] cool [14:27:23] ottomata: I never manage to get my LDAP creds correct in less than 3 times :S [14:30:29] Analytics-Backlog: Need a Dashiki namespace so we can protect configs {crow} - https://phabricator.wikimedia.org/T112268#1630543 (Milimetric) NEW [14:32:16] Analytics-Dashiki, Analytics-Kanban, Browser-Support-Firefox: vital-signs doesn't display pageviews graph in Firefox 41, 42 {crow} [3 pts] - https://phabricator.wikimedia.org/T109693#1630555 (Milimetric) Heh, thanks Nemo. There are two issues here. First, someone broke our config pages, which is tota... [14:45:42] Analytics-Kanban: Follow on security asks {tick} - https://phabricator.wikimedia.org/T109462#1630586 (mforns) After discussion with Chris Steipp and other schema owners, we've come to the consensus that for this kind of sensitive structures (see scenarios explained in task description): - We'll not auto-pur... [14:53:38] ottomata: some time before standup? [14:55:33] yes joal am here [14:56:34] Analytics-Backlog: Mark affected schemas as "containing user-inputed textual data" in the schema pagesv {tick} - https://phabricator.wikimedia.org/T112271#1630610 (mforns) NEW [14:57:02] ottomata: the new packaging of uap-java and uap-core expect the two folders to be in the same parent folder [14:58:07] so I wonder if we should create two repos, or update the existing one removing it's content and adding the two subfolders (themselves being repos, but since repackaging, it's feasible) [14:58:35] don't understand, does their layout not work? [14:59:00] it works if you clone the two repos in the same parent folder [14:59:54] So we decide, either we clone them both into two, then package using both, or we use only one parent directory as repo [15:01:40] oh [15:01:58] still don't understand, they won't build unless they are cloned that way? [15:02:07] Analytics-Kanban: Put toghether an updated documentation on EventLogging {tick} {oryx} - https://phabricator.wikimedia.org/T112124#1630625 (mforns) a:mforns [15:02:11] oh [15:02:12] ${basedir}/../uap-core/test_resources [15:02:14] hm [15:02:16] right :) [15:02:22] hm. [15:02:24] that's dumb. [15:02:47] hm, I wouldn't judge, but we need to make it work :) [15:02:51] aye [15:02:53] mh. [15:02:56] submodules? [15:02:59] git submodules? [15:03:04] hm. [15:03:06] so my call would be to keep 1 repo (exisitng one) [15:03:25] Clen wipe it, and clone both repos in [15:03:36] clone and git add files? [15:03:40] Not very correct, but ensures it works on our side [15:03:42] or git submodule add? [15:03:55] Don't know about git submodules :( [15:04:03] well, just git add would work [15:04:06] analytics/refinery/source for instance ? [15:04:06] but i generally don't like it [15:04:10] no [15:04:20] as it is hard to bring in new changes from upstream [15:04:28] this is more complicated but we could [15:04:31] have 3 repos :( [15:04:35] 2 that trakc upstream [15:04:37] OH [15:04:50] wait, joal, is the only reason we want to clone these into gerrit so that we can tag them? [15:05:21] Yes, tag, to track releases tighter on our side [15:05:32] do we need to make any content/code modifications to them? [15:05:34] no, right? [15:05:38] no content modifs [15:05:42] aye [15:05:47] we could then just have 1 parent repo as you suggest [15:05:47] Just folder organisation being correct [15:05:50] but use git submodule [15:05:53] and add these two repos [15:06:06] git submodule effectively 'tags' the checked out copy in a commit of the parent repo [15:06:25] maybe still good to clone these 2 into gerrit though, not sure. [15:06:26] I need to read on git submodules [15:06:29] that way we always have a ref [15:06:32] joal, its pretty simple [15:06:53] basically, it is a wrapper that saves a (remote, sha, path) [15:06:59] Just a subfolder having its own repo I guess, but commits / tags etc hierarchy must have some rules :) [15:07:02] then when you do git sudmodule update --init [15:07:09] it clones the remote @ sha into path [15:07:23] ok [15:07:24] in order to get a new commit [15:07:29] you have to cd path/ [15:07:41] git pull (or git checkout NEWSHA) [15:07:44] cd ../ [15:07:46] git add path [15:07:47] git commit [15:07:54] that will change the SHA at which the submodule is checked out [15:08:00] Right [15:08:10] Sounds not that bad actually :) [15:08:15] so, we could do 3 repos [15:08:16] 1 parent [15:08:23] and then 2 that track ua-parser upstream [15:08:25] or [15:08:28] we could do 1 repo [15:08:30] one parent [15:08:34] with submoudles that point at upstream directly [15:08:39] instead of our 2 clones [15:08:46] hm [15:09:01] 1 repo is less complicated, but it means we don't have centralized copies of the submodules [15:09:05] standup being in 20 minutes, I vote on asking the team :) [15:09:08] so, if that github repo went away [15:09:18] we'd lose the code...except on our laptops [15:09:19] ok [15:09:28] right ottomata, very good argument [15:09:45] 3 repos it'll be then :) [15:09:48] ok [15:10:03] i think its up to you if you want to physically tag the uap-* clones [15:10:05] Do we reuse our ua-parser as main parent one ? [15:10:09] e.g. with wmf-* [15:10:10] sure [15:10:12] i think taht's fine. [15:10:16] awesome [15:10:46] I don't have to create repos :( [15:11:05] I think I'll tag uap-* clones [15:11:10] cleaner [15:11:22] k [15:11:28] joal: i can create for you, shall I do now? [15:11:32] ottomata: can you create uap-core and uap-java [15:11:33] :) [15:11:35] right [15:11:43] yes, i'm going to import them at the upstream masters, s'ok? [15:11:50] perfect [15:12:10] I'll update the parent one to have the two submodules (removing exisitng stuff) [15:12:30] Then tag everywhere, then build, and deploy on archiva [15:12:32] Nice [15:14:40] haha, does oliver have commit rights on upstream? [15:14:48] https://github.com/ua-parser/uap-java/commit/8f138347c09699797cea150908a2e71dd2d09453 [15:15:39] Analytics-Backlog, Analytics-Dashiki: Fix annotation date parsing in Firefox {crow} - https://phabricator.wikimedia.org/T112273#1630662 (Milimetric) NEW [15:17:21] ottomata: Indeed he has ! [15:18:11] (PS1) Milimetric: Fix date parsing in Firefox [analytics/dashiki] - https://gerrit.wikimedia.org/r/237664 (https://phabricator.wikimedia.org/T109693) [15:18:49] mforns or nuria: mind giving this a quick look: https://gerrit.wikimedia.org/r/#/c/237664/ [15:19:07] milimetric: looking [15:20:25] milimetric: was that killing FF? [15:20:49] nuria: yeah, the current build of vital signs doesn't show any other graphs besides pageviews in Firefox [15:20:58] because the date format in the pageviews source files works with new Date() [15:21:05] but the wikimetrics date format doesn't [15:21:18] yaaay date parsing differences in browsers yaaay :/ [15:21:44] joal: [15:21:44] https://gerrit.wikimedia.org/r/#/admin/projects/analytics/ua-parser/uap-java [15:21:44] and [15:21:44] https://gerrit.wikimedia.org/r/#/admin/projects/analytics/ua-parser/uap-core [15:21:55] Thanks ottomata ! [15:21:59] madhuvishy, yt? [15:23:10] milimetric: give me 10 mins to test [15:23:44] Analytics-EventLogging, Analytics-Kanban, Patch-For-Review: Deploy EventLogging on Kafka to eventlog1001 (aka production!) {stag} [8 pts] - https://phabricator.wikimedia.org/T106260#1630698 (Ottomata) [15:23:46] Analytics-EventLogging, Analytics-Kanban, Performance-Team, Patch-For-Review: Make webperf eventlogging consumers use eventlogging on Kafka - https://phabricator.wikimedia.org/T110903#1630699 (Ottomata) [15:23:47] no rush nuria [15:23:58] Analytics-EventLogging, Analytics-Kanban: {stag} EventLogging on Kafka - https://phabricator.wikimedia.org/T102225#1630701 (Ottomata) [15:24:00] Analytics-EventLogging, Analytics-Kanban, Performance-Team, Patch-For-Review: Make webperf eventlogging consumers use eventlogging on Kafka - https://phabricator.wikimedia.org/T110903#1589603 (Ottomata) [15:24:27] Analytics-EventLogging, Analytics-Kanban, Performance-Team, Patch-For-Review: Make webperf eventlogging consumers use eventlogging on Kafka {stag} - https://phabricator.wikimedia.org/T110903#1630706 (Ottomata) [15:27:34] (CR) Nuria: [C: 2 V: 2] "Tested in FF, metrics from wikimetrics are visible just fine." [analytics/dashiki] - https://gerrit.wikimedia.org/r/237664 (https://phabricator.wikimedia.org/T109693) (owner: Milimetric) [15:28:39] ottomata: Should I go for light or annotated tag in uap-* ? [15:28:55] ? [15:29:33] Not being an exepert in git tagging, I am re-reading the tag section [15:29:35] joal: i am learning something new about git! [15:29:39] :D [15:29:41] i didn't know there were two types [15:30:00] das cool [15:30:01] up to you! [15:30:03] :) [15:30:39] ok :) [15:35:57] Analytics-EventLogging, Analytics-Kanban, Patch-For-Review: Puppetize parallel eventlogging-processor {stag} [5 pts] - https://phabricator.wikimedia.org/T104228#1630760 (ggellerman) [15:36:14] Analytics-EventLogging, Analytics-Kanban, Patch-For-Review: Deploy EventLogging on Kafka to eventlog1001 (aka production!) {stag} [13 pts] - https://phabricator.wikimedia.org/T106260#1630761 (ggellerman) [15:37:26] Analytics-Backlog, Analytics-EventLogging, Performance-Team, Patch-For-Review: Make webperf eventlogging consumers use eventlogging on Kafka {stag} - https://phabricator.wikimedia.org/T110903#1630764 (kevinator) [15:39:09] Analytics-Kanban: Follow on security asks {tick} [3 pts] - https://phabricator.wikimedia.org/T109462#1630768 (mforns) [15:39:12] Analytics-Kanban: Fix lagging report updater {lion} [5 pts] - https://phabricator.wikimedia.org/T112276#1630770 (Milimetric) NEW a:Milimetric [15:39:39] Analytics-Kanban, Patch-For-Review: Make reportupdater support script execution [8 pts] - https://phabricator.wikimedia.org/T112109#1630781 (mforns) [15:44:36] (PS3) Joal: Update bot filtering for webrequests. [analytics/refinery/source] - https://gerrit.wikimedia.org/r/237392 (https://phabricator.wikimedia.org/T108598) [15:47:56] joal, so what's the difference between the new patch and last patch? [15:48:26] commit message to have the thing showing up in phabricator :S Sorry for the spam Ironholds [15:49:28] no problem! [15:49:31] I'll +1 it again :) [15:49:45] thx :) [15:50:02] (CR) OliverKeyes: [V: 1] Update bot filtering for webrequests. [analytics/refinery/source] - https://gerrit.wikimedia.org/r/237392 (https://phabricator.wikimedia.org/T108598) (owner: Joal) [16:05:41] Analytics-EventLogging, Analytics-Kanban, Patch-For-Review: Handle duplicate insert error {stag} - https://phabricator.wikimedia.org/T112265#1630887 (Ottomata) Oh cool! This is already implemented! https://gerrit.wikimedia.org/r/#/c/237688/1/manifests/role/eventlogging.pp [16:26:54] Analytics-Backlog: Create new table for 'referer' aggregated data - https://phabricator.wikimedia.org/T112284#1630965 (JAllemandou) NEW [16:27:50] Analytics-Kanban, Research-and-Data: Analyze referrer traffic to determine report format {hawk} [8 pts] - https://phabricator.wikimedia.org/T108886#1630982 (JAllemandou) New tasks created to track the proposed solution: T112284 [16:37:31] (PS4) Ottomata: Update bot filtering for webrequests. [analytics/refinery/source] - https://gerrit.wikimedia.org/r/237392 (https://phabricator.wikimedia.org/T108598) (owner: Joal) [16:37:41] joal: ready for merge? +2 from me. [16:38:08] ottomata: ready for merge for source [16:38:19] (CR) Ottomata: [C: 2 V: 2] Update bot filtering for webrequests. [analytics/refinery/source] - https://gerrit.wikimedia.org/r/237392 (https://phabricator.wikimedia.org/T108598) (owner: Joal) [16:38:42] Thx [16:43:13] (PS1) Milimetric: Fix column filter to carry over any date filters [analytics/dashiki] - https://gerrit.wikimedia.org/r/237703 (https://phabricator.wikimedia.org/T112183) [16:43:42] mforns: if you're still around, give that a review ^ [16:43:49] milimetric, sure [16:44:02] thx very much [16:46:34] (CR) Mforns: [C: 2 V: 2] "LGTM" [analytics/dashiki] - https://gerrit.wikimedia.org/r/237703 (https://phabricator.wikimedia.org/T112183) (owner: Milimetric) [18:04:18] Analytics-Dashiki, Analytics-Kanban, Editing-Analysis, Editing-Department, Patch-For-Review: Time selector on https://edit-analysis.wmflabs.org/compare/ is only followed (?) by the first and fifth elements {crow} [3 pts] - https://phabricator.wikimedia.org/T112183#1628303 (Milimetric) @Jdforreste... [18:05:16] Analytics-Dashiki, Analytics-Kanban, Browser-Support-Firefox, Patch-For-Review: vital-signs doesn't display pageviews graph in Firefox 41, 42 {crow} [3 pts] - https://phabricator.wikimedia.org/T109693#1631601 (Milimetric) Thanks again, @Nemo_bis, all seems well in Firefox land now. It was just hand... [18:05:44] Analytics-Kanban, Research-and-Data: Analyze referrer traffic to determine report format {hawk} [8 pts] - https://phabricator.wikimedia.org/T108886#1631603 (Milimetric) Should I then close this one, @kevinator? [18:09:02] Analytics-Kanban, Research-and-Data: Analyze referrer traffic to determine report format {hawk} [8 pts] - https://phabricator.wikimedia.org/T108886#1631616 (kevinator) @milimetric yes, move to Done... I'll close it ;-) [18:10:35] milimetric: I editd my comment after the fact. I'll close the task ^^ [18:10:48] thx kevinator [18:11:08] (PS2) Milimetric: Correctly show comparison descriptions in a popup [analytics/dashiki] - https://gerrit.wikimedia.org/r/237621 (https://phabricator.wikimedia.org/T104261) (owner: Bmansurov) [18:14:19] (CR) Milimetric: [C: 2 V: 2] "Awesome! Yeah, this was an upstream bug, but it's also because we're using an out-dated version of semantic UI. We would upgrade but the" [analytics/dashiki] - https://gerrit.wikimedia.org/r/237621 (https://phabricator.wikimedia.org/T104261) (owner: Bmansurov) [18:14:28] (PS2) Milimetric: Make the roller input easier to read [analytics/dashiki] - https://gerrit.wikimedia.org/r/237636 (https://phabricator.wikimedia.org/T104261) (owner: Bmansurov) [18:21:57] (PS3) Milimetric: Make the roller input easier to read [analytics/dashiki] - https://gerrit.wikimedia.org/r/237636 (https://phabricator.wikimedia.org/T104261) (owner: Bmansurov) [18:22:55] (CR) Milimetric: [C: 2 V: 2] "Had to update slightly to also fix the other layout using dygraphs. I think I'd rather a solution that doesn't require styling per layout" [analytics/dashiki] - https://gerrit.wikimedia.org/r/237636 (https://phabricator.wikimedia.org/T104261) (owner: Bmansurov) [18:26:14] Analytics-Backlog, Analytics-Dashiki, Editing-Analysis, VisualEditor, Patch-For-Review: Improve the edit analysis dashboard {lion} - https://phabricator.wikimedia.org/T104261#1631726 (Milimetric) These last two improvements by Baha have been deployed. [18:26:56] Analytics-Backlog, Analytics-Dashiki, Editing-Analysis, VisualEditor, Patch-For-Review: Improve the edit analysis dashboard {lion} - https://phabricator.wikimedia.org/T104261#1631735 (Jdforrester-WMF) Nice. [18:27:05] Analytics-Backlog, Analytics-Dashiki, Editing-Analysis, VisualEditor, Patch-For-Review: Improve the edit analysis dashboard {lion} - https://phabricator.wikimedia.org/T104261#1631736 (Milimetric) [18:29:25] Analytics-Backlog, Analytics-Dashiki, Editing-Analysis, VisualEditor, Patch-For-Review: Improve the edit analysis dashboard {lion} - https://phabricator.wikimedia.org/T104261#1631748 (Jdforrester-WMF) [18:33:05] Analytics-Backlog, Analytics-Dashiki, Editing-Analysis, VisualEditor, Patch-For-Review: Improve the edit analysis dashboard {lion} - https://phabricator.wikimedia.org/T104261#1631752 (Jdforrester-WMF) [20:06:09] Have a good weekend a-team :) [20:06:18] See you on monday ! [20:54:52] have a great weekend, J [20:55:09] nice weekend milimetric [21:24:42] Analytics-Backlog: Investigate sample cube pageview_count vs unsampled log pageview count - https://phabricator.wikimedia.org/T108925#1632602 (JKatzWMF) @Ironholds that seems like a good idea. From a product perspective, I am okay with <5% random discrepancy, but if its non-random that presents more of a pro... [21:31:04] have a good weekend, Marcel [21:31:16] hey madhuvishy do you wanna talk for a sec about the endpoints, etc? [21:31:34] milimetric: sure, batcave? [21:31:47] yes [21:32:22] :] milimetric I thought you were leaving, but then I realized that you were wishing nice weekend to Joseph, no? I think none of us is leaving yet, hehehe [21:48:55] :) I never really leave, my computer just shuts down at some point [21:49:15] xD [21:57:11] halfak: I've got an idea. How about we move Research:* to MediaWiki.org? It can be born-Flow'ed. :-) [21:57:25] (Flighted?) [21:57:29] James_F, feeling kind of tempted [21:57:34] :P [21:58:32] halfak: I am, of course, speaking in this moment not as stuff, but as a community bureaucrat there, willing and able to help out. ;-) [22:02:31] milimetric: ​You could do both – /top-last/{project}/{access}/{days-in-the-past} and /top-range/{project}/{access}/{start}/{end} I guess? [22:06:00] * halfak gets sucked into reading RFC comments [22:06:10] halfak: Nooooo! ;-) [22:14:39] James_F: both would be ok with me, if people spoke up and represented those use cases [22:14:46] but I don't wanna just do it 'cause it's cool to slice data in many ways [22:14:48] :) [22:15:14] which it is, totally cool [22:41:10] milimetric: :_) [22:53:54] this is happening in SF - http://www.meetup.com/Reactive-Systems/events/225292151/