13:03:34 <sayan> #startmeeting hubs-devel
13:03:34 <zodbot> Meeting started Tue Dec 12 13:03:34 2017 UTC.  The chair is sayan. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:03:34 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
13:03:34 <zodbot> The meeting name has been set to 'hubs-devel'
13:03:42 <sayan> #topic Roll Call
13:04:04 <fm-hubs> pagure.pull-request.new -- ryanlerch opened pull request #492 on fedora-hubs: get basic allgroups page working https://pagure.io/fedora-hubs/pull-request/492
13:04:07 <sayan> .hello sayanchowdhury
13:04:08 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
13:04:17 <mizmo> .hello duffy
13:04:17 <ryanlerch> .helo ryanlerch
13:04:18 <zodbot> mizmo: duffy 'Máirín Duffy' <fedora@linuxgrrl.com>
13:04:34 <ryanlerch> .hello ryanlerch
13:04:35 <zodbot> ryanlerch: ryanlerch 'Ryan Lerch' <rlerch@redhat.com>
13:05:45 <sayan> #chair ryanlerch mizmo abompard[m]
13:05:45 <zodbot> Current chairs: abompard[m] mizmo ryanlerch sayan
13:05:54 <sayan> shaily: ping, meeting time
13:06:06 <shaily> .hello shaily
13:06:07 <zodbot> shaily: shaily 'None' <shaily15297@yahoo.com>
13:06:13 <abompard> .hello2
13:06:16 <zodbot> abompard: abompard 'Aurelien Bompard' <aurelien@bompard.org>
13:06:22 <sayan> #chair shaily abompard
13:06:22 <zodbot> Current chairs: abompard abompard[m] mizmo ryanlerch sayan shaily
13:07:22 <fm-hubs> pagure.pull-request.comment.added -- ryanlerch commented on PR #492 on fedora-hubs https://pagure.io/fedora-hubs/pull-request/492#comment-41457
13:07:22 <fm-hubs> pagure.pull-request.closed -- ryanlerch closed (without merging) pull request #492 on fedora-hubs https://pagure.io/fedora-hubs/pull-request/492
13:08:46 <sayan> #topic MVP Issues
13:09:10 <sayan> #topic The user management for a hub is currently not linked to FAS https://pagure.io/fedora-hubs/issue/389
13:09:53 <abompard> I started working on this
13:09:56 <sayan> abompard: ^^
13:10:01 <sayan> abompard: ok, go ahead
13:10:55 <abompard> Basically, we thought the work on the refactoring of the hubs config system (#487) has higher priority, so I'll get back to it when its done
13:12:03 <sayan> okay
13:12:08 <abompard> the reason is that we need something to be implemented in Ipsilon
13:12:10 <abompard> called CAIAPI
13:12:21 <abompard> and puiterwijk is working on that, but it's not quite ready yet
13:12:46 <abompard> so instead of working to call the FAS API and deprecating this in a couple weeks/month, it's better to work on something else
13:13:00 <ryanlerch> abompard: awesome!
13:13:21 <sayan> abompard: cool
13:13:27 <sayan> #link https://pagure.io/CAIAPI
13:13:40 <ryanlerch> there is plenty of cleaningup to do after the config stuff is done too -- shich i can help out with :)
13:14:05 <ryanlerch> i.e. more sub-tasks rely on the config stuff :)
13:14:17 <abompard> yeah, it's pretty low in our dependency tree
13:14:53 <sayan> #link disable "preview" status for hubs for MVP https://pagure.io/fedora-hubs/issue/478
13:14:57 <sayan> oops
13:15:05 <sayan> #topic disable "preview" status for hubs for MVP https://pagure.io/fedora-hubs/issue/478
13:15:47 <sayan> ryanlerch: ^^
13:16:43 <ryanlerch> i decided to leave this one for the time being, while abompard was messing with the config stuff
13:16:51 <abompard> makes sense.
13:17:24 <sayan> right
13:17:59 <sayan> ryanlerch: can you comment the ticket with the update?
13:18:55 <fm-hubs> pagure.pull-request.new -- ryanlerch opened pull request #493 on fedora-hubs: get basic allgroups page working https://pagure.io/fedora-hubs/pull-request/493
13:19:24 <ryanlerch> sayan: sure
13:20:17 <sayan> thanks
13:21:10 <sayan> #topic Hub Bio & Rules / Contact always at top of the page https://pagure.io/fedora-hubs/issue/462
13:21:43 <abompard> I plan on doing this, but after the new hub config system lands.
13:21:59 <sayan> this also should we worked after the config
13:21:59 <abompard> because info from the contact & rules widgets must be centralized in the hub config
13:22:09 <sayan> abompard: yep
13:22:58 <sayan> #topic Halp widget: do some testing https://pagure.io/fedora-hubs/issue/437
13:23:05 <sayan> abompard: this one ^^
13:23:13 <abompard> ah, yeah
13:23:31 <abompard> I need to do the styling changes suggested by mizmo
13:23:45 <abompard> but the testing itself is OK
13:24:34 <mizmo> abompard: if the code is available i could do the css changes
13:24:50 <mizmo> is a PR to a user fork possible in pagure? as i recall it used to not be?
13:25:21 <abompard> mizmo: the code is in the main repo, I believe
13:25:26 <mizmo> ryanlerch: what do you think about the color scheme i worked out in that ticket? does it make sense?
13:25:41 <sayan> #link https://pagure.io/fedora-hubs/issue/437#comment-481988
13:25:57 <mizmo> abompard: let me make sure i can find it :)
13:26:02 <ryanlerch> mizmo: yeah +1 from me
13:26:04 <sayan> looks good to me
13:26:21 <ryanlerch> i have helper classes for bg-fedora-blue etc
13:26:31 <ryanlerch> and color-fedora-blue
13:26:43 <ryanlerch> in the hubs css at the moment
13:26:56 * ryanlerch has to move that to fedora-bootstrap
13:27:08 <abompard> mizmo: hubs/static/client/app/widgets/halp/halp.css
13:27:09 <mizmo> ryanlerch: this one is more, a filter toggle than a button, i think i looked at those and wasn't sure they made sense given the toggle notion?
13:27:31 <mizmo> ah thanks for the halp abompard i was looking in /hubs/widgets
13:27:38 <mizmo> i will work on this now :)
13:27:43 <mizmo> and do a PR
13:28:22 <mizmo> ryanlerch: if it makes sense maybe we should make a toggle class in fedora-bottstrap
13:28:35 <abompard> mizmo: cool, thanks!
13:31:05 <mizmo> any other tickets?
13:31:11 <fm-hubs> pagure.issue.comment.added -- sayanchowdhury commented on ticket fedora-hubs#437: "Halp widget: do some testing" https://pagure.io/fedora-hubs/issue/437#comment-484202
13:31:23 <fm-hubs> pagure.issue.comment.edited -- sayanchowdhury edited a comment on ticket fedora-hubs#437: "Halp widget: do some testing" https://pagure.io
13:31:27 <mizmo> are we using the pagure milestone feature?
13:31:46 <sayan> mizmo: yes
13:31:48 <sayan> mizmo: https://pagure.io/fedora-hubs/roadmap?status=Open&no_stones=&milestone=Production
13:31:53 <ryanlerch> yeah -- there seems to be some sold stuff in therer though
13:32:02 <ryanlerch> milestones for flock
13:32:15 <fm-hubs> pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#437: "Halp widget: do some testing" https://pagure.io/fedora-hubs/issue/437#comment-484203
13:32:22 * shaily kind of lost track of the conversation due to network disconnection
13:32:27 * shaily would want to discuss search whenever there's time
13:33:13 <sayan> #topic Badges widget: implement categories https://pagure.io/fedora-hubs/issue/435
13:34:06 <sayan> No update here, closing on with the fedimg release in last week
13:34:17 <fm-hubs> pagure.issue.comment.added -- ryanlerch commented on ticket fedora-hubs#432: "Meetings widget: "Request a new meeting" button doesn't work" https://pagure.io/fedora-hubs/issue/432#comment-484204
13:35:42 <fm-hubs> pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#432: "Meetings widget: "Request a new meeting" button doesn't work" https://pagure.io/fedora-hubs/issue/432#comment-484205
13:36:23 <fm-hubs> pagure.issue.edit -- ryanlerch edited the close_status and status fields of ticket fedora-hubs#469 https://pagure.io/fedora-hubs/issue/469
13:36:50 <fm-hubs> pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#33: "Request New Meeting Feature" https://pagure.io/fedora-hubs/issue/33#comment-484207
13:37:08 <sayan> #topic People Widget https://pagure.io/fedora-hubs/issue/434
13:37:12 <sayan> ryanlerch: ^^
13:38:42 <ryanlerch> sayan: this one is on my list to get done this week
13:39:01 <ryanlerch> this is a team-hub only widget really
13:39:51 <sayan> okay
13:40:12 <ryanlerch> a PR will be filed on this one by the end of tomorrow
13:40:47 <sayan> ryanlerch: cool!
13:41:07 <sayan> #topic: The "All groups" page is a placeholder https://pagure.io/fedora-hubs/issue/387
13:41:25 <ryanlerch> sayan: just filded the PR for this one
13:41:48 <sayan> Oka
13:41:55 <sayan> #link https://pagure.io/fedora-hubs/pull-request/493
13:42:08 <ryanlerch> it'sbasic, but does the job for MVP
13:42:38 <ryanlerch> we can loop back and make it more reacty in the future -- i.e. post MVP
13:43:36 <sayan> okay moving to open floor then
13:43:40 <sayan> #topic Open Floor
13:44:07 <sayan> shaily: the floor is yours :)
13:44:23 <shaily> sayan: thanks!
13:45:01 <shaily> a status update first, about the ticket i had taken up last week
13:45:34 <shaily> about the userissues widget, apparently the PR that was merged in pagure doesn't cut it
13:45:42 <shaily> needs some changes to the core Issues model
13:45:45 <shaily> so pingou is working on that
13:45:48 <shaily> i'll continue once that's done
13:46:01 <shaily> about search now
13:46:16 <shaily> i filed #491 a couple of days back
13:46:22 <shaily> https://pagure.io/fedora-hubs/issue/491
13:46:45 <shaily> so we have data stored in two forms right
13:46:50 <shaily> in the sql db and in the cache
13:47:07 <shaily> the sql data is pretty straightforward to index, since every model it has a well defined schema
13:47:26 <shaily> not so much for the cached data, since its the widget output that we're caching
13:47:36 <shaily> which isn't uniform
13:47:51 <shaily> any way we could fetch that while executing search queries / updating the search engine's index?
13:48:17 <shaily> i had suggested widget config since we're storing that in the sql db and that's what is ultimately used to generate widget output
13:48:28 <shaily> but abompard response on the ticket makes sense there
13:48:36 <shaily> how should i proceed further
13:49:36 <shaily> my timeline for the next couple of weeks involves testing different search engine libraries and ultimately presenting a comparison here for the final choice decision
13:49:52 <shaily> but at some point i need to bring in what data we'll be indexing into the search engine
13:50:46 <shaily> i don't yet understand how we can index widget output
13:51:01 <abompard> shaily: we'll think about that
13:51:46 <shaily> so for the time being, should i continue comparing search engine libraries on different sample data sets (not hubs specific data)?
13:52:09 <abompard> yeah, I guess so
13:52:21 <abompard> the hubs data isn't really extraordinary
13:52:51 <shaily> abompard: okay, cool. thanks!
13:52:53 <abompard> BTW shaily, remember to blog during the outreachy internship. It's a requirement.
13:53:11 <shaily> abompard: sure, i'll write one this week! :)
13:53:16 <abompard> cool!
13:54:25 <shaily> okay, that's all from my end
13:54:31 <mizmo> i have an update from the cornell student team working on hubs if you are interested
13:54:51 <mizmo> they finished their project, they made both a 10 minute video presentation of their findings as well as a written report
13:55:09 <mizmo> as part of our initial agreement their work is licensed open source / creative commons
13:55:25 <mizmo> they did multiple rounds of user research with multiple fedora contributors -
13:55:43 <mizmo> they focused on user needs for the commops team and designed a set of widgets to support comm ops and im pretty excited about them
13:56:26 <mizmo> not MVP stuff at this point, but i'll file ui spec tickets for each widget they designed and upload their assets so we have them. i'll post a link to their presentation video to hubs-devel too so you can watch
13:56:43 <ryanlerch> mizmo: awesome! can't wait
13:57:11 <mizmo> as a quick overview - we may want to have a convo about how to implement,
13:57:27 <mizmo> the main thread across all the iwdgets they worked on focus on pairing up new incoming contributors with mentees
13:58:21 <mizmo> so each team has an incoming mentee queue, their idea is that when someone clicks to 'join a hub' they could fill out a form (something like why they want to join, with a checkmark to request a mentor)
13:58:28 <sayan> mizmo: what is assets here? -> "upload their assets"
13:58:32 <mizmo> then the newbie gets put in a 'needs mentorship queue' specific to that team
13:58:42 <mizmo> sayan: assets => their mockups :)
13:58:49 <mizmo> and other design artifacts like their writeups
13:58:52 <sayan> mizmo: okay
13:59:54 <mizmo> one of the widgets is for team hubs, that displays a tabbed view of mentees requesting mentorship, and mentees who have mentorship showing their pairs and their status. you can use the widget as a team member to accept a mentee, and it has a system to eventually 'graduate' the mentee, or send reminders - after so many reminders and no contact they get expired out of the mentee queue
14:00:30 <sayan> sounds cool!
14:01:27 <mizmo> there is also a widget specific for the commops hub that shows a list of all of the team hubs participating in the mentee program, and per team it displays how many mentees and mentors are active, what their 'graduation' rate is per team and the mentorship cancellation rate, plus the average wait time for an onboarding newcomer to be paired up with a mentee
14:01:31 <mizmo> and a widget specific to the mentors, to show a list of their mentees (max 5) to allow them to track the mentee's recent activities to better be able to follow / provide guidance
14:02:00 <mizmo> anyway, i thought i'd give that update. i was really blown away by their preso, i can see how these designs would really positively impact fedora if want can implement them and get fedorans using them
14:02:38 <ryanlerch> mizmo: sounds interests=ing!
14:02:46 <sayan> yeah!
14:02:51 <ryanlerch> gah, be shouldnt nap before meeitngs
14:02:57 <sayan> btw, we are over time
14:03:01 <ryanlerch> typing bad
14:03:17 <sayan> does anybody else have anything for the open floor?
14:03:40 <sayan> ryanlerch: that sounded like yoda speaking :)
14:04:04 <abompard> mizmo: It sounds great!!
14:04:05 <ryanlerch> sayan: nothing that cant be said in a ticket or PR :D
14:04:21 <sayan> ending the meeting in 3.
14:04:23 <sayan> 2.
14:04:23 <abompard> same here
14:04:25 <sayan> 1.
14:04:32 <sayan> #endmeeting