14:02:03 <stickster> #startmeeting Fedora Hubs
14:02:03 <zodbot> Meeting started Tue Nov  1 14:02:03 2016 UTC.  The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:02:03 <zodbot> The meeting name has been set to 'fedora_hubs'
14:02:09 <stickster> #meetingname fedora-hubs
14:02:09 <zodbot> The meeting name has been set to 'fedora-hubs'
14:02:14 <stickster> #topic Roll call
14:02:19 <stickster> .hello pfrields
14:02:19 <mizmo> .hello duffy
14:02:20 <zodbot> stickster: pfrields 'Paul W. Frields' <stickster@gmail.com>
14:02:23 <stickster> #chair mizmo
14:02:23 <zodbot> Current chairs: mizmo stickster
14:02:23 <zodbot> mizmo: duffy 'Máirín Duffy' <fedora@linuxgrrl.com>
14:02:59 <stickster> I hope I started this at the right time. I know there was a time change in Europe already, so it means an hour earlier their time.
14:03:11 * stickster gives a minute for others to show up
14:04:28 <stickster> #info --- Agenda link ---
14:04:33 <stickster> #link https://pagure.io/fedora-hubs/issues?status=Open&tags=milestone
14:06:33 <stickster> OK, let's go ahead... I'm going to start with oldest issues first (bottom of the list) to give abompard time to get here ;-)
14:06:55 <stickster> #topic IRC Widget
14:06:58 <stickster> #link https://pagure.io/fedora-hubs/issue/2
14:07:43 <stickster> sayan added a status note today at my request which links this to the waartaa Trello board where he and rtnpro are tracking their work
14:08:02 <stickster> #info waartaa trello board tracks this and related issues
14:08:07 <stickster> #link https://trello.com/b/RetFEvn2/waartaa
14:09:07 <stickster> However, the ircb "user story" here doesn't seem to be very specific
14:09:50 <stickster> sayan isn't here to speak to the IRC widget progress, so we may have to skip this for now.
14:10:21 <mizmo> seems reasonable
14:10:21 <stickster> #action stickster speak to sayan about making the Trello board cards (including USes and backlog tasks) more specific so people can tell what's happening
14:10:55 <stickster> Not that we need to get *this* detailed, but compare to https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/26
14:11:35 <stickster> #info skipping issues #2, #27, #32 for now
14:11:45 <stickster> #topic Manage Bookmarks Widget
14:11:51 <stickster> #link https://pagure.io/fedora-hubs/issue/11
14:12:14 <stickster> devyani7: are you around?
14:13:40 <stickster> *sigh
14:13:56 <stickster> #action stickster email devyani7 & cc the hubs-devel list to get an update on this ticket
14:14:17 <stickster> I'm just randomly guessing at where this work is happening, but https://pagure.io/fork/devyani7/fedora-hubs/commits/bookmark seems pretty stale
14:14:44 <stickster> there may be work in another branch, or maybe just on devyani7 local machine and not pushed yet
14:14:52 <stickster> mizmo: anything you know about this from previous meetings?
14:15:20 <mizmo> stickster: no :( im not sure if devyani7_ has been around for the last meeting i was at
14:15:25 <stickster> OK
14:15:28 <stickster> let's move on then :-)
14:16:47 <stickster> #topic Badges widget for projects/teams
14:16:51 <stickster> #link https://pagure.io/fedora-hubs/issue/17
14:17:35 <stickster> sayan told me this morning he had been doing some work on the path implementation; however, it's not noted in the ticket yet and really should be
14:18:18 <mizmo> ive been working on the style/layout of the other badges widget, haven't done this one yet
14:19:24 <stickster> I think his stuff was backend bits, IIRC... so is this in need of a further mockup, or something else?
14:19:57 <mizmo> so for me to do the styling i basically need data getting output to the page so i can format and style it in the template
14:20:12 <stickster> mizmo: Ah, OK -- that might be here then: https://pagure.io/fork/sayanchowdhury/fedora-hubs/commits/badges-user-profile
14:20:28 <stickster> sayan provided some temporary data so the output would show up
14:21:26 <stickster> mizmo: are you able to add sayan's fork as a remote and pull those commits into a branch you can work on?
14:21:51 <mizmo> stickster: yeh that is not for this ticket though that's for a different one i've been wroking on - 85
14:22:07 <stickster> Oh OK -- so that doesn't help for this #17?
14:22:26 <mizmo> no, and AFAIK the temp data is for 85 not 17
14:22:34 <stickster> ah ok
14:22:38 <mizmo> but if there's temp data for 17 it'd be good to know, that means i could start work on it too
14:23:26 <stickster> mizmo: Could you post that in a comment on issue #17 and tag sayan on it?
14:23:35 <mizmo> ok
14:23:54 <stickster> #action mizmo update #17 ticket with request for data so she can work on that ticket as she has with #85
14:23:59 <stickster> coolio
14:24:25 <stickster> mizmo: Anything else we could cover, or ask about, with regard to this issue?
14:24:31 <fm-hubs> pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#17: "Badges Widget for Project/Teams (with Path Support)" https://pagure.io/fedora-hubs/issue/17#comment-39285
14:24:50 <mizmo> stickster: i don't think so!
14:24:54 <stickster> Okey dokey
14:25:10 <stickster> #topic Release cycle status widget
14:25:10 <stickster> #link https://pagure.io/fedora-hubs/issue/63
14:26:15 <fm-hubs> pagure.issue.comment.added -- pfrields commented on ticket fedora-hubs#63: "Current status in release cycle widget" https://pagure.io/fedora-hubs/issue/63#comment-39286
14:26:22 <stickster> So I just added a request for info here
14:26:32 <mizmo> good idea!
14:26:41 <stickster> sayan told me vivek_ was discussing with threebean how to integrate this properly
14:26:48 <mizmo> vivek__: ^^ you don't have any updates on this one do you? are you still working on the release cycle widget?
14:27:00 <stickster> whether with PDC or (because PDC may not be ready) something else
14:27:25 <stickster> so I was just asking in the ticket to try to make that discussion more transparent for the team & onlookers
14:27:42 <stickster> But this is in progress for sure
14:27:48 <mizmo> totally, was just thinking we could update ticket now if vivek__ was around
14:27:56 <stickster> absosmurfly
14:29:42 <stickster> OK, hopefully he'll see the ticket ping then, and we'll hear back shortly
14:30:24 <stickster> mizmo: anything else we can add here for clarity?
14:30:52 <mizmo> nope
14:31:03 <mizmo> ticket comment looks good
14:31:04 <stickster> #action vivek_ to update ticket with progress/results of discussion with threebean
14:31:19 <stickster> #topic Badges widget with user profiles
14:31:20 <stickster> #link https://pagure.io/fedora-hubs/issue/85
14:31:30 <stickster> \o/ finally a ticket someone's here to cover :-D
14:32:21 <mizmo> lol
14:32:30 <mizmo> yeh so sayan put in some dummy data for that so i could polish the widget
14:32:39 <stickster> deja vu! :-D
14:32:53 <mizmo> but unfortunately even though i made a lot of progress (and i still have the CSS) the htmlt emplate i did is gone, i can't figure out why, maybe some kind of git thing wiped it out :-/
14:32:58 <mizmo> so im going to have to redo it this morning
14:33:03 <stickster> :-(
14:33:06 <mizmo> OH
14:33:07 <mizmo> OH
14:33:14 <mizmo> halfline just figured out what happened
14:33:17 <mizmo> lol
14:33:19 <stickster> hooray
14:33:31 <mizmo> i'm an idiot. i copy / pasta'ed the template html into fedora-bootstrap and styled it there
14:33:35 <mizmo> so it's in a different repo
14:33:36 <stickster> I was about to start singing "Poor Thing" since I've been obsessed with Sondheim's Sweeney Todd lately
14:33:41 <mizmo> wow maybe praying to St Benedict really works
14:34:06 <stickster> lol... patron saint of high-demand designers?
14:34:36 <mizmo> protection from evil!
14:34:59 <stickster> nice
14:35:35 <mizmo> well good news on this ticket's front then lol
14:35:49 <stickster> #info mizmo has made a lot of progress on the template/CSS so this is well on its way :-)
14:35:50 <mizmo> the way i've been doing it is so the extra styling stuff can be used 'upstream' in fedora-bootstrap (hopefully anyway)
14:36:48 <stickster> nice, again :-)
14:37:00 <stickster> will some of that be able to carry down to other widgets, then, too?
14:37:51 <mizmo> yep! that's the goal!
14:37:56 <stickster> coolio!
14:38:08 <stickster> mizmo: anything else you want to cover on this ticket?
14:38:13 <mizmo> nope!
14:38:18 <stickster> okey dokey then...
14:38:21 <stickster> #topic Halp widget
14:38:24 <stickster> #link https://pagure.io/fedora-hubs/issue/98
14:38:31 <stickster> abompard: are you around to talk about this one?
14:39:28 <mizmo> i think today is a french holiday
14:40:14 <fm-hubs> pagure.issue.comment.added -- pfrields commented on ticket fedora-hubs#98: "#halp/help widget: Default in the CommOps Hub" https://pagure.io/fedora-hubs/issue/98#comment-39289
14:40:19 <stickster> Oh right! I completely forgot!
14:41:07 <stickster> Well, the good news (from the ticket) is that abompard has been making some progress recently (a couple weeks ago), but this past week I know he ran into an issue
14:41:54 <stickster> the primary Mailman maintainer happened to be able to spend some time on reviewing and merging a lot of PRs, so abompard made himself available last week to work with him on various PRs'
14:42:15 <stickster> but he said he'd be back to working on the halp widget this week
14:42:29 <mizmo> oh okay cool
14:42:47 <mizmo> he'd emailed me about the UX aspect yesterday so he must be working on it actively now
14:43:00 <stickster> #info abompard was on a detour last week to work with upstream on merging a large number of Mailman PRs, but is back to working on halp widget this week
14:43:03 <stickster> cool
14:43:31 <stickster> I dropped an idea in the ticket just now because I read abompard's question about handling random meeting channels
14:43:46 <stickster> however, I have no idea whether it adds more complexity, which is not my intention :-)
14:44:20 <stickster> it seems less complex to me than trying to tie in fedocal stuff, but I'm really not a good person to estimate that effort :-\
14:44:58 <mizmo> we'd talked about it in the meting last week
14:45:22 <stickster> Ah OK, I'm just late then
14:45:32 <stickster> mizmo: did anything get decided there?
14:45:46 <mizmo> your suggestion i think is on the right track though
14:45:49 <mizmo> well here'es the thing
14:46:06 <mizmo> a number of hubs features i think are going to require some kind of lookup table or something to associate team hubs with different things
14:46:14 <mizmo> like their irc channel or their meetbot meeting label
14:46:19 <stickster> *nod
14:46:33 <mizmo> i think for this one meetbot has the meeting topic which is generally the team name?
14:46:38 <mizmo> (not the convo topic)
14:46:53 <mizmo> the only thing tricky there is for example, design team sometimes we do design-team sometimes we do fedora-design
14:47:00 <mizmo> meetbot doesn't handle that too well
14:47:00 <stickster> right right
14:47:16 <mizmo> if meetbot had a way to merge them / make one an alias of another
14:47:25 <stickster> yeah, the diff between #startmeeting <topic> and #meetingname <override>
14:47:26 * mizmo not sure
14:47:51 <mizmo> oh i didn't know about #meetingname <override> ?
14:48:05 <mizmo> i use #startmeeting <topic> because it won't work if you dont give a topic
14:48:29 <stickster> we use that for the Magazine, where we do '#startmeeting Magazine editorial board' but then '#meetingname magazine'
14:48:57 <stickster> so the meetings get filed as 'magazine-<blahblah_timestamp>'
14:49:03 <mizmo> is #meetingname a different field that gets stored?
14:49:29 <mizmo> it seems like maybe we should make some meetbot mods or something for this to be a clean thing rather than hacky
14:49:34 <stickster> only if someone forgets #meetingname, the meeting logs/minutes get filed as "magazine_editorial_board-<blahblah_timestamp>.{html,txt}"
14:49:56 <mizmo> thats a bummer, you shouldnt have to remember
14:50:14 <mizmo> see on design team we cant even remember / dont know if it's design-team or fedora-design
14:50:21 <mizmo> and its caused a mess
14:50:34 <stickster> yeah, so you get some logs in one label and some in another, you mean?
14:50:51 <stickster> and trying to find which one is correct for "last week" for instance is harder
14:51:19 <mizmo> exactly
14:51:38 <mizmo> hubs kind of has this idea of a namespace for teams
14:51:42 <stickster> it would be cool if meetbot gave you suggestions for teams it knows about, like registrations
14:51:54 <stickster> and if you choose one, it automatically hooks up one or more hub(s) too
14:52:20 <mizmo> yes! that would be ideal
14:52:55 <mizmo> it would also be good for the alias thing so we can reconcile the mess of the design team stuff
14:52:59 <mizmo> maybe thatd be a feature request for meetbot
14:53:00 * mizmo can file
14:53:01 <stickster> like if you do '#prepmeeting' it says, 'Hi, here are meetings I know about you could use for #startmeeting: magazine, design-team, hubs, ...'
14:53:28 <mizmo> #action mizmo to file RFEs for meetbot - meeting name suggestion list, and reconcile different meeting names / aliases
14:54:12 <stickster> mizmo: Maybe this is too much, but it would also be cool if you further did "#prepmeeting design-team" then meetbot gave you some canned text, like an agenda link, and maybe some details like which hub(s) are automatically hooked up
14:55:00 <stickster> not sure where to pull any of that from, but hopefully any team would be able to help maintain it so it doesn't overburden anyone specifically
14:55:12 <mizmo> oh thatd be really nice if you could set the link to the agenda in meetbot before the meeting and it'd sync to fedocal etc
14:55:53 <mizmo> and it might also be nice to have the agenda in the meeting minutes with the minutes underneath and you can see if you actually covered the agenda fully or not
14:56:39 <stickster> well, the agenda could be anything -- it might be a link to tickets like this meeting, or it might be a wiki page, or it might be an email...
14:57:03 <stickster> so we might have to avoid getting too "smart" about what we do with that link
14:57:14 <mizmo> it could just be a link at the top to those resources
14:57:18 <mizmo> in the meeting minutes
14:57:22 <mizmo> in a metadata section at the top
14:57:28 <stickster> yeah, more like it's text or a link you can follow -- right
14:57:53 * stickster misunderstood and thought you were saying we'd parse a link into something else and then paste that
14:58:02 <stickster> which seems like exponentially more work
14:58:04 <mizmo> if it's called out as part of metadata instead of buried in the log (which may or may not bubble it up into the meeting minutes summary) it'll be more visible
14:58:10 <stickster> agreed!
14:58:18 <mizmo> oh no you didn't misunderstand, i modified the idea to make more sense :)
14:58:24 <stickster> \o/
14:58:43 <stickster> I like this idea... question is whether we have someone who wants to work on meetbot to make it work :-)
14:59:11 <stickster> but it certainly seems to me that if we have a set of this metadata somewhere, it should be easy to include hub(s) in that collection too
14:59:19 <mizmo> #action mizmo to file RFE idea for meetbot / agenda link metadata
14:59:49 <stickster> so for example if our program manager runs a release readiness meeting, it automatically will send #halp not just to commops but to any hub registered for that meeting
15:00:17 <mizmo> well, im not sure about that -
15:00:39 <mizmo> so the idea with the halp feature is that all halps get bubbled up to everybody, but they get categorized by the meeting they were associated with
15:00:47 <stickster> OOOOHHHHH
15:01:04 <stickster> and it's up to the hub whether to show things in that category?
15:01:07 <mizmo> so if they're associated with multiple hubs, it becomes harder to categorize them
15:01:10 <stickster> or it doesn't even matter
15:01:19 <stickster> oh right, or they might even double up in that case
15:01:22 <stickster> which would be annoying
15:01:42 <mizmo> right, so for the commops hub, they'd show all categories because they have a more general view, but if we put the halp widget on design team's hub, we'd filter it to show design halps
15:01:58 <stickster> *nod
15:02:03 <stickster> cool, I get it now.
15:02:15 <mizmo> well
15:02:21 <stickster> still, the RFE above is definitely a neat one
15:02:22 <mizmo> no it makes sense
15:02:39 <mizmo> i was going to say for cross functional projects it'd make sense to associate multiple hubs to a meeting but
15:02:41 <mizmo> i think cross functional projects get their own hub
15:03:00 <mizmo> so you just associate itw ith the project hub
15:03:11 <stickster> yeah, and if that's the case we could assume they'd have a #meetingname or topic
15:03:18 <stickster> and handle the same way, so disco
15:03:31 <mizmo> yeh exactly
15:03:37 * stickster notes we're overtime here, so maybe we should close out
15:03:55 * stickster has another meeting coming up to tend to, anyhow
15:04:00 <mizmo> sounds good, thank you for running the meeting!
15:04:02 <stickster> good news is we finished *our* agenda :-)
15:04:09 <mizmo> lol
15:04:11 <stickster> thanks for the awesome brainstorming on meetbot
15:04:18 <stickster> I'll send out notes of course
15:04:28 <mizmo> same to you! thanks!
15:04:39 * mizmo also overjoyed at the discovery of hours of lost work
15:05:04 <stickster> #info rounding out this issue topic... abompard is still on the case, we have some interesting ideas for IRC->#halp->hubs flow
15:05:13 * stickster will end the meeting in 10 sec
15:05:23 <stickster> 3
15:05:24 <stickster> 2
15:05:25 <stickster> 1
15:05:27 <stickster> #endmeeting