14:00:59 #startmeeting fedora-hubs 14:00:59 Meeting started Wed Jul 13 14:00:59 2016 UTC. The chair is pingou. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:59 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:59 The meeting name has been set to 'fedora-hubs' 14:01:00 radhikak here but will be in another meeting 14:01:38 radhikak: thanks for letting us know, feel free to ping after the meeting if you have any questions or comments 14:02:06 a small announcement while mizmo arrives 14:02:08 .hello pfrields 14:02:09 stickster: pfrields 'Paul W. Frields' 14:02:18 we have a room at flock for a fedora-hubs hackfest: https://flock2016.sched.org/event/7ig9/fedora-hubs-meetuphackfest 14:02:24 \o/ 14:02:37 \o/ 14:02:46 it's scheduled at 13:30 CEST making this 11:30 UTC and 07:30 eastern time 14:03:01 Sure pingou 14:03:28 and the big question is: what will we have to show then? :) 14:04:29 So just as a reminder... the overall goal was to be able to demo the use of at least *a* hub 14:04:52 radhikak: stickster: do you know if mizmo is around? 14:05:20 pagure.pull-request.comment.added -- pingou commented on pull-request#213 of project "fedora-hubs" https://pagure.io/fedora-hubs/pull-request/213#comment-7156 14:05:24 pingou: Although mizmo's not in the office today, AFAIK she expected to be online in general 14:05:39 pagure.pull-request.comment.added -- pingou commented on pull-request#213 of project "fedora-hubs" https://pagure.io/fedora-hubs/pull-request/213#comment-7157 14:05:57 atelic: around? 14:06:03 pagure.pull-request.comment.added -- atelic commented on pull-request#213 of project "fedora-hubs" https://pagure.io/fedora-hubs/pull-request/213#comment-7158 14:06:09 stickster: ok so let's start and see if she joins :) 14:06:17 pingou: I'm here 14:06:27 o/ atelic 14:06:36 and o/ everyone else :-) 14:06:42 stickster: o/ 14:06:43 pagure.pull-request.comment.added -- pingou commented on pull-request#213 of project "fedora-hubs" https://pagure.io/fedora-hubs/pull-request/213#comment-7159 14:06:45 \o 14:06:51 stickster: \o 14:07:04 pagure.pull-request.comment.added -- atelic commented on pull-request#213 of project "fedora-hubs" https://pagure.io/fedora-hubs/pull-request/213#comment-7160 14:07:30 ok so we have a tag for tickets we want to solve for flock: https://pagure.io/fedora-hubs/issues?priority=1&tags=flock 14:07:42 here! sorry 14:07:45 o/ mizmo 14:07:54 stickster: mizmo \o 14:08:10 mizmo: hi :) 14:08:12 Oh, this is great pingou 14:08:24 stickster: all mizmo :) 14:08:34 mizmo++ 14:08:34 stickster: Karma for duffy changed to 10 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:08:39 but it is quite a list... 14:08:42 yes 14:08:45 thus this meeting 14:08:58 pagure.issue.comment.added -- skrzepto commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3586 14:09:11 I would like us to realistically estimate what can and what won't be achieved in 3 weeks= 14:09:14 Right, let's see whether there are some things that could be trimmed while still allowing a demo 14:09:30 high-level we were looking at having 3 team hubs mostly functional 14:09:40 what we could do is trim it back to focusing on only one or 2 teams 14:09:51 the 3 teams we've been working on are design, commops, and translations 14:10:04 so translations is depending on zanata, right? 14:10:17 which makes me realized I never replied to your email :( 14:10:20 i think translations might be the smartest to drop bc we're still waiting on new api calls from the zanata team, and i'm not sure if they got the go ahead from their managementt o do them yet 14:10:39 Oh crap, pingou, I think I'm the same -- I got it while at Summit and couldn't complete at the time 14:12:18 mizmo: I dropped that ball, sorry. If they're expecting a statement for me on priority for Hubs, that's my fault. OTOH, it's not clear to me how to articulate how this matches up with customer impact (since the responsible team is a customer-focused team in RH) 14:12:19 mizmo: I think putting translation as the 3rd hub to consider is good 14:12:31 pagure.issue.comment.added -- skrzepto commented on ticket fedora-hubs#172: "Write down the SSE server serving fedmsg messages to the hubs" https://pagure.io/fedora-hubs/issue/172#comment-3587 14:12:47 i got the feeling getting it done in time for flock was probably going to be hard for them anyway stickster - but we should still move forward just maybe target post flock at this point 14:12:54 mizmo: Agreed 14:13:11 not trying to let myself off the hook, but the time constraint is really the thing we need to focus on here 14:13:24 clearly 14:13:39 my experience with that dev team is it will probably take some time to work any feature through their process and priorities anyway, and 3 weeks (or even 2 months) would have been challenging to say the least 14:13:42 pagure.issue.assigned.added -- pingou assigned ticket fedora-hubs#172 to skrzepto https://pagure.io/fedora-hubs/issue/172 14:13:52 stickster, yeh they have a 2 week sprint cycle kind of thing going on 14:14:02 *nod 14:14:04 okay so if we focus just on design and comm ops hubs 14:14:14 (should we take flock tag off l10n stuff?) 14:14:24 I would think so 14:14:34 it would help reduce that list 14:15:01 sayan: regarding badges, did you see: https://github.com/fedora-infra/tahrir-api/pull/37 ? 14:15:02 * mizmo takes tag off 14:15:36 pingou: I did see 14:15:47 pagure.issue.tag.removed -- duffy removed the flock tags from ticket fedora-hubs#167 https://pagure.io/fedora-hubs/issue/167 14:16:15 ok taking flock tag off zanata widget ticket too 14:16:30 pingou: it works on the naming of the badges, but I think we build to build relationship between a badge and series 14:16:34 mizmo: do these ticket have a l10n tag? 14:16:36 pagure.issue.tag.removed -- duffy removed the flock tags from ticket fedora-hubs#165 https://pagure.io/fedora-hubs/issue/165 14:16:41 I saw a couple other things that might be debatable... https://pagure.io/fedora-hubs/issue/170 (mobile compatibility/testing) -- yes, definitely a good thing, but vital for Flock demo? 14:16:43 pingou, they dont 14:16:52 stickster, nope not vital, will take tag off that too 14:16:55 pingou, (i can add it) 14:17:02 pingou: for a widget like this - https://pagure.io/fedora-hubs/issue/160 14:17:04 mizmo: might be a good idea :) 14:17:08 pagure.issue.tag.added -- duffy tagged ticket fedora-hubs#165: l10n https://pagure.io/fedora-hubs/issue/165 14:17:27 pagure.issue.tag.removed -- duffy removed the flock tags from ticket fedora-hubs#170 https://pagure.io/fedora-hubs/issue/170 14:17:47 sayan: yup 14:17:49 pagure.issue.tag.added -- duffy tagged ticket fedora-hubs#167: l10n https://pagure.io/fedora-hubs/issue/167 14:18:04 sayan: since you already have the irc widget, do you think you will have time to work on badges? 14:19:03 pingou: I am starting my work on badges, planning to build a minimalistic one 14:19:06 so if we focus on commops and design, i think it might be important to support trac, which i know sucks bc its legacy but those teams both use trac heavily 14:19:21 that ticket is here and is tagged flock: https://pagure.io/fedora-hubs/issue/174 14:19:26 pingou: maybe next week would be the best time to say with the progress 14:19:55 sayan: ok 14:20:06 btw, can I remove the flock tag from this issue - https://pagure.io/fedora-hubs/issue/160 14:20:19 mizmo: ^ 14:20:26 sayan, sure! go4it :) 14:20:33 would like to concetrate on this - https://pagure.io/fedora-hubs/issue/17 14:20:57 mizmo: I'm conflicted... I think you're right that it may be necessary. At the same time, I'm sad we are putting time into Trac, when ultimately I'd like to see it go away 14:20:58 pagure.issue.tag.removed -- sayanchowdhury removed the flock tags from ticket fedora-hubs#160 https://pagure.io/fedora-hubs/issue/160 14:21:15 sayan, so one thing with issue #17 - is that is only for personal profiles 14:21:19 160 is for team hubs 14:21:32 mizmo: yes 14:21:48 if we wanted to focus on delivering a good demo of team hubs, itd be better to implement 160 (even if it's using the tag implementation instead of tree) 14:21:48 mizmo: oh 14:21:58 i guess though, personal profiles are another type of hub we should focus on 14:22:09 mizmo: 160 is: my next badges, is that on the team hub? 14:22:24 oh oh 14:22:27 same question as pingou 14:22:31 pingou, sayan sorry i was confused youre right thats a profile one lol 14:22:33 carry on :) 14:22:40 there is a different ticket for team hub badge widget tho 14:22:45 it talks about the badges you can earn for a certain team 14:23:06 it's actually a pretty critical widget in terms of UX in that for new folks just joining a team, it suggests to them things they can do to get started 14:23:36 pagure.issue.comment.added -- pingou commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3588 14:23:45 mizmo: 17 is the hubs one 14:24:12 sayan, and i am completely backwards. i am so sorry! you're right, 17 is the right one 14:24:34 the badge missions in that mockup == badge paths 14:24:36 mizmo: at least you both agree on the priority :) 14:25:09 * mizmo hasnt had her coffee yet, clearly 14:25:37 * stickster sucks down more coffee 14:25:41 regarding trac, I wonder if we don't already have a basic one 14:27:02 pingou, oh? 14:27:10 * pingou checks 14:27:25 pagure.issue.comment.added -- skrzepto commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3589 14:27:49 mizmo: no inded, only pagure and github issues 14:27:58 mizmo: shouldn't be too hard to make a trac one based on these 14:27:59 wah wah 14:28:02 well 14:28:07 okay that's good news :) 14:28:12 * pingou takes the trac one 14:28:27 * mizmo grabs the design team mockup to see what other widgets are key on there 14:28:40 mizmo: do we still want to consolidate all the issues in one widget? 14:29:00 pingou, i think ultimately thats the better way to do it, but i dont think thats necessary for flock demo 14:29:10 pagure.issue.assigned.added -- pingou assigned ticket fedora-hubs#174 to pingou https://pagure.io/fedora-hubs/issue/174 14:29:22 mizmo: https://pagure.io/fedora-hubs/issue/33 I had a few questions about this one 14:29:35 mizmo roger (and better for me :-p) 14:29:47 pingou, sure whats up! 14:29:56 https://pagure.io/fedora-hubs/issue/33#comment-3528 14:30:30 pagure.issue.comment.added -- sayanchowdhury commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3590 14:31:02 pingou, ah good point! i think the gap would be easy to address tho, just generate an invite with a pointer to the meeting planning link that gets auto sent to the team mailing list 14:31:22 similar to how, for example, fedocal sends out automated meeting reminders to the team list 14:31:42 pagure.issue.comment.added -- pingou commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3591 14:32:17 mizmo: which means hubs grows code to send emails? 14:32:42 hm, ideally no 14:32:45 * stickster wonders whether we should be careful not to dive down into too many individual tickets here 14:32:46 and we need to associate a hub w/ a list 14:32:57 yeh thats one of those critical things right 14:32:58 as opposed to prioritizing the ones we have 14:33:11 bc how is the feed widget going to display design team messages on the design team hub if theresno association 14:33:33 mizmo: the feed widget is to be configured in fmn :) 14:33:36 stickster, would it make more sense totalk high level about things that should be inthe demo and then sort out the tickets to make sure they reflect that? (and create any missing ones) 14:33:40 well the content of the feed widget 14:33:52 pingou, so can fmn handle the associate between team<=>mailing list? 14:33:59 mizmo: yeah, I'm thinking 14:34:17 from a UX pov we were thinking that association would be done by the hub admin in the edit hub panel (which i know doesnt exist right now but the mockups do) 14:34:17 mizmo: we could tell in fmn to only account for mailing post coming from a dedicated list 14:34:36 so high level for the demo, this is the stuff i'd like us to show off - 14:34:41 log into hubs 14:34:49 click on 'design team' in the bookmarks bar 14:35:10 at the top of design team, see a welcome message (eg purple note at the top here http://blog.linuxgrrl.com/wp-content/uploads/2014/04/design-hub-idea_notes1.png ) 14:35:16 pagure.issue.comment.added -- skrzepto commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3592 14:35:16 dismiss welcome message 14:35:26 * devyani7 reads the convo on #185 14:35:28 scroll through feed widget. things id like us to be able to show in the feed widget: 14:35:34 - design-team@lists.fpo posts 14:35:41 - planet.fedoraproject.org/design blog posts 14:35:52 - design-team trac ticket updates 14:36:17 - design-team meeting reminders 14:36:28 - design team meeting minutes (if possible, lower priority) 14:36:32 for the right hand side of the screen 14:36:38 i'd like us to be able to show 14:36:49 - counts for members / subscribers / a button to join team 14:37:07 I think we need a 'design team hub' ticket with all this in 14:37:10 - list of community admins with link to community guidelines (should point to fedoraproject.org/wiki/Design for now) 14:37:24 - IRC / wartaa widget for #fedora-design 14:37:27 then we can check what is there and what is to be added 14:37:35 - ticket widget for fedora-design trac 14:37:42 - badges widget for design team badges 14:37:56 i can copy/pasta into the design team ticket, sec 14:38:08 does any of the above seem like, whoah nelly we cannot possibly do this? 14:38:25 we could definitely stand to drop a few of these and it'd still be a solid demo 14:38:42 pagure.issue.comment.added -- pingou commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3593 14:39:32 * stickster listens in to see what skrzepto atelic devyani7 pingou (et al.) think 14:39:34 in the left side the main challenge with the feed widget is to add the group support to fmn 14:39:50 +1 14:39:53 we really need to start rolling out new fmn release, I see at least 3 pretty big changes 14:39:59 - 1 the new arch for the backend 14:40:05 - 2 skrzepto 's SSE server 14:40:08 - 3 group support 14:40:23 pagure.issue.comment.added -- sayanchowdhury commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3594 14:40:32 #1 and #2 are there, just need to be merged/released/deployed (gonna take a little time already) 14:40:39 #3 isn't started 14:40:45 pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#166: "Design Team Hub" https://pagure.io/fedora-hubs/issue/166#comment-3595 14:40:48 on the right column: 14:41:05 count members / subscribers / join button -> done 14:41:10 IRC -> WIP 14:41:10 pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#166: "Design Team Hub" https://pagure.io 14:41:20 admins -> TODO 14:41:23 links -> TODO 14:41:30 badges -> TODO 14:41:33 tickets -> TODO 14:42:46 admins + links is easily hard coded though :) 14:42:52 fake it till you make it! 14:42:59 ^^ 14:43:05 :) 14:43:13 :P 14:43:42 and we shall call it the 'fixme' widget :) 14:44:44 mailing list posts -> working? WIP? 14:45:15 mizmo: isn't that in fedmsg already (as in fmn and thus should already work) 14:45:17 ? 14:45:33 pagure.issue.comment.added -- skrzepto commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3596 14:45:46 pingou, i think so, but to get say design-team@lists.fpo to show up in design-team hub - we have to configure that in FMN? does that require the groups support? 14:45:59 mizmo: yes 14:46:05 okay so 14:46:11 mailing list posts -> WIP (FMN groups support) 14:46:14 mizmo: you should be able to set that in FMN for yourself but not yet for groups 14:46:24 https://apps.fedoraproject.org/datagrepper/id?id=2016-fbad5a3e-1503-4461-acf7-6380f6d7f327&is_raw=true&size=extra-large 14:46:36 apparently fedmsg informs there is a new message but not of its content 14:46:44 pagure.issue.comment.added -- skrzepto commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3597 14:46:53 so we may have to query MM3's API for it then 14:47:00 mizmo: ok so that's design 14:47:04 now commops? 14:47:37 for commops, should be very similar - i think the main difference is comm ops has the halp! widget 14:47:52 thats the one radhikak has been working on the design for and i think atelic got the backend done already? 14:48:04 in the demo the two will look different because of the content 14:48:44 pagure.issue.comment.added -- pingou commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3598 14:48:46 lmacken: when you get around, could be useful to review this log 14:49:20 it might be nice for commops to display community blog posts in the feed (similarly to how design team shows planet.fedoraproject.org/design) 14:49:32 * pingou isn't aware of the status of a halp! backend 14:49:35 but i dont know if we have a mechanism for that (showing a particular blog feed) 14:50:06 pingou, ohhh sorry im stupid and confused, plusplus 14:50:12 is planet.fp.o/design on fedmsg/ 14:50:14 ? 14:50:18 halp was the other commops widget, but i dont think we're doing that 14:50:18 mizmo: I was wondering :) 14:50:20 not for flock 14:50:30 * mizmo goes ahead and grabs that coffee, clearly cannot go much longer wo 14:50:31 ok so ++ it is 14:50:34 i dont know if planet.fpo/design is 14:51:20 im guessing probably not :-/ 14:51:21 pagure.issue.comment.added -- skrzepto commented on ticket fedora-hubs#185: "Measure the frequency of visit of a hub" https://pagure.io/fedora-hubs/issue/185#comment-3599 14:51:35 so we may need something that checks it regularly 14:51:37 but tahts one of those things thats not super critical either. if we drop blog feeds, fine. we can just say in demo its a possibility 14:51:48 honestly planet.fpo/design isnt super busy anyway. community blog is tho. 14:52:06 but id say value of blog feeds for flock demo is definitely towards the bottom 14:52:16 ok 14:52:24 what would be more awe inspiring probably would be the meeting stuff with meeting minutes 14:52:38 but its probably harder too :( 14:52:42 minutes are on fedmsg iirc 14:52:47 at least their notif 14:52:56 and meeting we already kinda have iirc 14:53:05 can we link to the minutes instead? 14:53:49 skrzepto, yep, thats all the mockups show anyway is a link 14:54:06 itd be really slick to be able to go to a team's page and see the link for their latest minutes 14:54:19 https://apps.fedoraproject.org/datagrepper/raw?category=meetbot 14:54:36 https://apps.fedoraproject.org/datagrepper/id?id=2016-102fed9d-2ee6-4d64-8e77-88270cce35b2&is_raw=true&size=extra-large 14:54:41 https://meetbot.fedoraproject.org/gluster-meeting/2016-07-13/community_meeting.2016-07-13-12.00 14:54:54 minutes++ 14:55:00 looks like we'll need to fix the url 14:55:05 but basically, doable :) 14:55:15 pingou, yep the meeting end ones would be perfect with the meetbot url 14:55:22 yeh i noticed that one 404s :( 14:55:42 https://meetbot.fedoraproject.org/gluster-meeting/2016-07-13/community_meeting.2016-07-13-12.00.html 14:55:46 just missing the .html 14:56:17 sayan: something to fix for the next fedmsg_meta update :) 14:56:40 pingou: yes, I will be pushing a commit after this meeting 14:56:40 can meeting reminders be done too? 14:57:06 or even just a little widget on the side to say when the team's meetings are 14:57:12 (could just be a link to their fedocal) 14:57:20 both design and commops have fedocals they use 14:57:35 there is already the fedocal widget 14:57:42 that shows the coming meeting in a specified calendar 14:57:58 so you could do a 'Fedora Release' fedocal widget 14:58:08 and a 'commops' fedocal widget 14:58:14 okay great 14:58:20 that's there already :0 14:58:30 with a handy 'Add to calendar' button :) 14:58:41 \o/ 14:58:50 i haven't built it in a while and checked out whats implemented, should do that 14:59:04 btw, I don't know the status of the meeting widget now, but it used to show a lot of future meetings. 14:59:14 it almost takes up the right widget 14:59:18 https://pagure.io/fedora-hubs/issue/180 so I think this be dropped in favor of FMN 14:59:26 can we limit that to maybe 2-3? 14:59:42 I know it's not quite user-friendly (different app), but replicating FMN's UI w/ all the filters in hubs sounds like a not-so-good idea 14:59:52 pingou, for flock yeh, but ultimately can the config be done in hubs and use fmn as backend? 14:59:53 sayan: +1 15:00:11 mizmo: it would mean replicating FMN's UI in there :/ 15:00:27 and there are a lot of rules you can add/remove to a filter 15:00:27 i think its an odd experience tho sending folks to another site 15:00:47 or maybe add a scroll to all the widget with a max height 15:01:04 we could do a simplified version for hubs and fmn is the more powerful one, im not sure that admins are going to want so many options 15:01:06 sayan: a property per widget rather 15:01:15 yes 15:01:16 but maybe we could talk about it after flock and see how we feel then 15:01:21 wfm 15:01:24 mizmo: agreed 15:01:38 pagure.issue.tag.removed -- pingou removed the flock tags from ticket fedora-hubs#180 https://pagure.io/fedora-hubs/issue/180 15:01:40 I found fmn a bit bewildering, but I'm just one person 15:01:40 ill take the flock tag off 180 15:01:43 oh you got it 15:01:46 trying to ^^ 15:01:55 there we go 15:02:06 sayan: https://pagure.io/fedora-hubs/issue/178 15:02:31 pagure.issue.tag.removed -- pingou removed the flock tags from ticket fedora-hubs#179 https://pagure.io/fedora-hubs/issue/179 15:02:37 mizmo: for the same reason ^ 15:03:16 mizmo: pingou: shall we integrate the fmn UI as an iframe? 15:03:17 wfm 15:03:37 ^^ just a suggestion 15:03:45 sayan: it's a possibility but we do not have SSO, so might become a little tricky 15:03:54 Hey, I see https://pagure.io/fedora-hubs/issue/168 is actually referencing an additional Hub altogether (for Badges team) -- is this appropriate for Flock (i.e. easy to populate if the stuff for the other priority Hubs are completed)? 15:04:04 sayan: to investigate post-flock :) 15:04:24 stickster, yep that one needs to be deflocked, we dropped that one a while ago 15:04:33 pagure.issue.tag.removed -- duffy removed the flock tags from ticket fedora-hubs#168 https://pagure.io/fedora-hubs/issue/168 15:04:35 pagure.issue.tag.removed -- duffy removed the flock tags from ticket fedora-hubs#168 https://pagure.io/fedora-hubs/issue/168 15:04:50 https://pagure.io/fedora-hubs/issue/162 should be fairly easy 15:05:10 devyani7: maybe this would suit you better and we can leave https://pagure.io/fedora-hubs/issue/185 to skrzepto ? 15:05:24 pingou: tests in progress, there is one contributor who is working on it right now 15:05:29 * devyani7 clicks the link 15:05:41 sayan: w/ fmn? cool! :) 15:06:01 pingou: nope, statscache https://pagure.io/fedora-hubs/issue/178 15:06:18 sayan: ok, so WIP for this ticket? 15:06:35 pingou: yes 15:06:39 * stickster is in another meeting now but trying to stay tuned in here 15:06:39 pagure.issue.assigned.added -- pingou assigned ticket fedora-hubs#178 to sayanchowdhury https://pagure.io/fedora-hubs/issue/178 15:06:46 pingou: wfm :) 15:06:49 sayan: still ok w/ it for flock? 15:06:58 pingou: yes 15:07:12 pingou: mizmo: but there is a question :) 15:07:24 * pingou has a hard-stop in 10 minutes 15:07:31 sure 15:07:41 I never noticed this ticket, what is the plans for statscache and hubs? 15:08:10 I think just including some stats in some widgets 15:08:15 sayan, https://github.com/fedora-infra/statscache/issues/50 basically we need it to be running and usable 15:08:59 mizmo: yes, but would there be integration with hub? 15:09:59 sayan, yeh i think some widgets were going to need it (not ones for flock iirc) 15:10:22 should we try to assign some more tickets? 15:10:25 https://pagure.io/fedora-hubs/issues?assignee=0&tags=flock 15:10:35 we have 13 un-assigned tickets for flock 15:10:41 mizmo: the focus for the ticket is to deploy stascache with some graphs :) 15:10:59 sayan: https://pagure.io/fedora-hubs/issue/27 doable for flock ? 15:11:11 radhikak back , reading through the meeting logs 15:11:14 mizmo: https://pagure.io/fedora-hubs/issue/33 this one I would take off the table for now 15:11:25 sayan, im actually confused why the statscache one is taggedf or flock 15:11:27 pingou: no, for flock 15:11:38 pagure.issue.tag.removed -- pingou removed the flock tags from ticket fedora-hubs#27 https://pagure.io/fedora-hubs/issue/27 15:11:59 sayan: https://pagure.io/fedora-hubs/issue/17 assigned to you? 15:12:22 mizmo: also for integrating statscache we need to write plugins seperately 15:12:25 pingou: yes 15:12:33 pagure.issue.assigned.added -- pingou assigned ticket fedora-hubs#17 to sayanchowdhury https://pagure.io/fedora-hubs/issue/17 15:13:13 pingou, taking 33 off seems fine 15:13:36 radhikak: https://pagure.io/fedora-hubs/issue/161 wanna play with bootstrap and css? :) 15:13:46 pagure.issue.tag.removed -- pingou removed the flock tags from ticket fedora-hubs#33 https://pagure.io/fedora-hubs/issue/33 15:14:29 devyani7: assigning https://pagure.io/fedora-hubs/issue/162 to you then :) 15:14:31 radhikak clicks the link 15:14:31 thanks :) 15:14:35 +1 15:14:37 pagure.issue.assigned.added -- pingou assigned ticket fedora-hubs#162 to devyani7 https://pagure.io/fedora-hubs/issue/162 15:14:48 pingou, oh hey we were talking about hard coding that widget (161) - it already exists 15:15:20 mizmo: the one that doesn't is #4 (the library) 15:15:47 skrzepto: interested by https://pagure.io/fedora-hubs/issue/185 ? 15:15:51 pingou, right 15:15:58 pagure.issue.assigned.added -- devyani7 assigned ticket fedora-hubs#185 to skrzepto https://pagure.io/fedora-hubs/issue/185 15:16:07 ^^ 15:16:09 Seems doable , but I guess will needing a lot of pictures :P 15:16:13 :) 15:16:32 radhikak, the widget is already implemented, you just need to ellipsize the list 15:16:35 radhikak: take a group such as packager, there will be a lot of sponsors/admins 15:16:54 it already exits 15:17:07 mizmo: https://pagure.io/fedora-hubs/issue/173 seems related 15:17:09 yeh theres some bootstrap ellipsize function i think that you could use 15:17:26 pingou, yep 15:17:35 * skrzepto clicks 15:18:10 I suppose i can take it 15:18:15 cool :) 15:18:51 pingou, ill finish up some more functional tests for fas3 and ill get started with 185 15:19:00 thanks 15:19:10 pingou, why dont we drop library widget from flock 15:20:04 mizmo: I'm having an idea for it, I'll see what I can do and otherwise we drop it +1 15:20:16 pagure.issue.assigned.added -- pingou assigned ticket fedora-hubs#4 to pingou https://pagure.io/fedora-hubs/issue/4 15:20:26 pingou, okay cool :) 15:20:35 https://pagure.io/fedora-hubs/issues?assignee=0&tags=flock 8 left 15:20:47 142 and 166 cannot be assigned 15:20:47 Any widget available :) pingou mizmo 15:21:05 pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#142: "CommOps Hub design" https://pagure.io/fedora-hubs/issue/142#comment-3600 15:21:12 radhikak: https://pagure.io/fedora-hubs/issue/169 ? 15:22:00 mizmo: sudden though, isn't the ++ widget a 'personal' widget (as is not a team one) ? 15:22:09 you ++ someone, not a team no? 15:22:16 Where would the data from https://pagure.io/fedora-hubs/issue/159 come from? 15:22:22 pingou, ah youre right it is a personal hub widget 15:22:22 Seems interesting , design and implementation ? 15:22:33 radhikak: please :) 15:22:34 Yes pingou you ++ a person 15:22:42 pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#142: "CommOps Hub design" https://pagure.io 15:22:42 atelic: FAS 15:22:58 pingou, is ipsilon ready for that? 15:23:14 atelic: sorry, hubs info come from hubs 15:23:30 radhikak, yeh 169 needs design and implementation, should be similar to www.patternfly.org/pattern-library/communication/empty-state/ 15:23:34 the level is from FAS (admins/user...) 15:23:45 skrzepto: we need to push puiterwijk a little further for that :D 15:23:46 On it then mizmo and pingou 15:23:57 thanks radhikak 15:24:05 pagure.issue.assigned.added -- pingou assigned ticket fedora-hubs#169 to radhikamani88 https://pagure.io/fedora-hubs/issue/169 15:24:14 pingou: okay, I can probably pick that one up 15:24:17 what am I going to be pushed on? 15:25:07 pagure.issue.assigned.added -- pingou assigned ticket fedora-hubs#159 to atelic https://pagure.io/fedora-hubs/issue/159 15:25:17 puiterwijk: having ipsilon return the user's status in a group :) 15:25:35 pingou: I see.. 15:25:52 * puiterwijk notes once more that Ipsilon doesn't get that info from FAS, so I'll need to do more FAS API calls 15:26:03 https://pagure.io/fedora-hubs/issues?assignee=0&tags=flock 15:26:11 we're down to 6, but I really have to go now 15:26:18 #chair mizmo 15:26:18 Current chairs: mizmo pingou 15:26:30 can I let you finish and I'll read the backlog? 15:26:37 sure :) 15:27:05 thanks 15:27:06 anybody up for taking this one? https://pagure.io/fedora-hubs/issue/158 15:27:11