14:01:02 #startmeeting fedora-hubs 14:01:02 Meeting started Tue Oct 25 14:01:02 2016 UTC. The chair is sayan. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:01:02 The meeting name has been set to 'fedora-hubs' 14:01:12 #topic Roll Call 14:01:24 .hello vivekanand1101 14:01:25 vivek_: vivekanand1101 'Vivek Anand' 14:01:28 .hello jcline 14:01:29 jcline: jcline 'Jeremy Cline' 14:01:42 .hello devyani7 14:01:43 devyani7_: devyani7 'Devyani Kota' 14:01:44 .hello sayanchowdhury 14:01:46 sayan: sayanchowdhury 'Sayan Chowdhury' 14:01:48 .hello a2batic 14:01:53 a2batic: a2batic 'Kanika Murarka' 14:04:19 #topic Action items from last meeting 14:04:31 Break the integration of IRC Widget into small issues for easy tracking 14:04:34 sayan to check if the Plus Plus widgets needs FAS3 14:04:36 abompard push commits to a branch on his fork 14:04:38 sayan review docs PR from jcline and get it merged ASAP 14:04:40 sayan get abompard access to hubs-dev for testing as well 14:04:41 hello jogender.. 14:04:51 '.' 14:04:59 :P 14:05:03 jogender: it's .hello 14:05:14 .fasinfo jogender 14:05:15 devyani7_: User "jogender" doesn't exist 14:05:22 .fas jogender 14:05:23 a2batic: jogi96 'Jogender Kota' 14:06:02 .hello jogi96 14:06:03 jogender: jogi96 'Jogender Kota' 14:06:16 #chair vivek_ jcline a2batic devyani7_ jogender mizmo 14:06:16 Current chairs: a2batic devyani7_ jcline jogender mizmo sayan vivek_ 14:07:06 So, rtnpro and I sat down an broken down the tasks into smaller task 14:07:07 https://trello.com/b/RetFEvn2/waartaa 14:08:11 jcline PR was pushed during last meeting itself 14:08:26 sayan++ 14:08:27 jcline: Karma for sayanchowdhury changed to 16 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:08:28 and I also gave abompard access to hubs-dev 14:08:38 jcline what did your PR do? (sorry ive been out for a couple weeks) 14:08:49 mizmo, it was just documentation updates 14:09:02 sayan++ 14:09:47 jcline, ah ok cool! 14:10:00 mizmo: jcline also added vagrantfile and ansible role for provisioning 14:11:10 sayan, that does remind me, I'm not sure what we need to do to get pagure building the docs, but that would be cool. 14:11:51 pingou: I see plus plus service uses a FAS account for fas client 14:12:13 https://pagure.io/plus-plus-service/blob/master/f/plus_plus_service/lib.py#_28 14:12:15 Here is the code 14:13:56 pingou: so will this be resolved when the FAS3 is deployed? 14:14:01 jcline: sure, that would cool 14:15:37 Also I added the tags milestone that needs to be discussed during the meeting 14:15:41 https://pagure.io/fedora-hubs/issues?status=Open&tags=milestone 14:16:29 so that people who will be chairing the meeting can be see the tickets and go through them 14:16:51 oh thats great sayan! 14:16:53 Ah, that's convenient 14:17:04 ill also use that list to read through and make sure any mockup issues that came up are responded to asap 14:18:04 seems like I forgot for two tickets 14:19:11 pagure.issue.tag.added -- sayanchowdhury tagged ticket fedora-hubs#63: milestone https://pagure.io/fedora-hubs/issue/63 14:19:33 #topic IRC Widget https://pagure.io/fedora-hubs/issue/2 14:20:16 I am still working on the API for signin 14:20:50 Could not progress much because of suffering from fever the whole week :( 14:21:07 sayan, :( 14:21:18 are you feeling better now? 14:21:32 mizmo: fever gone, but cough and cold still there 14:21:47 It's more that 2 weeks now :( 14:21:51 but recovering 14:22:12 To track the progress of the work you can track here https://trello.com/c/8bBtyah1/20-signup-basic-auth 14:23:01 I have broken into small task so that it's easier to track on what's going on waartaa 14:23:02 Oof, hope you get better soon :( 14:23:10 cool 14:23:22 do you need any mockups / changes to the waartaa mockups sayan? 14:23:29 mizmo: no 14:23:44 mizmo: I will ping when I need 14:23:52 cool :) 14:24:14 mizmo: also the chat page work is stalled because the contributor who was working seems to having a lot of office work right now 14:24:51 Also, I updated rtnpro with matrix.org so that he can start looking into integrating it with ircb 14:25:27 sayan, oh sweet! 14:25:35 matrix integration seems like a really smart idea 14:26:14 moving to next ticket 14:26:34 #topic Manage Bookmarks Widget (Modal) https://pagure.io/fedora-hubs/issue/11 14:26:45 devyani7_: what's your update on this ticket? 14:26:56 sayan: it will likely still have to use a fas account, but w/ FAS3 it could use token instead of password 14:27:34 pingou: ok 14:27:42 sayan, I don't have any updates *this* week exactly, 14:28:34 devyani7_: Can you update on what part you are working on this ticket? 14:28:40 am yet to work on the 3-layer of the vertical bookmark bar 14:28:55 pagure.issue.comment.added -- duffy commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36324 14:28:56 pagure.issue.comment.added -- duffy commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36326 14:28:57 pagure.issue.comment.added -- duffy commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36326 14:28:58 pagure.issue.comment.added -- duffy commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36326 14:28:59 pagure.issue.comment.added -- ralph commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36326 14:29:01 pagure.issue.comment.added -- riecatnor commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36326 14:29:02 pagure.issue.comment.added -- ralph commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36326 14:29:03 pagure.issue.comment.added -- mattdm commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36326 14:29:04 pagure.issue.comment.added -- ralph commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36326 14:29:05 pagure.issue.comment.added -- mattdm commented on ticket design#374: "UX feedback on fedmenu" https://pagure.io/design/issue/374#comment-36326 14:29:36 devyani7_: ok 14:29:46 * devyani7_ nods 14:29:58 pagure.issue.comment.added -- duffy commented on ticket design#427: "Fedora specific mailman3/hyperkitty favicon" https://pagure.io/design/issue/427#comment-37398 14:30:20 #topic Badges Widget for Project/Teams (with Path Support) https://pagure.io/fedora-hubs/issue/17 14:30:51 these notifications are not recent? 14:30:59 O.o 14:31:12 devyani7_: someone is importing the issues to pagure 14:31:26 vivek_, oh, i see. 14:31:38 * a2batic wonders the same 14:31:45 :P 14:31:57 I need to start working on this. I will some time this week to write the backend 14:32:28 s/will/will squeeze/ 14:33:03 #topic Current status in release cycle widget https://pagure.io/fedora-hubs/issue/63 14:33:22 vivek_: what's the update on this ticket? 14:33:41 about nothing has happened apart from saptaks doing some front end work 14:34:03 yeah, saptaks showed me the frontend work 14:34:13 i asked ralph just now about the pdc he was talking about in the issue 14:34:38 his msg: PDC doesn't have that data yet. better to rely on other release schedule data sources if you have them. 14:35:00 I have told him to integrate that as a widget with dummy data 14:35:09 cool 14:35:20 vivek_: did you ask how to get it integrated with PDC? 14:35:32 or should we directly use the other data sources? 14:35:39 nope. i was hoping he will update the ticket 14:36:04 (as i didn't ask him rather, showed your comment) 14:36:34 vivek_: ok 14:37:08 i will talk to him more as he is awake now 14:37:28 vivek_: Ok, It will be good if you can update the ticket with the details 14:37:36 cool 14:37:45 just a silly q, what is PDC 14:38:23 mizmo: https://pdc.fedoraproject.org/ 14:38:45 sayan++ thanks :) 14:38:45 mizmo: Karma for sayanchowdhury changed to 17 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:38:49 https://github.com/product-definition-center/product-definition-center 14:39:00 mizmo: https://fedoraproject.org/wiki/Changes/ProductDefinitionCenter 14:40:22 #topic Badges Widget for User Profiles https://pagure.io/fedora-hubs/issue/85 14:40:55 mizmo: I need help on this for the classes 14:41:21 * sayan looks for the code branch 14:43:24 seems like I haven't pushed the code. will push the code after the meeting 14:45:41 sayan, okay cool i can write them. does your code spit out the text unstyled right now? 14:45:55 mizmo: yes, it does 14:46:02 sayan, awesome that makes it super easy for me. 14:46:39 mizmo: okay I will push the code after the meeting or later tonight 14:46:46 and ping you when done 14:47:38 #topic #halp/help widget: Default in the CommOps Hub https://pagure.io/fedora-hubs/issue/98 14:47:43 abompard: are you around? 14:48:09 yeah 14:48:19 sayan, sounds good 14:48:45 abompard: can you update on the issue https://pagure.io/fedora-hubs/issue/98 14:51:43 sayan: yeah sure! 14:51:48 sorry for missing the meetings folks 14:51:52 will read the log 14:52:02 abompard: no issues 14:52:37 sayan: about issue 98, do you need more details from me? 14:52:52 actually, mizmo, could you have a look at https://pagure.io/fedora-hubs/issue/98 ? 14:53:03 I have a design question 14:53:29 abompard, sure 14:53:30 * mizmo takes a look 14:54:08 abompard: no, update on what you did last week on this ticket 14:54:14 abompard, so there should be a notion of an irc channel associated with a hub, i dont know where/how that is stored, 14:54:29 sayan: gotcha 14:54:30 abompard, but the design of the irc config is such that a hub admin can associate a specific IRC channel to that hub 14:54:56 where you might run into an issue is where a #halp is used in a channel not associated with a hub yet... at which point maybe it could be categorized as 'general' 14:55:11 mizmo: yeah, like the meeting channels 14:55:13 (does that make sense?) 14:55:16 yeh exactly 14:55:20 although 14:55:23 okay that is tricky too 14:55:27 mizmo: I'll look for the IRC-Hub association somewhere 14:55:28 if someone calls for help during a meeting.... 14:55:34 the meeting should be associated with a team 14:55:43 so this is pretty complicated 14:56:07 i think meetbot fedmsgs have a field that says what team the meeting is for 14:56:21 but i dont know if when you're looking for halp you're looking at meetbot stuff only? 14:56:25 or general irc? 14:56:45 so maybe your irc-hub association is really the team name in the meetbot fedmsg => a hub 14:56:46 ? 14:57:01 mizmo: I'm looking at the fedmsg 14:57:23 mizmo: yeah, I wonder if we have that data somewhere 14:57:36 abompard, well the meetbot stuff is a little sloppy unfortunately :( 14:57:38 mizmo: that would solve my problem 14:57:57 for example, there's seperate fedora-design and design-team 'teams' in meetbot 14:58:02 but it's all the same team 14:58:12 so looking up our meeting minutes is a bit tough :-/ 14:58:37 maybe we need to do some kind off mapping 14:59:14 yeh 14:59:23 i think each team needs some kind of way to look up its assets 14:59:31 eg meetbot, irc channel, mailing list, ticket system, etc 15:00:22 yeah, that seems like a generic hub config, not a widget config 15:00:48 because for example the IRC chans would be used by multiple widgets 15:01:12 abompard: yes, it should be a generic config 15:02:24 too many teams here https://meetbot-raw.fedoraproject.org/teams/ 15:05:06 since we are overtime let's discuss this after meeting 15:05:20 jcline: btw, can you tell the issue you were planning to workon? 15:05:28 the one related to fmn 15:06:13 sayan: there is an issue on the overview of the project page 15:06:19 sayan, right now I'm working on fmn.sse and have got a pretty significant backlog of issues to work through before it's ready 15:06:50 After that I assume hubs is supposed to consume those messages to populate the dashboard? 15:06:51 jcline: no issues, I'll just add the tag milestone to it 15:07:19 jcline: yes, display the feed 15:07:24 sayan, : I tried to look into the documentation but, on the overview tab, both documentation and development guide are saying that the site cannot be reached. 15:07:35 jogender: oh! yes 15:07:39 need to look into that 15:08:10 #endmeeting