14:02:29 <pingou> #startmeeting fedora-hubs
14:02:29 <zodbot> Meeting started Tue Jun 21 14:02:29 2016 UTC.  The chair is pingou. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:29 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:02:29 <zodbot> The meeting name has been set to 'fedora-hubs'
14:02:37 <pingou> #topic rollcall
14:02:38 <mizmo> \o
14:02:38 * pingou here
14:02:43 <mizmo> .hello duffy
14:02:43 * skrzepto is here
14:02:44 <zodbot> mizmo: duffy 'Máirín Duffy' <fedora@linuxgrrl.com>
14:02:49 <devyani7> .hello devyani7
14:02:50 <zodbot> devyani7: devyani7 'Devyani Kota' <devyanikota@gmail.com>
14:02:50 <radhikak> .hello radhikamani88
14:02:53 <zodbot> radhikak: radhikamani88 'Radhika Kolathumani' <radhikak@umich.edu>
14:03:04 <sayan> .hello sayanchowdhury
14:03:05 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
14:03:14 <pingou> sayan: are you still or are you available?
14:03:34 <sayan> pingou: available, I just lost track of time
14:03:38 <pingou> ok :)
14:03:54 <pingou> stickster: said he wouldn't make the meeting
14:04:04 <pingou> I pinged abompard this morning but haven't heard back from him
14:04:29 <pingou> let's move on to the updates
14:04:35 <pingou> #topic status updates
14:04:48 <pingou> devyani7: would you like to start?
14:04:59 <devyani7> pingou: sure, ok :)
14:05:37 <pingou> go ahead :)
14:05:37 <devyani7> so, we have the edit button that lists down the bookmarks
14:05:57 <devyani7> and also allows reordering,
14:06:03 <mizmo> \o/
14:06:12 <devyani7> I took a while there fidgeting with js :( my bad
14:06:52 <devyani7> anyway, pr coming for that^^^
14:07:01 <devyani7> mizmo: :)
14:07:05 <pingou> cool, looking forward :)
14:07:13 <devyani7> now am working on the frequency part of the task
14:07:27 <devyani7> added priority field, and populating it
14:07:30 <pingou> most consulted hubs?
14:07:42 <devyani7> pingou: yup
14:07:45 <pingou> nice
14:07:57 <devyani7> s/priority/hub_views
14:08:03 <sayan> devyani7: hubs_views right?
14:08:17 <devyani7> sayan: yup, rectified^^ :)
14:08:20 <sayan> ah! yes :)
14:08:31 <devyani7> so working on showing the dialog box
14:08:52 <devyani7> until the user closes it^^
14:09:14 <devyani7> <eom>
14:09:36 <pingou> hm, I'm not sure to follow, what's in the dialog box?
14:09:56 <devyani7> um, a suggestion to move the bookmark frequently visited
14:10:02 <devyani7> furthr up in the list
14:10:06 <pingou> ah ok, I see
14:10:06 <devyani7> further*
14:10:16 <pingou> cool cool :)
14:10:29 <pingou> atelic: want to continue?
14:10:41 <atelic> Sure thing
14:11:29 <atelic> Last week skrzepto brought up the issue of test coverage so I have been working with him to add tests to the api and he has a big PR against develop for the 45+ tests that were added
14:11:44 <skrzepto> +1
14:11:50 <skrzepto> atelic++
14:11:50 <zodbot> skrzepto: Karma for atelic changed to 1 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
14:12:05 <pingou> nice team work on that!
14:12:43 <atelic> also last week we talked about adding Reactjs as a tool for hubs to begin using so as a proof of concept I wrote out the Feed widget with that and it is up for review
14:13:16 <sayan> atelic++ \o/
14:13:16 <zodbot> sayan: Karma for atelic changed to 2 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
14:13:35 <atelic> I do have some concerns about the implemtation pingou pointed out here: https://pagure.io/fedora-hubs/pull-request/200#comment-6445 so I need to look into that
14:14:02 <atelic> i also made sure to add in the SSE code from before into the react verson to kill two birds
14:14:24 <atelic> </update>?
14:14:43 <atelic> h/t skrzepto for tests
14:14:43 <pingou> thanks atelic ! :)
14:15:00 <atelic> :)
14:15:07 <devyani7> atelic++ skrzepto++ :)
14:15:07 <zodbot> devyani7: Karma for atelic changed to 3 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
14:15:10 <zodbot> devyani7: Karma for skrzepto changed to 1 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
14:15:14 <pingou> skrzepto: do you have more goodies than the tests?
14:16:01 <skrzepto> Not much more, just poking hubs and finding holes in it and reporting issues. One of which i caused with the model change which is fixed and now im writing tests so it won't happen again.
14:17:04 <pingou> cool :)
14:17:14 <fedmsg-hubs> pagure.pull-request.comment.added -- sayanchowdhury commented on pull-request#200 of project "fedora-hubs" https://pagure.io/fedora-hubs/pull-request/200#comment-6459
14:17:17 <pingou> radhikak: I saw you kept on working on the calendar widget :)
14:17:49 <radhikak> Yes, I was reworking on calendar widget and release cycle last week
14:18:28 <radhikak> and finally setup up my blog up and running, but still have to add a template so as to enable user comments
14:19:22 <radhikak> I have received some feedback on the last issues that I have worked on and will be continuing to work on it this week along with hyper kitty heuristic
14:19:27 <fedmsg-hubs> pagure.pull-request.comment.added -- pingou commented on pull-request#199 of project "fedora-hubs" https://pagure.io/fedora-hubs/pull-request/199#comment-6460
14:20:16 <radhikak> Further, mo and I discussed about improving the documentation for fedora bootstrap
14:20:45 <atelic> +1 on that
14:21:05 <sayan> radhikak: cool :)
14:21:29 <pingou> more doc is always good :)
14:21:52 <radhikak> So will be working on it as well. Just wanted to double check my thoughts on the help widget https://pagure.io/fedora-hubs/issue/98
14:22:36 <radhikak> I was hoping to see the reasoning that I posted on ticket is correct or not
14:23:49 <mizmo> radhikak, i think the way it works based on the fedmsg doc entry is that someone in a meeting uses the #help hashtag in a meeting
14:24:08 <pingou> correct
14:24:10 <mizmo> each meeting has a topic/team
14:24:20 <mizmo> and the person will write a message to go with the #help tag
14:24:29 <mizmo> and the msg of course will have a date
14:24:39 <mizmo> so i'd suggest something - to use the docs example -
14:24:40 <pingou> #help radhikak would like feedbacks on her thoughts on the ticket https://pagure.io/fedora-hubs/issue/98
14:24:49 <mizmo> the help widget could have a listing by team of who needs helpk, eg
14:24:57 <mizmo> "“The #fedora-apps team needs people to help review code http://ambre.pingoured.fr/fedora-infra/“
14:25:07 <mizmo> they could be broken down by team / meeting name / or even date
14:25:10 <pingou> (where have I seen this one before?)
14:25:24 <pingou> and person I guess
14:25:26 <mizmo> probably the newest ones should be most prominent and the oldest ones should scroll off bc as it gets older probably less likely they still need the help
14:25:39 <mizmo> yeh the person who called for help should be listed next ot each item
14:26:05 <mizmo> i guess maybe think of it like a bulletin board where people are looking for babysitters or dog walkers or whatever, the help widget is sort of abulletin board where people look for help across the project
14:26:29 <mizmo> i can copy/pasta this into the ticket
14:26:35 <pingou> +1
14:26:48 <radhikak> Ohh cool, I do have ideas on how to work on it.
14:27:28 <fedmsg-hubs> pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#98: "#halp/help widget: Default in the CommOps Hub" https://pagure.io/fedora-hubs/issue/98#comment-3332
14:27:53 <pingou> radhikak: anything else? :)
14:28:02 <fedmsg-hubs> pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#98: "#halp/help widget: Default in the CommOps Hub" https://pagure.io
14:28:11 <radhikak> nope that's all for me
14:28:28 <pingou> mizmo: want to continue?
14:28:33 <mizmo> sure
14:28:43 <mizmo> basically i've been working on the localization team hub and some widget ideas for it
14:28:48 <mizmo> https://scontent-atl3-1.cdninstagram.com/t51.2885-15/e35/13395003_860468670763220_1948141851_n.jpg?ig_cache_key=MTI3NDEyOTAyNjkwNjMxNjg1Mg%3D%3D.2
14:29:08 <mizmo> i was going to meet with the team last night but they had to reschedule so we're on for next tuesday night i think
14:29:21 <pingou> nice
14:29:43 <mizmo> yep next tues (just double checked)
14:29:55 <mizmo> i have more ideas for widgets on individual translators pages - in that funky screenshot is for translators as a group
14:30:21 <mizmo> also need to mock up a page for each individual translation team, so there are going to be 3 types of translation widgets (translation team - all langs, individual language teams, individual translators)
14:30:38 <mizmo> one question i have, not sure if anybody has ideas
14:30:56 <mizmo> i was thinking it might be neat if we could notify (maybe in the feed widget) translators when a new version of a package is built that includes a new po file
14:31:04 <mizmo> is this tricky or possible?
14:31:27 <mizmo> i think they would like to see the new translations in context in the built code to check their work
14:31:40 <pingou> in theory doable with our summershum
14:31:49 <pingou> but since we never deployed the API in front of it
14:31:55 <pingou> it becomes trickier
14:32:02 <mizmo> okay
14:32:12 <mizmo> so i can design the front end for it but with the caveat it is likely not going to be in the flock prototype
14:32:21 <pingou> w/ summershum we could check if a file in a package changed compared to another package (2 versions here)
14:32:34 <pingou> but it would report true, even if, say, just a date changed
14:32:43 <sayan> can we check if there is new po file?
14:32:53 <pingou> mizmo: unlikely to be in 1.0 either
14:32:55 <mizmo> im trying to figure out where the po files are too... if there is something on the message bus when a commit gets pushed to a po file (i am not sure)
14:33:10 <pingou> po files are upstream
14:33:16 <mizmo> the po's dont seem to be in individual upstreams that i checked
14:33:23 <mizmo> i think if it comes from zanata there is some other process
14:33:30 <pingou> sayan: with summershum we could (compare the list of files in the 2 versions)
14:33:34 <mizmo> eg anaconda https://github.com/rhinstaller/anaconda/tree/master/po
14:33:52 <mizmo> ohh
14:33:52 <pingou> mizmo: they should be pulled in when they make a release
14:33:54 <sayan> pingou: nice
14:33:55 <mizmo> maybe bc they are in gitignore
14:34:06 <mizmo> pingou, are they pulled from zanata?
14:34:36 <mizmo> i think it's probably too tricky but was thinking it'd be nice to have messages when new translation strings are submitted
14:34:53 <pingou> https://github.com/rhinstaller/anaconda/blob/master/po/Makefile.am#L95 apparently
14:35:11 <pingou> submitted to zanata, I believe skrzepto asked for it
14:35:23 <pingou> but changed upstream, I don't think that's something we can easily do
14:35:37 <mizmo> unless maybe zanata has api for it
14:35:44 <skrzepto> yup i have
14:35:47 <mizmo> if upstream doesn't use zanata tho there isnt a way
14:36:01 <mizmo> skrzepto, noriko's team has your ticket too
14:36:10 <mizmo> it came up during some conversation with them so that is good
14:36:36 <skrzepto> nice :) im eager to work on the fedmsg2zanata project
14:36:48 <mizmo> well that's about all i have, i dont want to hog up anymore time. if anybody has ideas for l10n lemme know, even crazy ideas (<= good brain food :) )
14:36:56 <mizmo> skrzepto, sweet :) the translators are going to love it
14:37:19 <mizmo> skrzepto, oh! i can give you a normal version of that mockup too if thats helpful at this point
14:37:37 <pingou> don't we need changes on zanata first?
14:37:59 <skrzepto> mizmo, that would be great :) i can include into the issue i sent zanata so they have a visual
14:38:05 <mizmo> yep! the idea with the mockup being skrzepto can see what kind of data he needs from them
14:38:20 <pingou> ah in that way, +1
14:38:34 * mizmo doesn't always know what ponies she needs to ask for until she mocks it up
14:39:35 <pingou> sayan: want to continue?
14:40:03 <sayan> pingou: sure
14:40:30 <sayan> As you know I was working on the auth part of waartaa
14:40:51 <sayan> I finally got to integrate redux-oidc and login works
14:41:07 <pingou> \ó/
14:41:29 <sayan> And also I have been working on the badges widgets for user profile
14:41:57 <sayan> I made some changes to tahrir to push some more data via the user profile json
14:42:21 <mizmo> sweet!
14:42:30 <sayan> From the code point of where it's done
14:42:33 <mizmo> sayan, anything for the paths / linear badge stuff?
14:42:58 <sayan> mizmo: that's next. After this issue I will be on it
14:43:06 <mizmo> cool :)
14:43:28 <sayan> Right now I am working on the frontend part for the badges widget.
14:43:42 <pingou> cool
14:43:48 <pingou> sayan: react or old-style? :)
14:44:05 <sayan> The problem I am facing is looking for the appropriate class in fedora-bootstrap
14:44:44 <sayan> pingou: old-style, should I move that to react?
14:44:49 <sayan> that would be good actually
14:44:59 <pingou> sayan: might be an idea
14:45:06 <pingou> since atelic started some work on this
14:45:10 <fedmsg-hubs> pagure.issue.comment.added -- radhikamani88 commented on ticket fedora-hubs#57: "PlusPlus Widget" https://pagure.io/fedora-hubs/issue/57#comment-3333
14:45:37 <atelic> hopefully it won't be hard to add in now that the basic setup is there
14:45:41 <sayan> pingou: yes, I helped atelic with SSE issue :)
14:45:45 <sayan> atelic: yes
14:45:57 <pingou> I'd say go for it then :)
14:46:16 <pingou> on my side
14:46:29 <pingou> I finally have the entire pipeline set-up for FMN
14:46:43 <pingou> from the fedmsg consumer to the different backends via the worker(s)
14:47:04 <pingou> I'm testing it w/ real-life data (ie fedmsg-hub listening to the prod fedmsg)
14:47:33 <pingou> and some messages are taking way too long to be processed (like 20 minutes for bugzilla or mailman messages)
14:47:37 <pingou> I tackle these two
14:47:48 <pingou> I'm now onto org.fedoraproject.prod.taskotron.result.new
14:47:57 <pingou> which is running for more than 1h here :(
14:48:23 <pingou> once these optimisations are done, I think we'll be good to move to stg :)
14:48:38 <pingou> which also means, we'll be able to start working on the actual SSE skrzepto :)
14:48:41 <rtnpro> Hi
14:48:45 <pingou> o/ rtnpro
14:48:46 <skrzepto> pingou, nice :)
14:48:57 * sayan waves to rtnpro
14:49:13 <pingou> so fingers crossed we'll be ready next week
14:49:17 <rtnpro> I worked on implementing a the log store for IRCB logs
14:49:31 <pingou> skrzepto: we the SSE, we may be able to check it before that
14:49:37 <pingou> org.fedoraproject.prod.taskotron.result.new -> DEBUG:fmn:results retrieved in: 5331.58s
14:49:48 <pingou> I think we need to improve there ^ :)
14:49:56 <rtnpro> I am currently working to create a subscriber API to subscribe to realtime IRC logs and expose it to waartaa
14:50:02 <pingou> rtnpro: with the retention policy discussed earlier?
14:50:30 <pingou> rtnpro: realtime IRC logs, using which tech? sse? ws?
14:50:32 <rtnpro> pingou, yes, that can be done, but I am not focusing on the policies, right now
14:50:36 <pingou> ok
14:50:48 <rtnpro> pingou, inspired by meteor, of course
14:50:57 <pingou> meteor?
14:51:08 <rtnpro> pingou, we have our zeromq backed store for that
14:51:26 <skrzepto> pingou, where's the code reside for "org.fedoraproject.prod.taskotron.result.new -> DEBUG:fmn:results retrieved in: 5331.58s" I would like to take a look :)
14:51:29 <rtnpro> pingou, actually inspired by meteor, fedmsg, flux and a lot of stuffs
14:51:47 <rtnpro> pingou, I mean the concepts
14:52:14 <pingou> skrzepto: in fmn
14:52:18 <rtnpro> pingou, I will share the PR with you for review :D
14:52:21 <pingou> rtnpro: ok cool :)
14:52:26 <pingou> rtnpro: now I'm scared :D
14:52:38 <sayan> :D
14:53:11 <fedmsg-hubs> pagure.pull-request.comment.added -- atelic commented on pull-request#200 of project "fedora-hubs" https://pagure.io/fedora-hubs/pull-request/200#comment-6461
14:53:34 <fedmsg-hubs> pagure.pull-request.comment.edited -- atelic edited a comment on pull-request#200 of project "fedora-hubs" https://pagure.io/fedora-hubs/pull-request/200#comment-6461
14:54:04 <sayan> skrzepto: you next?
14:54:13 <pingou> sayan: I think I was last :)
14:54:19 <pingou> did I miss anyone?
14:54:37 <pingou> if so
14:54:40 <sayan> oh! then i did miss skrzepto updates
14:54:42 <pingou> #topic open-floor
14:54:53 <fedmsg-hubs> pagure.issue.new -- jflory7 opened a new ticket fedora-hubs#203: "Create a "News" aggregator widget from variety of sources" https://pagure.io/fedora-hubs/issue/203
14:55:01 <pingou> has anyone some ideas/thoughts they would like to share?
14:55:07 <fedmsg-hubs> pagure.issue.comment.added -- jflory7 commented on ticket fedora-hubs#203: "Create a "News" aggregator widget from variety of sources" https://pagure.io/fedora-hubs/issue/203#comment-3334
14:55:08 <fedmsg-hubs> pagure.issue.edit -- jflory7 edited the priority fields of ticket fedora-hubs#203 https://pagure.io/fedora-hubs/issue/203
14:55:52 <fedmsg-hubs> pagure.issue.tag.added -- jflory7 tagged ticket fedora-hubs#203: widget https://pagure.io/fedora-hubs/issue/203
14:55:53 <skrzepto> The authorization layer is still missing in hubs. When do you think would be a good time to insert it?
14:56:28 <pingou> skrzepto: anytime would be good, but getting a working prototype for flock would be higher on my list
14:56:40 <pingou> and that's already going to be tight :)
14:56:50 <skrzepto> pingou, alright ill put that to my backlog for now then
14:57:16 <pingou> should we close?
14:57:22 <pingou> we're reaching the hour
14:57:22 * devyani7 raises hand
14:57:32 <pingou> devyani7: don't ask to ask :)
14:57:50 <devyani7> pingou: since frequency part of the task is related to issue #11
14:58:00 <devyani7> should I add commits and then PR
14:58:08 <devyani7> or PR then commits
14:58:17 <devyani7> sayan^^^
14:58:24 <pingou> let's do one feature at a time
14:58:32 <pingou> small steps are always easier
14:58:55 <devyani7> pingou: the thing is order isn't being saved to db yet
14:59:00 <sayan> I am for doing commits that works and PR
14:59:19 <devyani7> so ?
14:59:29 <pingou> devyani7: why not?
14:59:42 <devyani7> pingou: since WIP :P am afraid
14:59:56 <pingou> devyani7: then don't you want to finish before moving on to something else?
15:00:07 <pingou> :)
15:01:09 <devyani7> pingou: nod nod, just that I felt things were synced with #185
15:01:17 <devyani7> will do that :) thanks
15:01:45 <pingou> cool :)
15:02:35 <devyani7> <eom>
15:02:39 <pingou> should we close?
15:02:44 <pingou> 3
15:02:47 <pingou> 2
15:02:59 <pingou> one
15:03:30 <pingou> #endmeeting