15:02:48 #startmeeting hubs-devel 15:02:48 Meeting started Tue May 2 15:02:48 2017 UTC. The chair is sayan. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:48 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:48 The meeting name has been set to 'hubs-devel' 15:02:55 #topic Roll Call 15:03:02 Hey im on the train, going to work at the rh summit today 15:03:15 .hello abompard 15:03:16 abompard: abompard 'Aurelien Bompard' 15:03:33 .hello jcline 15:03:34 jcline: jcline 'Jeremy Cline' 15:03:47 mizmo: sure, np 15:04:00 .hello sayanchowdhury 15:04:00 sayan: when I look at https://apps.fedoraproject.org/calendar/location/fedora-hubs%40irc.freenode.net/ I the meeting time at one hour ago 15:04:01 sayan: sayanchowdhury 'Sayan Chowdhury' 15:04:24 abompard: yeah, we did not change back after the DST 15:04:48 and I believe it was at 14UTC last week 15:04:58 so what's the right time? 15:05:20 oh 15:05:42 abompard: 14UTC should be the time, but we usually dicuss after the DST changes 15:05:45 Yeah, it's been really confusing for me. I'd prefer we pick a UTC time and stick with it, ignoring DST 15:06:10 jcline: yes 15:06:53 in that case let's just follow 14UTC 15:06:59 cool :) 15:07:18 #chair abompard jcline 15:07:18 Current chairs: abompard jcline sayan 15:08:10 #topic Status Updates 15:08:26 abompard: do you want to go ahead and update on what are you working on? 15:08:58 yes 15:09:17 so, I'm working on the backend to the Feed widget and the Stream page 15:09:40 there's currently no backend, all data comes from the actions.json file in the source code 15:10:05 so I'm working on plugging that in fedmsg 15:10:40 My current design will be to store each user's feed and stream items in Redis, that we already use for the work queue 15:11:14 this way it's easy to limit in size, and Redis makes more sense than SQLAlchemy in that case since it's transient data 15:12:00 I also keep in mind that we want the UI to auto-update 15:12:11 Sounds sensible to me 15:12:13 but I haven't started working on the SSE server itself 15:12:56 it's shouldn't be too hard to implement though 15:13:11 abompard: since the Feed is based on React, it should be auto updating itself 15:13:15 To get the user notifications from the bus, I need FMN to edit them 15:13:27 based on the state changes? 15:13:57 sayan: yeah except the state changes must arrive in React in some way, and that's where the SSE (EventSource) server comes into play 15:14:16 abompard: yes, that updates the state 15:14:53 abompard: what do you mean by "I need FMN to edit them" ? 15:14:55 sayan: yup. Well, this EventSource server needs to be written, but it's a simple protocol, that's why I think it shouldn't be too hard 15:15:07 sayan: ah, sorry, s/edit/publish/ 15:15:18 I don't know why I wrote "edit" :) 15:15:32 currently FMN doesn't push notifications on the bus 15:15:33 make sense now :) 15:15:36 only via email and irc 15:16:21 On that front, I've started on a fedmsg backend for FMN. It should be pretty simple, I just need to think about how groups tie into FMN and if that's generally useful or only helpful for Hubs. 15:16:50 cool 15:17:27 I haven't worked on group notifications yet, but I'm keeping it in mind, it shouldn't be too hard to insert this case in the code when I arrive at that point 15:17:29 I *think* I can probably do the backend without having the group work in and then add that later, but I need to do some research 15:18:58 So yeah, I'm still away from the testing phase even limited to user Feeds (no notifications), but I'm getting there 15:19:18 abompard: cool 15:19:55 I guess that's all for me :) 15:19:59 abompard: can you create ticket for this "Feed Widget and Stream page"? 15:20:05 and update it there too? 15:20:15 Right, will do 15:20:34 We already have a ticket for Feed Widget and Stream page seperately 15:20:44 you can mention those ticket too 15:21:38 Going ahead with my update 15:22:32 I am still continuing with the packaging of the irc-bridge, right now I am handling the dependencies for nodejs babel 15:23:39 jsmith replied to mail today that he too has been working on packaging nodejs babel but he is stuck with lodash 15:24:21 lodash is packaged but babel needs a updated package 15:25:11 abompard: jcline: seems like the irc brige has a huge list of dependencies and would need some time 15:25:24 so we can use the matrix.org irc bridge in the beginning 15:25:56 Yeah 15:26:13 I did a setup of local instance of matrix homeserver and started working on https://pagure.io/fedora-hubs/issue/284 15:26:49 * jcline[m] waves from the bridge 15:27:37 * yudocaa[m] waves back 15:28:22 so probably I am hoping to have some update on the ticket #284 by next week 15:29:13 \o/ 15:29:26 btw, I am also planning to filter out the issues for flock demo this week so that we can working towards them 15:29:57 jcline: what's the update on the review request on the synapse package? 15:30:08 I saw bowlofeggs comment on the ticket 15:30:51 Yeah, I poked him about a review, but he didn't want to step on toes, so I'll continue poking people 15:33:40 cool 15:34:17 jcline: abompard: I would be afk from Jan 14th for 2 weeks 15:34:21 for PyCon US 15:35:46 Do you mean May? 15:35:51 oops 15:35:54 Haha :) 15:35:55 Yeah 15:36:01 I don't know why I wrote Jan 15:36:21 Cool. Get some Voodoo donuts on my behalf while you're there! 15:36:50 I've heard a lot of those 15:37:18 sure :) 15:38:01 jcline: abompard: probably next week we can focussing towards flock 15:38:18 anything else, or we can go over and end this meeting? 15:38:44 I don't have anything else 15:40:49 ending this meeting in 15:40:50 3. 15:40:52 2. 15:40:54 1. 15:40:58 #endmeeting