14:03:59 #startmeeting fedora-hubs 14:03:59 Meeting started Tue May 3 14:03:59 2016 UTC. The chair is pingou. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:59 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:03:59 The meeting name has been set to 'fedora-hubs' 14:03:59 .hello pfrields 14:04:00 stickster: pfrields 'Paul W. Frields' 14:04:05 #meetingtopic roll call 14:04:11 .hello pingou 14:04:12 pingou: pingou 'Pierre-YvesChibon' 14:04:12 .hello dhrish20 14:04:15 dhritishikhar: dhrish20 'Dhriti Shikhar' 14:04:20 .hello devyani7 14:04:21 devyani7: devyani7 'Devyani Kota' 14:04:22 .hellom sayanchowdhury 14:04:26 oops 14:04:27 .hello dhanesh95 14:04:30 dhanesh95: dhanesh95 'Dhanesh Bhalchandra Sabane' 14:04:32 .hello sayanchowdhury 14:04:33 sayan: sayanchowdhury 'Sayan Chowdhury' 14:05:05 anyone else? 14:05:26 #meetingtopic hubs status 14:05:37 so what's new? :) 14:05:52 I've been working on improving the meeting widget 14:06:16 so something like the 'Add to calendar' button works, or the description is cut at 150 characters with a link to the meeting in fedocal 14:06:23 oooh 14:06:37 I also look at customizing the favicon per hub 14:07:01 but ryanlerch isn't really fan of the idea 14:07:11 https://pagure.io/fedora-hubs/issue/73 for the discussion 14:07:12 * jflory7 is around-ish 14:07:17 pingou, i saw that ticket too, i'm not a fan either 14:07:36 mizmo: and of the notification? 14:07:41 i think changing the favicon in some way to indicate new content might be nice - and other websites do this sort of thing. but changing it per user i think is too much, i agree with ryanlerch 14:07:49 ok 14:07:57 I'll adjust the PR in this sense then 14:08:28 and it will make notifying easier as otherwise depending on the avatar the notification is more or less easy to see 14:08:44 yeh definitely 14:08:49 * pingou 's red avatar didn't work well with a red dot 14:09:07 sometimes sites (and i dont know how they do this) bold their which makes the tab blink 14:09:19 <pingou> oh, joining a hub already worked :] 14:09:32 <pingou> mizmo: pagure does that when a comment is added to the page while you're not working 14:09:41 <sayan> tab blink happens in pagure also 14:09:44 <pingou> bolding and blinking are two actions though 14:09:55 <mizmo> pingou, oh yes it does! that sort of thing would be nice 14:10:14 <mizmo> i would say make the ticket more generically about notifying about new content in tab, maybe favicon isn't the best / only implementation 14:10:22 <mizmo> btw i did a ton of triage last week 14:10:25 <mizmo> i cleaned out the tags too 14:10:31 <pingou> yes, thanks a lot for that :) 14:11:19 <sayan> we can add number of notifications in the title 14:11:23 <pingou> mizmo: I might prefer we make another ticket for notifying by blinking the tab, otherwise we end up never closing tickets :) 14:12:08 <pingou> we will need a way to notify users of new content, but that is also only of interest once we have the SSE or web-socket in place 14:12:40 <sayan> pingou: +1 14:13:02 <pingou> I've been thinking about this 14:13:15 <pingou> I wonder if we shouldn't implement it on FMN itself 14:13:31 <pingou> then hubs could just listen to it and act accordingly 14:14:00 <pingou> basically, I would prefer if we only evaluated FMN's rules in one place 14:14:28 <pingou> instead of doing it once in FMN for some messages, then once in hubs for the hubs notifications 14:15:11 <devyani7> pingou: +1, sounds right :) 14:15:14 <mizmo> are we talking about msg filtering or notification? 14:15:23 <mizmo> i think the filtering should be done in context as much as possible 14:15:51 <pingou> then the message is added to the hub(s) and the users watching these hubs are notified 14:16:14 <sayan> What is message filtering? 14:16:16 <pingou> but the "add message to hub" and the "notify user of new message" is going to be the same process basically 14:16:42 <pingou> sayan: infra related fedmsg message (and not ambassador related messages) being added to the infra hub 14:17:04 <pingou> does that make sense? 14:17:20 <sayan> yes, got it 14:17:33 <mizmo> if the notification is a favicon change or a tab blink, how would FMN do that? 14:17:35 * mizmo confused 14:18:13 <pingou> mizmo: FMN listens to fedmsg, check if the message that comes in fits some rules 14:18:34 <pingou> if it does, it will send a message, eventually via server-sent-event to hubs 14:18:39 * sayan brb 14:18:53 <pingou> hubs will get this message, add it to the page, blink/adjust the favicon 14:19:28 <pingou> when the user focuses on the page, title and favicon are reset 14:19:41 <mizmo> ah okay 14:19:45 <mizmo> cool, i get it 14:19:49 <mizmo> that makes sense 14:19:51 <sayan> sounds good to me 14:20:13 <pingou> cool :) 14:21:03 <pingou> the added bonus, is that if we manage to improve FMN's way of handling new messages, we'll be improving things for all notifications (irc, email, hubs...) 14:22:01 <mizmo> yes :) 14:22:24 <pingou> ok, I think that's all I've got on my side 14:22:38 <mizmo> another thing is we didn't really finish this https://etherpad.gnome.org/p/fedora-hubs-roadmap 14:23:14 <pingou> oh, I said it but quickly, 'joining' a hub already works :) 14:23:25 <pingou> if you click on it, it'll add the hub to your bookmark bar 14:23:51 <pingou> and you can leave the hub as well, the missing part is the fedmsg message to clear the cache 14:24:55 <mizmo> ooh 14:26:58 * pingou notes that there is WIP in pagure to add a roadmap feature 14:26:59 * mizmo is looking thru the etherpad 14:27:10 <mizmo> nice! 14:27:21 <mizmo> well for now we can use a 'flock' tag on tickets right? for flock roadmap items 14:27:27 <pingou> sure yes 14:27:27 <mizmo> i'm not 100% sure we have everything we need in this doc tho 14:27:43 <pingou> I am fairly confident we don't :) 14:28:16 <pingou> I start to wonder if we need more panels 14:28:27 <pingou> http://209.132.184.98/ambassadors/ like the owners there 14:28:31 * mizmo looks 14:28:37 * sayan clicks 14:28:41 <pingou> should we show just some and have a panel to show them all? 14:28:47 * devyani7 clicks too 14:28:55 <mizmo> oh boy that's too many in one lol 14:29:16 <pingou> which means, we could do something like: hub template vs panel template 14:29:29 <mizmo> i think for the right sidebar widgets, where there's more than say 4 or 5 in a data set, should generate a "view all" link that takes you to a subpage for more of the stuff 14:29:30 <pingou> it could also be useful for the meeting widget, instead of sending people to fedocal 14:29:47 <pingou> mizmo: so my question was to use panel instead of sub-page 14:29:58 <pingou> w/ the idea that you never leave the hub 14:29:58 <mizmo> pingou, what do you mean by panel? a modal? 14:30:03 <pingou> yes, sorry 14:30:07 <mizmo> ohh okay 14:30:19 <pingou> (what we use to edit/add a widget) 14:30:29 <mizmo> a modal might be okay 14:30:46 <mizmo> modals can be a little weird if they are very long and have to scroll though 14:30:49 <mizmo> weird / annoying 14:31:02 <pingou> true 14:31:11 <mizmo> but for most cases i dont see them being a problem (keeping in mind that bootstrap modals should support mobile) 14:31:15 <pingou> they would need a 'Open in a new page' then I guess 14:31:22 <mizmo> yeh 14:31:49 <pingou> has anyone tested the current website in a mobile? 14:32:01 <sayan> nope 14:32:10 <sayan> but can do it right now 14:32:29 * pingou is trying as well 14:32:53 * mizmo isnt sure how to 14:33:08 <pingou> mizmo: no smartphone or tablet? 14:33:24 <mizmo> pingou, i have one but it can't connect to localhost on my laptop 14:33:37 <pingou> mizmo: try the cloud instance :) 14:33:51 <mizmo> pingou, do you have the url handy? 14:33:54 <pingou> http://209.132.184.98/ambassadors/ 14:34:01 <mizmo> oh thats it okay 14:34:05 <pingou> or plain http://209.132.184.98/ 14:34:05 <mizmo> are you keeping that one updated? 14:34:18 <pingou> I think it's almost up to date 14:34:36 <pingou> (like the change to the meeting widget isn't there but the edit/add/remove widget is) 14:34:44 <mizmo> hm not ideal mobile wise 14:34:49 <mizmo> the CSS needs some work 14:35:08 <pingou> here it gives me the same style as on desktop 14:35:11 <sayan> it's the desktop site, I think we need to work on the mobile 14:36:02 <mizmo> where in the priority do we want it tho 14:36:22 <mizmo> i guess it depends how much work it is to do 14:36:29 <pingou> one issue, is that iirc SSE isn't supported on mobile device 14:36:33 <mizmo> i wouldn't put it in level 1 prioirty 14:36:40 <pingou> which means we would have to use websocket instead of SSE 14:37:15 <mizmo> codeblock was interested in doing a mobile app 14:37:33 <sayan> mizmo: +1, mobile shouldn't be in level 1 14:38:55 <pingou> http://www.w3schools.com/HTML/html5_serversentevents.asp SSE is also not supported by IE 14:38:57 <mizmo> ill mark it level 2 14:39:05 <pingou> ok, I don't really mind :] 14:39:20 <mizmo> pingou, my thought about IE is.... heh 14:39:27 <mizmo> not too worried about it 14:39:41 * pingou has never really be worried about IE 14:40:17 <pingou> https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events#Browser_compatibility this is more annoying 14:40:42 <pingou> oh, it's actually better than last time I checked 14:40:49 <pingou> but still no Firefox Mobile :( 14:41:14 <mizmo> i dont think firefox mobile is widely used anymore, didnt they discontinue support? 14:41:27 * mizmo used to use it exclusively for the bookmark sync capability but it had problems rendering a lot of stuff 14:41:28 <pingou> not that I know 14:41:35 <sayan> mizmo: it's the firefox os they discontinued 14:41:52 <sayan> I don't think it's the same 14:41:56 <pingou> agreed 14:42:04 <mizmo> sayan, ohhh okay 14:42:42 <mizmo> i still think its an edge case, esp with firefox os out of the picture, it's only people who wanted it who installed it, and they likely still have the default / os browser on the phone 14:43:15 <pingou> anyway, starting with SSE is easy and shouldn't be a big problem 14:43:38 <pingou> if it turns out it is, we can revisit and see about switching to web-socket 14:43:49 <mizmo> okay cool 14:43:53 <pingou> WS will be more work than SSE anyway 14:44:39 <pingou> do we have something else on our plate ? 14:44:40 <mizmo> is there anything in flock demo section of the document that doesn't make sense or is missing? 14:44:58 <mizmo> maybe starting with what we want to demo and working back from that (stuff necessary for demo should be level 1 priority) 14:45:11 <pingou> mizmo: sounds good 14:45:35 <mizmo> - Auto-Generated User Hub (amazing) 14:45:39 <mizmo> need to figure out what goes on this 14:45:52 <mizmo> there are mockups tho 14:46:31 <mizmo> - Shows FAS Groups you are in 14:47:44 <mizmo> https://pagure.io/fedora-hubs/issue/raw/files/6beed7d9cf562725001abc14d5b341c8e689c295eaf81e23daa747003f53cfd0-profile-vs-stream_profile-someoneelse.png 14:48:26 <mizmo> something like that 14:48:47 <mizmo> but needs refinement for membership in our priority groups 14:49:58 <mizmo> i think what ill work on today is going through this demo script and refining it a bit more 14:50:03 <mizmo> and starting to make tickets for work items 14:50:05 <mizmo> does that make sense? 14:50:11 <pingou> sounds good 14:50:16 <mizmo> (and tagging tickets we already have that support the demo with 'flock' tag) 14:50:17 <pingou> the simpler the ticket the better 14:50:19 <sayan> mizmo: yeah 14:50:26 <pingou> it gives us small steps and we see progress :) 14:50:48 <devyani7> +1 :) 14:51:24 <mizmo> #action mizmo to start creating flock ticket tag and going thru demo setting up tickets to support it 14:51:44 <mizmo> we should maybe also have an interns tag for things we think the interns could work on? 14:52:22 <pingou> mizmo: we maybe want to break down some tickets at one point, some of the tickets atm sounds like brainstorming in progress and less 'tasks/issues to do/fix' 14:52:38 <sayan> pingou: you need to add as mizmo as chair 14:52:41 <mizmo> pingou, well some of the tickets are really UI specs, not development tasks 14:52:54 <pingou> #chair sayan mizmo devyani7 14:52:54 <zodbot> Current chairs: devyani7 mizmo pingou sayan 14:53:06 <mizmo> if it has a 'ui-spec' tag then its more a design thing 14:53:13 <pingou> ok 14:54:25 <mizmo> sorry if it clutters everything up :( 14:54:31 <pingou> no worries :) 14:55:01 <pingou> maybe we could use the ticket dependency here 14:55:18 <pingou> create 'tasks' and link them to design tickets 14:55:31 <pingou> anyway, just an idea 14:55:31 <mizmo> https://pagure.io/fedora-hubs/issues?tags=!ui%20spec hehe not quite so many 14:55:38 <mizmo> oh thats a good idea! 14:55:57 <mizmo> the design idea would depend on the tasks? 14:56:11 <pingou> or the other way around, not sure what makes most sense 14:56:28 <mizmo> the design being the parent makes more sense maybe 14:56:37 <sayan> tasks related to design idea 14:57:04 <mizmo> #action mizmo to start creating flock ticket tag and going thru demo setting up tickets to support it 14:57:12 <pingou> thanks mizmo 14:57:17 <mizmo> #info link tasks related to design ideas to the design tickets 14:58:19 <mizmo> anything else? 14:58:29 <mizmo> do you guys feel like you know what you should be working on 14:58:30 <pingou> not from me today 14:59:15 <sayan> I will be working on waartaa, learnt ReactJS over the last weekend and started laying out the project 14:59:25 <mizmo> cool 14:59:39 <sayan> https://github.com/waartaa/waartaa/tree/react 14:59:43 <sayan> #link https://github.com/waartaa/waartaa/tree/react 14:59:55 <mizmo> sayan, so should maybe IRC widgets for the hubs be a part of the flock level 1 list of items? 15:00:14 <sayan> mizmo: yes 15:00:21 * mizmo adds to list 15:00:35 <mizmo> sayan, what about pm'ing people from their profile? doable? 15:00:43 * devyani7 is reading about conglomerators and was working on getting fedora bootstrapped badges :P 15:01:07 <devyani7> #action devyani7 needs to sync her blog with fedora planet 15:01:23 <sayan> mizmo: I guess that's would be tough to complete 15:02:37 <pingou> devyani7: 15:02:39 <pingou> +1 15:02:47 <pingou> devyani7: let us know if you need help w/ that 15:02:47 <devyani7> :) 15:03:13 <fedmsg-hubs> pagure.issue.comment.added -- pingou commented on ticket fedora-hubs#127: "use image sprites technique for badges" https://pagure.io/fedora-hubs/issue/127#comment-2464 15:03:15 <devyani7> pingou: sure thing. one test tomorrow. so will do tomorrow afternoon. :) 15:03:21 <fedmsg-hubs> pagure.issue.edit -- pingou set the status of ticket fedora-hubs#127 to: Fixed https://pagure.io/fedora-hubs/issue/127 15:03:40 <pingou> ok I've to go to another meeting 15:03:55 <devyani7> thanks pingou :) 15:04:06 <pingou> #endmeeting