15:05:25 <decause> #startmeeting Fedora Hubs 15:05:25 <zodbot> Meeting started Wed Apr 13 15:05:25 2016 UTC. The chair is decause. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:05:25 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:05:25 <zodbot> The meeting name has been set to 'fedora_hubs' 15:05:39 <decause> #topic Roll Call 15:05:48 <decause> .hello decause 15:05:49 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com> 15:05:53 <devyani7> .hello devyani7 15:05:54 <zodbot> devyani7: devyani7 'Devyani Kota' <devyanikota@gmail.com> 15:07:39 <decause> looks like we're going to have a short meeting today ;) 15:07:58 <devyani7> :P 15:08:14 <mleonova> hey decause 15:08:34 <decause> mleonova: hi there :) 15:08:53 <decause> we're having the hubs check-in now 15:08:56 <mleonova> thought the meeting was the hour before) 15:09:14 <mleonova> hmm.. sadly nothing to check-in. 15:09:35 <mleonova> I'm still trying to find my way around the new team 15:09:38 <decause> it was at 11am last week, but we /could/ move it if it works better for some folks 15:09:42 <decause> mleonova: oh def 15:09:47 <decause> you just started :) 15:09:49 <decause> here 15:09:55 <decause> #topic Check-ins 15:10:05 <decause> hrmm 15:10:11 <decause> #chair devyani7 15:10:11 <zodbot> Current chairs: decause devyani7 15:10:17 <decause> #topic Check Ins 15:10:25 <decause> #topic Check-ins 15:10:28 <decause> odd 15:10:32 <decause> no message? 15:10:42 <decause> maybe it is an older version of zodbot 15:10:45 <sayan> .hello sayanchowdhury 15:10:47 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com> 15:11:13 <decause> welcome back sayan 15:11:24 <decause> #chair sayan 15:11:24 <zodbot> Current chairs: decause devyani7 sayan 15:11:27 <mleonova> .hello mleonova 15:11:28 <zodbot> mleonova: mleonova 'Maria Leonova' <mleonova@redhat.com> 15:11:31 <decause> #chair mleonova 15:11:31 <zodbot> Current chairs: decause devyani7 mleonova sayan 15:12:12 <sayan> decause: hello :) 15:12:13 <decause> I guess I can start with my updates, unless anyone else wants to go first? 15:12:34 <sayan> this is the same meeting right? https://apps.fedoraproject.org/calendar/commops/#m3341 15:13:33 <decause> #topic Check-ins: GSoC 15:13:39 <decause> So 15:14:16 <decause> last week was the meeting for the mentor deadline for requesting slots for internships fro Google Summer of Code 15:14:37 <decause> we have requested slots, which included space for work on Fedora hubs 15:14:50 <decause> it will depend on how many slots we get, on what projects will get work 15:14:54 <mleonova> woohoo! 15:15:07 <decause> but I'm hopefull that we can get at least one hubs intern from GSoC 15:15:23 <decause> #info Slot Request Deadline for GSoC was Monday 4/11 15:15:44 <decause> mentors should be finding out *today* how many slots will be allocated to their projects 15:15:52 <rtnpro> .fas rtnpro 15:15:53 <zodbot> rtnpro: rtnpro 'Ratnadeep Debnath' <rtnpro@gmail.com> 15:15:55 <decause> I have not seen anything in my inbox yet though 15:16:05 <decause> #chair rtnpro 15:16:05 <zodbot> Current chairs: decause devyani7 mleonova rtnpro sayan 15:16:24 <Dimuthu> decause++ 15:16:41 <devyani7> decause: cool ! 15:16:53 <Dimuthu> hi guys :) 15:17:00 <decause> GSoC has been my focus (outside of Fedora budget) for the past week, and students will find out soon whether or not they were selected 15:17:14 <sayan> cool! 15:17:16 <decause> #info GSoC Student notification will happen on April 22nd 15:18:09 <decause> it is my intention to hold a regular "standing meeting" for *all* the GSoC interns, Outreachy Interns, and Red Hat interns during this cycle once we have everyone hired and on the books 15:18:37 <decause> hopefully we can find a time that works for everyone 15:18:47 <sayan> decause++ 15:18:55 <devyani7> decause++ 15:18:55 <zodbot> devyani7: Karma for decause changed to 39 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:19:03 <Dimuthu> decause++ 15:19:03 <decause> ok, I think that about sums up my GSoC updates 15:19:20 <decause> anyone else have updates they'd like to share? 15:19:24 <devyani7> decause: so, last week I started working on a feature to get the mailing list posts of a similar thread together, 15:19:46 <decause> #topic Check-in: devyani7 15:20:01 <devyani7> so far am still tweaking the feed widget. it still needs work^^ 15:20:11 <decause> devyani7: have you seen the work that threebean was doing with the 'conglomerators' 15:20:14 <decause> ? 15:20:31 * decause thinks that is what he was calling it 15:20:39 <devyani7> decause: yes 15:20:49 <decause> devyani7: excellent :) 15:21:05 <decause> that is going to help significantly with making the feed readable 15:21:10 <devyani7> should finish it soon :) 15:21:25 <devyani7> also, simultaneously, iwas working on issue #17 15:21:37 <devyani7> https://pagure.io/fedora-hubs/issue/17^^ 15:21:58 <decause> threebean and I discussed how these filters require some intense thinking, but once they are written in the fedmsg-meta areas, they can be used in other places besides hubs also :) 15:22:17 <devyani7> decause: true that :) 15:22:20 <decause> #link https://pagure.io/fedora-hubs/issue/17 15:23:06 <devyani7> ya, so issue #17, I worked on an intial PR #72 15:23:15 <devyani7> but we still need work on the tahrir side. 15:23:50 <decause> nod nod 15:23:52 <devyani7> working on writing the API, still a long way :/ 15:24:29 <devyani7> will get these two done by next week 15:24:35 <devyani7> hopefully^^ 15:24:39 <devyani7> :) 15:25:05 <sayan> devyani7: have you pushed the intial changes for the api somewhere? 15:25:24 <devyani7> sayan: nope, its still work in progress 15:25:48 <sayan> devyani7: cool, do ping me if you need help :) 15:25:55 <devyani7> :( things are not clear for me yet. 15:26:08 <devyani7> sure thing, thankyou sayan :) 15:26:10 <decause> devyani7: def be sure to release early and often, it helps to get input from other mentors 15:27:04 <devyani7> decause: duly noted :) 15:27:18 <decause> :) 15:27:29 <decause> other updates? Be sure to change the topic if you have any 15:27:38 <sayan> decause++, making small commits help easily rollback if something goes wrong 15:27:39 <Dimuthu> decause: currently working on https://pagure.io/fedora-hubs/issue/33 and developing other meeting widgets 15:28:32 <sayan> decause: I have nothing the check-in but rtnpro and I need to discuss on the IRC widget 15:28:53 <decause> nod nod 15:29:03 <devyani7> sayan++ rtnpro++ :) 15:29:03 <zodbot> devyani7: Karma for sayanchowdhury changed to 5 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:29:06 <zodbot> devyani7: Karma for rtnpro changed to 4 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:29:32 <sayan> so you might be knowing that we plan to integrate ircb with the IRC widget 15:29:32 <Dimuthu> faced a python problem. i asked from threebean about it. still no reply :( 15:30:00 <rtnpro> sayan, not just ircb, but waartaa 15:30:14 <rtnpro> sayan, ircb is a component of waartaa 15:30:25 <sayan> rtnpro: right 15:30:43 <sayan> rtnpro: do you want to go aheadwith the dicussion you and threebean had? 15:31:10 <rtnpro> I was going through https://fedoraproject.org/wiki/Fedora_Hubs, specially the, IRC integration part 15:31:32 <rtnpro> it says that "Fedora Project policy is that we personally don't retain IRC logs unless the user is explicitly notified of this collection (such as during a meeting conducted with Zodbot). " 15:32:20 <rtnpro> however, the kind of mockups we have, where we show user mentions on a IRC channel and then allow the user to jump to the conversation he was mentioned in 15:32:37 <rtnpro> these things are not possible if we do not store logs 15:33:07 <rtnpro> however, if we want to limit our scope to only mentions in meetings, then that's OK 15:33:18 <rtnpro> however, it's not a user friendly use case 15:33:36 <rtnpro> decause, sayan, anyone, any comment? 15:35:20 <rtnpro> sayan, ^^ 15:35:53 <sayan> rtnpro: nothing to comment here 15:36:27 <rtnpro> so, this needs to be discussed with the technical stakeholders of the project 15:37:01 <rtnpro> going ahead... 15:37:02 * decause is also talking in FAmSCo, apologies for delay 15:37:48 <decause> rtnpro: I am very aware of this issue yes 15:38:20 <rtnpro> coming to the IRC widget, we plan to implement it as an iframe in fedora hubs page, pointing to Fedora's waartaa instance 15:38:21 <decause> I think that it's possible that we can meet some kind of middle-ground, such as mizmo suggested having only 10 lines of scrollback in the widget 15:38:31 <decause> or 15:38:36 <rtnpro> yeah 15:38:48 <decause> we can make a policy proposal that some channels agree to be publicly logged 15:39:04 <rtnpro> yeah 15:39:19 <decause> I think that having a #fedora-room-hubs variant will divide communication 15:39:57 <decause> rtnpro: I think there may be potential for zodbot here to 'replay/relay' messages between channels also, if we have to go that route 15:40:19 <decause> I would like to see a few scenarios of how this would work, and then we can bring it to the community 15:40:31 <mizmo_______> i dont fully understand people's concerns about logging etiher 15:40:43 <decause> I think that this real-time communication potential of Hubs is very timely, and something we need, and will provide *much* value to the project 15:40:44 * mizmo_______ sorry for the nick, i'm ready to dump this irc client 15:40:55 <decause> mizmo_______: :) 15:41:32 <rtnpro> mizmo, decause, as long as the logs are not public, I think we are good to store logs 15:41:48 <mizmo_______> rtnpro: what do people define as public though 15:42:11 <rtnpro> we can implement a policy layer, only logged in users can see the logs, for channels they are part of 15:42:21 <mizmo_______> i mean, my thoughts are this - 15:42:28 <mizmo_______> every channel you're in basically is logged 15:42:29 <rtnpro> similar to irccloud, etc 15:42:33 <mizmo_______> as many popular IRC clients log by default 15:42:40 <mizmo_______> so somewhere, a transcript of what you say is somewhere 15:42:41 <rtnpro> yes 15:42:45 <mizmo_______> and if people are using hubs as an irc client 15:43:27 <mizmo_______> if they opt into logging 15:43:30 <mizmo_______> how is it diff than a desktop client 15:43:41 <mizmo_______> it could be a per user option maybe 15:43:43 <rtnpro> no difference 15:43:45 <mizmo_______> on by default 15:44:14 <mizmo_______> i just hope the folks with the privacy concerns feel that way too 15:45:21 <rtnpro> the fedora hubs irc client usage is the same as idling on IRC channels using znc like stuff 15:45:33 <rtnpro> no one stops you from doing that 15:45:34 <mizmo> ugh am i still here 15:45:36 <mizmo> there was a netsplit 15:46:02 * rtnpro had said "the fedora hubs irc client usage is the same as idling on IRC channels using znc like stuff" 15:46:14 <mizmo> okay cool 15:46:28 <mizmo> are there particular people who are very concerned about the privacy issues? could we run it by them? 15:47:26 <rtnpro> mizmo, good idea, only they can tell what the concerns exactly are 15:47:40 <mizmo> we could do a blog post maybe outlining our current plan and ask for feedback 15:47:51 <rtnpro> mizmo++ 15:47:51 <zodbot> rtnpro: Karma for duffy changed to 16 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:48:07 <mizmo> rtnpro: would you be willing to do the blog post? or would you rather someone else write it 15:48:42 <rtnpro> mizmo, I can prepare the draft, then someone needs to polish it up for publication 15:48:49 <rtnpro> mizmo, will that work 15:49:02 <mizmo> rtnpro: cool i'd be happy to polish up for you 15:49:11 <rtnpro> mizmo, awesome :) 15:49:16 <mizmo> decause: ^^ would rtnpro's blog work? or would it be better for community blog? 15:50:15 <rtnpro> let's move to the implementation of the IRC chat widget 15:50:31 <mizmo> sure 15:50:55 <rtnpro> the realtime nature of the chat widget requires us to use a mature JS framework like react, angular2 15:51:16 <rtnpro> however, AFAIK, fedora-hubs may not be that JS heavy 15:51:31 <mizmo> well threebean talked about using react or angular actually 15:51:42 <rtnpro> so, I think it'd be better to decouple the development of the IRC widget and delegate it to waartaa 15:51:54 <sayan> rtnpro: threebean planned to move the frontend to a JS framework soon 15:52:08 <rtnpro> cool 15:52:21 <mizmo> oh not react, backbone.js is what he mentioned 15:52:26 <mizmo> "Furthermore, we should likely use something like angular or backbone.js to manage the data synchronization with those client-side templates." 15:52:32 <rtnpro> mizmo, yeah 15:52:46 * decause is in 3 meetings... sorry folks 15:52:55 <decause> FAMSCO is running way late 15:53:01 <decause> and taking lots of my bandwidth 15:53:27 <rtnpro> I think it'd be best to load the chat widget as an iframe in hubs page, similar to how Google hangout is loaded in Gmail and other pages 15:53:33 <decause> rtnpro: start with your blog first, and we can then do a "pointer" post on the commblog if we need to later 15:53:46 <rtnpro> this will give both the projects to chose the best framework for the job 15:53:57 <rtnpro> decause, ok 15:54:19 <mizmo> rtnpro: makes sense to me 15:54:27 <rtnpro> awesome :) 15:54:47 <rtnpro> sayan, did we miss any point that needs discussion? 15:55:16 <sayan> rtnpro: no, I think all the things were covered 15:55:23 <rtnpro> cool 15:56:51 <rtnpro> <eof> from me unless anyone has any question 15:57:16 <decause> rtnpro: there was a proposed gsoc project for doing this work 15:57:22 <decause> or, helping with it 15:57:37 <decause> the student who proposed it listed you two as mentors 15:57:50 <decause> rtnpro and sayan, IIRC 15:58:05 <sayan> decause: AFAIK dhritishikhar planned to work on this on GSoC 15:58:11 <rtnpro> decause, there's lot that needs to be done, and student did not have experience with the technologies we're using 15:58:35 <mizmo> oh, we also have two dev interns thru the RH program coming in to help with hubs, as well as a ux intern for this summer 15:59:23 <decause> mizmo: yes, they are working into my calculations 15:59:48 <sayan> decause, mizmo: our plan is to make the IRC widget working before Flock this year 16:00:12 <mizmo> oh god that would be so sweet 16:00:32 <decause> mizmo: I was planning on running a regular standing meeting for *all* interns (gsoc/outreachy/rht) 16:00:38 <mizmo> anything i can do to help? i will go thru the IRC mockup tickets and see if theres anything needing to be done 16:01:37 <sayan> mizmo: nothing right now, but surely ping in need 16:02:00 <sayan> to make sure everything going in the right direction 16:02:29 * Dimuthu searching for a help 16:02:57 <decause> ok, just timechecking we're at the top of he hour 16:03:10 <decause> not that any other meetings are scheduled here in #fedora-hubs 16:03:36 <sayan> Dimuthu: let's take it after the meeting? let see if I can help :) 16:03:54 <Dimuthu> sayan : ok :) 16:04:42 <mizmo> stuff i'm planning real quick 16:04:49 <mizmo> im going to go thru the mockups and clean up the dir a bit (the git dir) 16:05:00 <mizmo> i am thinking about transferring the mockupsf rom github to pagure 16:05:09 <mizmo> im also going to start a ux style guide 16:05:25 <mizmo> and ive been working through tickets with the tag 'needsmockup' 16:05:32 <mizmo> so if you need any mockups, add that tag :) 16:05:36 <mizmo> </eom> 16:06:10 <devyani7> mizmo: cool :) 16:09:29 <decause> mizmo++ 16:09:36 * decause is about to be done with famsco meeting 16:09:39 <decause> after 2 hours 16:11:14 <decause> next week will be less hectic on my end (budget week is crazy for a decause) but I'm glad to see the progress happening on tickets, and the potential we've got for interns 16:11:33 <decause> I think a big thing that we can do to prepare for the arrival is to do some 'grooming' of the tickets 16:11:54 <decause> and adding of any adddtional tickets that are on the drawing board, but could be written down as issues 16:12:22 <decause> also, any updates to the install docs/instructions 16:13:40 <decause> we're 15 over almost, so I'd like to end the meeting in 2 mins unless anyone has any last minute biz 16:13:45 <decause> #topic Open Floor 16:15:47 <decause> ok, then let's close 16:15:50 <decause> thanks all for being here :) 16:15:58 <decause> exciting times for FedoraHubs :) 16:16:01 <decause> #endmeeting