15:00:37 #startmeeting fedora_hubs 15:00:37 Meeting started Tue Nov 29 15:00:37 2016 UTC. The chair is sayan. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:37 The meeting name has been set to 'fedora_hubs' 15:00:59 #topic Roll Call 15:01:10 .hello pfrields 15:01:12 stickster: pfrields 'Paul W. Frields' 15:01:38 pingou: devyani7_ a2batic mizmo1 abompard jcline meeting time 15:01:45 vivek|mob: saptaks ^^ 15:01:52 .hello sayanchowdhury 15:01:56 sayan: sayanchowdhury 'Sayan Chowdhury' 15:01:56 .hello jcline 15:02:02 jcline: jcline 'Jeremy Cline' 15:02:04 .hello abompard 15:02:06 abompard: abompard 'Aurelien Bompard' 15:02:08 .hello saptaks 15:02:09 saptaks: saptaks 'Saptak Sengupta' 15:02:50 .hello a2batic 15:02:51 a2batic: a2batic 'Kanika Murarka' 15:03:07 * pingou here 15:03:47 #topic Action Items from last week 15:04:13 * devyani7 15:04:14 * sayan to setup time with devyani7 to check issues with hubs setup 15:04:16 * sayan 15:04:18 * sayan to test the halp_widget branch 15:04:20 * sayan to setup time with devyani7 to check issues with hubs setup 15:04:22 * **UNASSIGNED** 15:04:24 * (none) 15:04:28 oops copied from the wrong place 15:04:38 * sayan to test the halp_widget branch 15:04:40 * sayan to setup time with devyani7 to check issues with hubs setup 15:05:40 I did not setup time with devyani7 but I tried to check for the issue she reported https://pagure.io/fedora-hubs/issue/275 15:05:49 but could not reproduce it 15:06:00 Can somebody else try to reproduce this issue? 15:06:06 saptaks: jcline ^^ 15:06:28 sayan, yeah, I will look into that 15:06:49 the vagrant development and the manual setup both works fine for me 15:07:20 #chair stickster jcline abompard a2batic saptaks 15:07:20 Current chairs: a2batic abompard jcline saptaks sayan stickster 15:07:23 Here (sorry late) 15:07:28 #chair mizmo1 15:07:28 Current chairs: a2batic abompard jcline mizmo1 saptaks sayan stickster 15:07:36 It looks like it might be a dependency of a dependency had a problem which then perhaps got fixed 15:07:45 I'll see if it's still happening, though 15:08:00 jcline: you faced the same issue? 15:08:18 No, I was just reading the error fpaste 15:08:44 Yeah I doubted the dependencies in the package.json is throwing that error 15:09:36 #action sayan to test the halp_widget branch 15:09:50 #action sayan to setup time with devyani7 to check issues with hubs setup 15:09:56 sayan: lI think her vagrant has npm3 which doesn't get the peer dependency. So maybe they need to be mentioned explicitly. 15:10:27 saptaks: I have npm3 locally 15:10:44 But the manual installation was fine 15:11:02 yeah, needs react-dom@15.4.0 apparently? 15:11:02 It's good to have more eyes on a JS issue :) 15:11:12 I also have npm3 locally and it works fine. But that is what I get on googling and there is a lot of issues around this. 15:11:36 stickster: the error does suggest that I think as well 15:13:01 saptaks: which version of node are you running? 15:13:50 Moving to tickets 15:15:00 I have kept work on waartaa on halt 15:15:02 sayan: seems like I am using npm 2.15 15:15:10 saptaks: and node? 15:15:50 4.5 15:15:51 #topic Badges Widget for Project/Teams (with Path Support) https://pagure.io/fedora-hubs/issue/17 15:16:16 saptaks: ok, I saw in a GH issue that it was suggested to use Node 6 15:16:26 and I am right now on Node 6 15:16:46 mizmo1: you can starting working on this branch 15:16:54 s/branch/issue 15:17:39 sayan: do you have it checked into devel or is there a fork like last time? 15:17:58 mizmo1: the branch name is badge-path-support, and the template would be widgets/templates/badgespath.html 15:18:09 mizmo1: in my fork 15:18:10 okay thanks! 15:18:20 #action mizmo to start working on css/html for badges path widget, branch is badge-path-support 15:18:42 pingou: is it possible to know the current hub name? 15:18:59 current hub name as in the name of the hub user is in? 15:19:46 sayan: I think so 15:20:17 pingou: anywhere we have used it earlier? 15:20:34 w/i a widget? right? 15:21:06 pingou: yes 15:21:31 so widget in the db have a 'hub_id' 15:21:42 so we could use a relation to get .hub 15:21:59 self.hub.name, in __repr__ of widget 15:21:59 oh ok 15:22:35 yeah! that's what I needed 15:22:37 thanks 15:22:49 cool :) 15:23:36 moving to next ticket 15:23:46 #topic Current status in release cycle widget https://pagure.io/fedora-hubs/issue/63 15:24:09 saptaks: what's the update on this ^^ 15:24:53 sayan: I am yet to send a Pull Request. Frontend work I have done 15:25:06 I will send a Pull Request tonight 15:25:18 vivek_: has been working on the backend part of it 15:25:59 sayan: I have created the 2 views that can be toggled in between as discussed in last to last meeting 15:27:32 saptaks: ok 15:28:03 saptaks: can you update that to the ticket? 15:29:28 sayan: I will update it tonight. 15:30:51 #topic Badges Widget for User Profiles https://pagure.io/fedora-hubs/issue/85 15:30:59 I will send a PR for this 15:31:23 #action sayan to send PR for the issue 85 15:31:47 #topic #halp/help widget: Default in the CommOps Hub https://pagure.io/fedora-hubs/issue/98 15:31:53 abompard: ^^ 15:32:22 Not much more results to report this week 15:32:29 I started looking into errbot 15:32:45 but I'll need to talk to the openstack guys to know what their status is 15:32:56 I'll send them another email asap 15:33:04 abompard: No response from openstack guys? 15:33:07 nop 15:33:10 :-( 15:33:12 :( 15:33:16 yeah :-/ 15:34:04 #action abompard to drop a mail to openstack folks to know their status 15:34:07 persistence pays :-) 15:34:18 yeah :-) 15:34:33 Yeah 15:34:40 a2batic: what's your status now? 15:34:45 is your exams over? 15:34:54 * stickster encourages folks to pipe up here in channel if needed... don't have to wait for a meeting :-) 15:35:15 sayan, I have resumed my work on issue #261 15:35:29 a2batic: great 15:35:54 No, not yet, I have stude leave this week, I will try to complete 15:36:02 *study 15:36:06 a2batic: can you drop a plan to the mailing list? that would be good 15:37:08 sayan, plan about issue #261 or #261 #262 #263 together ? 15:37:35 a2batic: yes, better before that it would be good to see how is the zanata2fedmsg plugin working now 15:38:35 sayan, but zanata2fedmsg is working, right ? 15:39:56 * sayan dig for the zanata issue 15:41:11 https://zanata.atlassian.net/browse/ZNTA-1166 15:41:15 #link https://zanata.atlassian.net/browse/ZNTA-1166 15:41:26 * a2batic clicks 15:43:14 sayan, I thought it has been fixed :/ 15:43:33 a2batic: did not get you fixed as in? 15:43:43 status is shown as Merged 15:44:26 a2batic: yeah so the thing is they added the webhook 15:44:41 zanata2fedmsg needs to be tested against that webhook 15:45:02 you can see the last message with the payload 15:45:23 * a2batic nods 15:45:35 zanata2fedmsg receives that via webhook and publishes it to fedmsg 15:45:48 a2batic: can you test that with zanata2fedmsg? 15:46:21 and see the payload for each of the webhook 15:46:35 before moving ahead and writing the plan? 15:46:53 sayan, ok, I will do this after the meeting today 15:47:04 a2batic: great 15:47:24 #action a2batic to test zanata2fedmsg plugin with the new webhook endpoints 15:47:33 Moving to open floor 15:47:38 #topic Open Floor 15:48:12 Anyone want to share something? 15:48:30 if anybody needs mockups for anything or updated mockups let me know :) 15:48:39 i updated the mocks for the bookmarks bar on devyani's ticket 15:49:09 mizmo++ 15:49:27 we are set from the mockup point right now 15:50:40 going over and ending the meeting then 15:50:49 #endmeeting