14:01:38 <sayan> #startmeeting hubs-devel
14:01:39 <zodbot> Meeting started Tue Apr  4 14:01:38 2017 UTC.  The chair is sayan. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:39 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:01:39 <zodbot> The meeting name has been set to 'hubs-devel'
14:01:50 <mizmo> shillman: around? i'm sending your portfolio review now
14:02:02 <sayan> #topic Roll Call
14:02:13 <sayan> .hello sayanchowdhury
14:02:14 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
14:03:00 <jcline> .hello jcline
14:03:01 <zodbot> jcline: jcline 'Jeremy Cline' <jeremy@jcline.org>
14:03:11 <abompard> .hello abompard
14:03:12 <zodbot> abompard: abompard 'Aurelien Bompard' <aurelien@bompard.org>
14:03:38 <mizmo> .hello duffy
14:03:40 <zodbot> mizmo: duffy 'Máirín Duffy' <fedora@linuxgrrl.com>
14:03:53 <sayan> #chair jcline mizmo abompard
14:03:53 <zodbot> Current chairs: abompard jcline mizmo sayan
14:04:18 <sayan> #topic IRC Widget
14:04:35 <stickster> .hello pfrields
14:04:36 <zodbot> stickster: pfrields 'Paul W. Frields' <stickster@gmail.com>
14:04:41 <sayan> jcline: what's the update on the synapse package?
14:04:43 * stickster lurking while doing release stuff for Alpha
14:04:49 <sayan> #chair stickster
14:04:49 <zodbot> Current chairs: abompard jcline mizmo sayan stickster
14:05:05 <jcline> sayan, I'm doing the scratch build for the package review submission right now
14:05:13 <jcline> In about 30 seconds it should be up for review
14:05:38 * stickster notes we were trying the packages out yesterday afternoon and they seemed to work well!
14:05:40 <sayan> jcline: last week, you talked about documentating the process of setup for the end user?
14:06:08 <jcline> sayan, yeah, I was going to write a wiki page to go along with it
14:06:44 <jcline> It's actually pretty straightforward, I set up one from the RPM yesterday and stickster helped me test it
14:06:56 <sayan> stickster++
14:06:56 <zodbot> sayan: Karma for pfrields changed to 12 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
14:07:28 <sayan> jcline: abompard: have you worked on NodeJS packaging before?
14:07:44 <sayan> I would like to have my package reviewed before sending out a review reuest
14:07:50 <sayan> s/reuest/request/
14:07:58 <abompard> sayan: nope, sorry
14:08:03 <jcline> sayan, I haven't
14:08:34 <jcline> I could still look at it, but it wouldn't be the eyes of an expert I'm afraid
14:08:53 <pingou> sayan: for nodejs review we should ping jsmith
14:08:56 <jcline> Scratch build finished, synapse review request: https://bugzilla.redhat.com/show_bug.cgi?id=1438842
14:09:26 <sayan> pingou: thanks, I dropped him an email but did not get any reply
14:09:40 <pingou> may be busy
14:09:46 <sayan> will ping him on irc once
14:09:51 <sayan> pingou: yeah
14:10:34 * stickster just hit him up in #fedorfa-devel
14:10:40 <stickster> oops, can't spell but you get my point :-)
14:12:27 <mizmo> fedorfa :)
14:12:31 <mizmo> thats kind of catchy
14:12:58 <sayan> jcline: is it possible to start writing the IRC widget with the help of the instance you have?
14:13:10 <mizmo> sayan: what component is nodejs?
14:13:11 <mizmo> synapse is python right
14:13:29 <sayan> mizmo: the irc-bridge is nodejs
14:13:32 <jcline> sayan, possibly, but I don't have the irc bridge set up yet
14:13:36 <mizmo> ah okay
14:14:24 <sayan> the point is we haven't made much development on the IRC widget after the plan to migrate to matrix
14:15:04 <jcline> Yeah. I do have a lot of other stuff on my plate, though, so I don't know how much time I could devote to it this week
14:15:04 <sayan> except that the packaging getting done.
14:15:53 <sayan> I also have a couple of things to complete this week, including deployment of the Badges Path to prod after the freeze is over
14:16:23 <mizmo> ooh that's exciting! badges path is going to be great.
14:17:02 <sayan> mizmo: yeah, this week I am mostly looking into the broken badges and the deployment of the badges path
14:17:15 <mizmo> sayan: there are broken badges?
14:17:30 <sayan> mizmo: there are a few badges that are not getting awarded
14:17:37 <mizmo> oh weird
14:18:40 <sayan> yes, so I will fixing those. One is broken for 3 years now :)
14:18:51 <mizmo> heh, nice. good find :)
14:20:10 <mizmo> we have at least a couple of other things besides badges and irc we want to try to have in place for flock
14:20:14 <mizmo> to be able to demo the design hub
14:20:35 <mizmo> the feed widget, hooked up to hyperkitty and planet, which i think abompard has been working on (rquires new api from hyperkitty right?)
14:20:52 <mizmo> and the other is fas integration for the team rosters, joining a team, that sort of stuff
14:21:00 <abompard> mizmo: I've started working on the authorization system
14:21:07 <mizmo> abompard: \o/ yay!
14:21:24 <sayan> abompard: I was going through the hyperkitty api and saw that you have already integrated DRF
14:21:37 <abompard> sayan: DRF is great :)
14:21:50 <sayan> abompard: yeah, so the api needs improvements?
14:22:07 <sayan> abompard: agreed :)
14:22:41 <sayan> API improvments before it getting integrated with hubs?
14:22:45 <abompard> sayan: with the last commits it should be sufficient, you can only query public lists but that's most of what we need at the moment
14:23:00 <abompard> it's not deployed to prod though
14:23:18 <abompard> But I can deploy it to staging if you want to test
14:24:00 <abompard> There may be some more API endpoints to add if necessary, maybe a way to change the sort order, maybe stats like the number of participants / threads / etc.
14:24:22 <sayan> abompard: awesome
14:24:27 <abompard> I'll add that when someone tells me it's needed, not before ;-)
14:24:53 <abompard> so my plan was to work on the HK widget when authz is done
14:24:56 <mizmo> iirc the feed widget shows the title of the post, links to the full thread on hyperkitty, shows the number of replies, number of participants
14:25:23 <mizmo> oh and a preview of the post. i'd like for people to be able to read the full post too (the first in the thread) and then click a link to be able to view some replies inline
14:25:37 <abompard> mizmo: yeah I should have in the API everything that I saw on the mockup
14:25:42 <mizmo> eg maybe the most recent 2 replies, to see more they should click a link to go to the thread in hyperkitty
14:25:54 <mizmo> ok great :)
14:26:03 <abompard> ah I didn't see that, but it can be done too
14:26:18 <mizmo> and just public lists is fine for now, if we're operating under the assumption that we're going to demo at flock how it'd work for the design team
14:26:25 <mizmo> actually the three teams we initially targeted all have public lists
14:26:35 <abompard> I didn't think of changing the feed widget to includ HK data, but I can try to work on that afther the HK widget is done
14:26:46 <mizmo> the way the replies worked in the mockups, the first post to the thread looks like a blog post and the replies look like blog comments
14:26:51 <mizmo> oh okay cool
14:27:36 <sayan> abompard: so you are also working on the fas integration right for authorization?
14:28:19 <abompard> sayan: I've sent an email to puiterwijk about his new API, but for full integration I think it'll have to wait after Flock
14:28:39 <abompard> There's a lot of security gotchas
14:29:17 <abompard> especially if we want write access to FAS from Hubs
14:29:39 <abompard> so I'm thinking of a way to have something working for Flock
14:29:48 <puiterwijk> I can tell that if you want write access, you're going to get to know me very well and how I do security reviews
14:29:52 <abompard> which would not be fully integrated with FAS, but would work.
14:30:14 <puiterwijk> abompard: well, I'm hoping to have the initial CAIAPI in dev somewhere next week, staging soon after that hopefully...
14:30:22 * abompard is kinda afraid of "getting to know puiterwijk very well"
14:30:56 <puiterwijk> Well, as long as you let me know in advance when I can start the review, it's not too bad...
14:30:59 <abompard> So, my plan is to have something working sooner rather than something perfect after Flock
14:31:05 <mizmo> so for a flock demo say, FAS would let us show what a hub would look like with current group members but new members could't join through hubs
14:31:17 <mizmo> perfect is enemy of good, sounds like a good plan abompard
14:32:05 <abompard> what I can do quickish, is use the existing owners / members tables in the DB.
14:32:18 <abompard> so it's not connected to FAS (except for authentication)
14:32:24 <mizmo> sounds good to me!
14:32:27 <abompard> but I can add that later when CAIAPI is done
14:32:34 <mizmo> well, and listing the owners/ members? or no?
14:32:45 <abompard> mizmo: yep
14:32:50 <mizmo> okay cool
14:32:55 <abompard> mizmo: it's actually almost done already
14:32:55 <mizmo> sounds great
14:33:01 <mizmo> wow!
14:33:05 <abompard> but it's all in the "almost" ;-)
14:33:17 * mizmo claps in excitement anyway :)
14:33:51 <abompard> BTW, I'm going to use your attention here a bit to note that the review for my Halp widget has stalled
14:34:06 <abompard> and I need to get it committed before I can send the authz PR
14:34:21 <abompard> because I need a (generic) component in the Halp widget
14:34:45 <sayan> I haven't reviewed the React code for the Halp widget yet
14:34:47 <sayan> :(
14:35:03 <abompard> so if someone wants to have a look, bowlofeggs started the review already
14:35:15 <abompard> but that was 2 weeks ago
14:35:37 <abompard> https://pagure.io/fedora-hubs/pull-request/341
14:36:14 <abompard> Anyway, here's my workplan:  1: halp widget, 2: authz, 3: HK widget, 4: HK in the Feed widget
14:36:31 <abompard> feel free to tell me if my priorities aren't in order
14:37:09 <mizmo> Well, halp widget is so close to done I'd push it, but I think 2-4 are higher priority than 1
14:37:48 <abompard> mizmo: so you'd switch 3 and 4 ?
14:37:58 <abompard> mizmo: actually I need a component of 1 to push 2
14:38:07 <abompard> that's why I've set it that way
14:38:15 <mizmo> ahh right, makes sense
14:38:22 <abompard> but 3 and 4 are totally exchangeable
14:38:38 <mizmo> abompard: i would switch 3 and 4, i see the separate widget as less fundamental than having the data in the feed widget
14:39:05 <mizmo> so 4 before 3 if there isn't a dependency there
14:39:07 <abompard> mizmo: OK, noted. I expect that I'll be able to reuse most of the code anyway
14:39:14 <mizmo> okay cool :)
14:39:31 <abompard> but I'm sometimes wrong with that :D
14:39:53 <abompard> (I'm a constant optimist for code reuse)
14:40:10 <mizmo> makes sense!
14:40:19 <mizmo> seems like we are in good shape
14:40:25 <mizmo> is there anything i can help with on the UX side?
14:40:53 <abompard> Hmm, I suspect that I'll have questions as soon as I start implementing
14:41:05 <abompard> Oh, for authz and the "preview" hubs
14:41:34 <abompard> I can set the logged-in-only visibility on the widgets, but I can't do more granular for now
14:42:00 <abompard> If you agree, I think we can aim for that one after Flock
14:42:24 <mizmo> that should be fine for Flock!
14:42:29 <abompard> cool
14:43:31 <abompard> mizmo: do you have a mockup that shows the preview and first replies thing you said about mailing-list data?
14:43:54 <mizmo> abompard: yes! lemme grab, one sec
14:46:15 <mizmo> abompard: blob:http://imgur.com/15a40f3a-6095-49db-8e66-2754da921e30
14:46:53 <sayan> wrong url?
14:46:58 <abompard> mizmo: according to imgur, "I've taken a wrong turn"
14:47:06 <mizmo> sec
14:47:16 <mizmo> try this :) http://imgur.com/a/eNIzH
14:47:17 <mizmo> sorry about that
14:47:32 <mizmo> i guess they dont like direct links anymore
14:47:37 <abompard> mizmo: that's a F25 wallpaper idea
14:47:52 <pingou> http://i.imgur.com/u0Cyz3K.png ?
14:47:59 <abompard> oh
14:48:12 <abompard> mizmo: OK it is the mockup :)
14:48:56 <mizmo> abompard: does that make sense? this one only shows one reply below, but iwas thinking 2-3. there's 48 total, and clicking on the '48 comments / ' could take you to the hyperkitty thread page
14:48:57 <abompard> mizmo: OK I'll see what I can do :)
14:49:06 <mizmo> \o/
14:49:42 <abompard> mizmo: and "hide summary" collapses the whole thing into just "tatica made a blog post" ?
14:49:59 <abompard> (except it would be a mailing-list post)
14:50:12 <mizmo> anything else we need to cove today?
14:50:27 <sayan> mizmo: nope
14:51:32 <sayan> Nothing more to add, so moving over to open floor
14:52:04 <sayan> abompard: or do we show a small excerpt also ?
14:52:24 <mizmo> abompard: i have a little spec that covers that, lemme pull it up
14:54:22 <mizmo> https://pagure.io/fedora-hubs/issue/7#comment-535
14:54:54 <abompard> mizmo: ah, nice, thanks
14:54:59 <mizmo> trying to find an example of the summary state for a hyperkitty post
14:56:06 <mizmo> abompard: well in the interest of time :) yeh the summary version would just have the post, not any replies, and it'd be a ellipsized version of the post, maybe the first 3-5 lines
14:56:36 <abompard> mizmo: okay
14:57:11 <sayan> #topic Open Floor
14:57:23 <sayan> Anything to discuss for open floor?
14:57:46 <sayan> Ending the meeting in
14:57:48 <sayan> 3.
14:57:51 <sayan> 2.
14:57:55 <sayan> 1.
14:57:59 <sayan> #endmeeting