14:03:06 #startmeeting fedora_hubs 14:03:06 Meeting started Tue Aug 23 14:03:06 2016 UTC. The chair is sayan. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:03:06 The meeting name has been set to 'fedora_hubs' 14:03:07 o/ 14:03:14 #topic Roll Call 14:03:21 .hello sayanchowdhury 14:03:23 sayan: sayanchowdhury 'Sayan Chowdhury' 14:03:23 .hello pfrields 14:03:25 stickster: pfrields 'Paul W. Frields' 14:03:31 .hello a2batic 14:03:32 a2batic: a2batic 'None' 14:04:20 #chair stickster a2batic mizmo 14:04:20 Current chairs: a2batic mizmo sayan stickster 14:04:58 let's move ahead 14:05:05 #topic status update 14:05:17 a2batic: do you want to go ahead? 14:05:40 mizmo, I have set up hubs on my machine 14:06:23 a2batic: afaik you will be helping us with the mockups, right? 14:06:58 sayan, ya mockups and i can help with UI as well 14:07:09 a2batic: great 14:07:53 I don't have much to update from the last week 14:08:28 I *memorized* bootstrap common layout things, and was trying to build a skeleton for waartaa 14:08:43 and removed patternfly as we discussed last meeting 14:09:12 On the badges front, I worked on the existing patches for the Paths 14:09:20 based on the suggestion by pingou 14:09:35 I have waiting for pingou to check the PR's once 14:09:47 s/have/am 14:10:00 mizmo: around? 14:10:32 Last week skrzepto worked on the Plus Plus backend 14:10:50 which got merged and we have ready PR for the frontend too. 14:11:07 https://pagure.io/fedora-hubs/pull-request/251 14:11:07 skrzepto_away++ 14:11:47 a2batic: would be great to have your thoughts on the issue ^^ 14:13:18 * a2batic having a look 14:13:39 We need to triage the issues from #32 https://pagure.io/fedora-hubs/issues 14:14:14 sayan, am now, sorry was refilling my drink 14:14:14 and set the proper priority to it 14:14:44 do we want to do that now or set up a separate triage meeting 14:15:06 mizmo: since we have time, we can triage a few 14:15:25 Also should we start reviewing the Hubs Roadmap again - https://etherpad.gnome.org/p/fedora-hubs-roadmap 14:15:47 * mizmo looks at roadmap\ 14:16:07 (taking a while to load) 14:16:21 The sooner we triage the issues the better because then we can try to get more contributors 14:16:30 and forward them to the right issue 14:16:43 to keep the pace 14:17:31 okay for the new roadmap, there's meeting minutes from a couple of weeks ago that should help, one sec 14:17:42 https://lists.fedoraproject.org/archives/list/hubs-devel@lists.fedoraproject.org/thread/KWK7D2HKPSNMIQ43KULIJK4J2ZKDFGEK/ 14:18:05 why dont we have a roadmap section in the pagure.io README for hubs so it's easily found? 14:18:20 +1 14:18:21 i can basically copy the set of featuers we came up with for oct 13 milestone into that 14:18:23 okay cool 14:18:36 #action mizmo to copy latest roadmap into pagure README for hubs (https://lists.fedoraproject.org/archives/list/hubs-devel@lists.fedoraproject.org/thread/KWK7D2HKPSNMIQ43KULIJK4J2ZKDFGEK/) 14:18:48 we should archive the old one too bc it has some useful workflow stuff 14:18:58 #action mizmo to archive old roadmap file into hubs repo 14:19:03 mizmo: right 14:19:21 mizmo: did you get to see the mockups needed for waartaa? 14:19:28 sayan, i did, i was just about to ask about that 14:19:54 sayan, we can put subscribe icon instead of button with "subscribe" alt 14:20:12 sayan, on the other side i was wondering if there's anything already in place or is this basically a clean / from fresh design? 14:20:36 mizmo: clean, fresh design 14:20:50 sayan, okay great, just wanted to make sure there wasnt any pre-existing bits it needed to have incorporated 14:21:50 sayan, ill start on those this week 14:21:57 mizmo: thanks :) 14:22:06 mizmo++ 14:22:24 mizmo: we are having PyCon India just after 1 month 14:22:35 and we are demoing waartaa there 14:23:03 PyCon India would be a great place to find new contributors for Hubs 14:23:11 sounds great! 14:23:31 sayan, can you add me as a member in the github waartaa group? that way i can assign the mockup tickets to myself 14:23:36 mizmo: sure 14:24:09 have we had any zanata updates? who is working on that? 14:24:56 mizmo: no, we don't have any updates :( 14:25:35 what do we need to make progress there? 14:25:39 are we waiting on alex's team? 14:25:50 mizmo: yes, the last mail that we got from alex 14:25:53 do we need to assign it to someone? 14:26:35 i think they were going to send us sample output, right? 14:26:39 did we receive that? 14:26:48 yes, that's what I knew 14:27:05 mizmo: let me write a mail again to him 14:27:17 also we need to get contributors to get the code work going 14:27:43 Maybe posting a blog post on the community blog will help us get few contributors 14:28:11 okay cool 14:28:23 #action sayan to contact alex for update on zanata / sample output we can use to move forward 14:28:36 do we have specific things we want to assign new contributors yet? 14:28:54 she isn't able to make it today, but i have been working with a woman who is interested in applying for an outreachy internship to help with hubs UX work 14:29:04 although we need more devs :) 14:29:11 mizmo: yes, more devs 14:29:14 * stickster would love to see another dev through outreachy 14:29:32 we should get into that process and add a dev slot too 14:29:42 i think it'll start soon (the applicatoin process) 14:29:54 mizmo: we can give the contributors the Normal priority task 14:30:11 sayan, ok, up to #32 at this point right since the rest aren't triaged for priority 14:30:22 Applications for the program will open on September 5 and the deadline for applying will be October 17. <= outreachy 14:30:24 mizmo: should we go ahead and triage a few issues 14:30:44 well i wanted to go down the list of roadmap features and make sure we're moving forward with each 14:31:03 #action mizmo to investigate adding hubs positoins to outreachy (ux/dev / apps open up sep 5) 14:31:11 then we'll do triage? 14:31:24 IRC integration is the next feature - no blockages on that one right? 14:31:32 basically im starting on mockups for waartaa today 14:31:44 and i will try to create docs for fedora-bootstrap along the way 14:33:45 sorry got disconnected 14:33:48 internet went down 14:34:08 it's all good 14:34:14 mizmo: that's sounds good 14:34:27 is there anything else blocking waartaa work or is that progressing ok? 14:34:38 no 14:35:01 let triage the next few issues 14:35:06 #topic https://pagure.io/fedora-hubs/issue/33 14:35:36 ok, theres 3 more features on the list but maybe we can talk about them at the end 14:35:42 Request New Meeting Feature 14:36:10 i think it should be prioritized how we did the other meeting feature tickets.... 14:36:33 so it sohuld be normal 14:36:35 mizmo: this should go to normal 14:36:55 pagure.issue.edit -- duffy edited the priority fields of ticket fedora-hubs#33 https://pagure.io/fedora-hubs/issue/33 14:37:07 https://pagure.io/fedora-hubs/issue/34 14:37:07 #topic WikiTree Widget https://pagure.io/fedora-hubs/issue/40 14:37:19 oh thats fixed 14:37:24 (34 - sorry ) 14:37:30 Does the triage here get reflected in the roadmap EP too? 14:38:00 stickster, i think what we're going to do is start using the README file in pagure to store the roadmap, and the latest roadmap is here: https://lists.fedoraproject.org/archives/list/hubs-devel@lists.fedoraproject.org/thread/KWK7D2HKPSNMIQ43KULIJK4J2ZKDFGEK/ 14:38:13 Ah OK -- that's helpful 14:38:15 and we're basically marking anything relating to the 5 roadmap features as high, everything else normal or low 14:38:41 stickster: but then we can assign the contributors normal/low tickets 14:38:50 sayan, i think 40 would be awesome, but theres no mockup, and im not sure if lmacken ever found his code 14:38:58 we should probably ping lmacken on this one. 14:39:07 my guess is it assocaites a wiki namespace with a team which would be uber useful 14:39:12 let's set it normal 14:39:19 #action sayan ping lmacken on the issue #40 14:39:32 pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#40: "WikiTree Widget" https://pagure.io/fedora-hubs/issue/40#comment-4186 14:39:33 pagure.issue.edit -- duffy edited the priority fields of ticket fedora-hubs#40 https://pagure.io/fedora-hubs/issue/40 14:39:44 mizmo: yes, but that's seems like a interesting feature to workon 14:39:58 sayan, should it be high? 14:40:14 mizmo: keep it normal 14:40:23 okie doke 14:40:34 next is https://pagure.io/fedora-hubs/issue/43 14:40:37 Aging Hubs Feature 14:41:17 i think this one is probably low priority, it's not one of the key roadmap features *and* since the system is new and the team hubs we'll release with will be active, it won't really come into play for some time 14:41:22 set it to low? 14:41:40 yes, set it to low 14:41:48 pagure.issue.edit -- duffy edited the priority fields of ticket fedora-hubs#43 https://pagure.io/fedora-hubs/issue/43 14:41:58 but this can be a easy issue to work on 14:42:09 should we tag it with easyfix or something like that? 14:42:16 yes, I think so 14:42:37 pagure.issue.tag.added -- duffy tagged ticket fedora-hubs#43: easy https://pagure.io/fedora-hubs/issue/43 14:42:53 https://pagure.io/fedora-hubs/issue/44 Manual Hub Archiving Feature 14:42:58 this one is similar; rather than automatic it's manual 14:43:03 same thing - low priority, tagged easy? 14:43:15 +1 14:43:19 pagure.issue.tag.added -- duffy tagged ticket fedora-hubs#44: easy https://pagure.io/fedora-hubs/issue/44 14:43:20 pagure.issue.edit -- duffy edited the priority fields of ticket fedora-hubs#44 https://pagure.io/fedora-hubs/issue/44 14:43:32 Same for the next one too https://pagure.io/fedora-hubs/issue/45 14:43:37 okie doke 14:43:51 pagure.issue.tag.added -- duffy tagged ticket fedora-hubs#45: easy https://pagure.io/fedora-hubs/issue/45 14:43:52 pagure.issue.edit -- duffy edited the priority fields of ticket fedora-hubs#45 https://pagure.io/fedora-hubs/issue/45 14:44:08 https://pagure.io/fedora-hubs/issue/47 14:44:12 Local, Regional, National, Continental Hubs 14:44:38 I think should go as a low priority 14:44:42 this one needs more UX thought, not one of the priorities on the roadmap, i would make it low as well 14:45:01 pagure.issue.tag.added -- duffy tagged ticket fedora-hubs#47: needsdiscussion https://pagure.io/fedora-hubs/issue/47 14:45:02 pagure.issue.edit -- duffy edited the priority fields of ticket fedora-hubs#47 https://pagure.io/fedora-hubs/issue/47 14:45:21 https://pagure.io/fedora-hubs/issue/50 14:45:24 Mobile app for Hubs 14:45:34 so there is an intern in the bangalore office who might be interested in this one 14:45:40 but i haven't heard from her in a few days 14:45:51 i found some folks local to her to help her get fedora installed so she could get a dev env up 14:46:03 i dont know if the prioirty should be high though, i think it should be normal 14:46:39 mizmo: do you mean responsive 14:46:45 or a seperate mobile app? 14:47:12 sayan, well we need both.... codeblock wanted to make a separate mobile app, but we need to work on responsive too 14:47:39 mizmo: hmm, ReactJS apps can directly convert ot React Native 14:47:53 s/ot/to 14:48:26 ooh 14:48:32 that might be nice 14:48:44 #link https://facebook.github.io/react-native/ 14:48:45 relrod, do you have react experience? would you be willing to do the fedora mobile app using react? 14:48:51 ill add a note to the ticket about that 14:49:48 pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#50: "Mobile app for Hubs" https://pagure.io/fedora-hubs/issue/50#comment-4187 14:49:49 pagure.issue.edit -- duffy edited the priority fields of ticket fedora-hubs#50 https://pagure.io/fedora-hubs/issue/50 14:49:54 so, if we build the UI using React, you don't need to worry about the mobile app 14:50:13 it's native, that's what the link says 14:50:49 oh ok great 14:50:53 so what should we do with the ticket 14:51:02 how does react format for mobile - does it use the responsive CSS? 14:51:45 ^^ don't know much on that 14:52:03 okay maybe we should keep ticket open to investigate? 14:52:07 Yes 14:52:37 if not feasible, maybe go for a Java app :) 14:52:44 pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#50: "Mobile app for Hubs" https://pagure.io 14:52:49 s/java/dalvik (sp?) 14:53:16 * sayan is a total noob on mobile apps 14:53:47 dalvik seems discontinued https://en.wikipedia.org/wiki/Dalvik_(software) 14:54:14 let the ticket be open we can look into it later 14:54:29 sure next is 14:54:30 https://pagure.io/fedora-hubs/issue/52 14:54:35 IRC Chat Notification Icon + Dropdown 14:54:45 Nedd to think upon this one 14:54:53 s/Nedd/Need 14:55:06 since it's part of the irc feature should it be high? 14:55:10 i can add "needsdiscussion" tag 14:55:27 sure 14:55:35 would you like it assigned to you? 14:55:45 pagure.issue.tag.added -- duffy tagged ticket fedora-hubs#52: needsdiscussion https://pagure.io/fedora-hubs/issue/52 14:55:53 mizmo: yes, you can assign it to me 14:56:10 pagure.issue.assigned.added -- duffy assigned ticket fedora-hubs#52 to sayanchowdhury https://pagure.io/fedora-hubs/issue/52 14:57:07 https://pagure.io/fedora-hubs/issue/57 14:57:12 PlusPlus Widget 14:57:13 let's move this issue to high, skrzepto_away already worked on the backend for the project 14:57:20 and merged 14:57:26 should it be assigned to him? 14:57:30 and the frontend is a waiting PR https://pagure.io/fedora-hubs/pull-request/251 14:57:31 is it finished or is more work needed? 14:57:41 pagure.issue.edit -- duffy edited the priority fields of ticket fedora-hubs#57 https://pagure.io/fedora-hubs/issue/57 14:57:59 i think it was waiting on the user metadata box to be finished 14:58:19 mizmo: which is blocked on FAS3 14:58:27 pagure.issue.assigned.added -- duffy assigned ticket fedora-hubs#57 to skrzepto https://pagure.io/fedora-hubs/issue/57 14:58:33 should we release this someway to have the feature in 14:58:48 and move it to the user metadata widget when it's ready? 14:58:55 we should have the user metadata box just not have the FAS3 info for now I think 14:59:16 mizmo: ok 14:59:18 i dont think it's a good idea to launch a feature then move it around bc of development issues - i think we could still put a user metadata box and jsut have the ++ info in it 14:59:48 mizmo: that's sounds good 15:00:16 pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#57: "PlusPlus Widget" https://pagure.io/fedora-hubs/issue/57#comment-4188 15:00:26 sayan, ok who can do that work? is skrzepto_away's internship over at this point or can he do this? 15:00:41 mizmo: let me add a comment to the user metadata ticket 15:01:01 if devyani does not reply, a2batic do you want to help here? 15:02:19 mizmo: let's keep this open. 15:02:25 and not assigned 15:02:32 ok 15:02:37 pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#57: "PlusPlus Widget" https://pagure.io 15:02:38 * mizmo clears assignee 15:02:47 pagure.issue.assigned.reset -- duffy reset the assignee of ticket fedora-hubs#57 https://pagure.io/fedora-hubs/issue/57 15:02:54 we are at 1 hour, so maybe we should end the meeting here 15:02:58 sounds good 15:03:04 so we're at #57 so far 15:03:10 yes 15:03:16 #info we've triaged up through ticket #57 at this point for priority / assignee 15:03:21 #topic Open Floor 15:03:26 sayan, yes I can help with UI 15:03:47 a2batic: cool, let's talk after the meeting 15:03:56 sayan, cool 15:04:06 mizmo: we had this page with screenshots with waartaa's earlier version 15:04:07 http://www.waartaa.com/features/ 15:04:17 sayan, oh great, this is super useful 15:04:33 do you need anything to help recruit folks at pycon india, flyers or anything like that 15:04:47 kushal: ^^ 15:05:07 mizmo, I will get back to you by tomorrow 15:05:11 kushal, okie doke 15:05:17 kushal: +1 15:05:27 we are good to end? 15:05:35 i think so! thanks everybody :) 15:05:42 #endmeeting