15:00:45 <sayan> #startmeeting hubs_devel
15:00:45 <zodbot> Meeting started Tue Feb  7 15:00:45 2017 UTC.  The chair is sayan. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:45 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:45 <zodbot> The meeting name has been set to 'hubs_devel'
15:00:54 <sayan> #topic Roll Call
15:00:58 <abompard> .hello abompard
15:00:59 <zodbot> abompard: abompard 'Aurelien Bompard' <aurelien@bompard.org>
15:01:10 <fm-hubs> pagure.issue.comment.added -- duffy commented on ticket pagure#1843: "Can't add an attachment to a pre-existing comment" https://pagure.io/pagure/issue/1843#comment-72078
15:01:13 <sayan> .hello sayanchowdhury
15:01:14 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
15:01:14 <stickster> .hello pfrields
15:01:16 <zodbot> stickster: pfrields 'Paul W. Frields' <stickster@gmail.com>
15:01:21 <shillman> .hello wispfox
15:01:26 <zodbot> shillman: wispfox 'Suzanne Hillman' <wispfox@gmail.com>
15:02:06 <mizmo> .hello duffy
15:02:07 <zodbot> mizmo: duffy 'Máirín Duffy' <fedora@linuxgrrl.com>
15:02:49 <sayan> #chair abompard stickster shillman mizmo
15:02:49 <zodbot> Current chairs: abompard mizmo sayan shillman stickster
15:03:29 <stickster> sayan: anyone else we should ping for here?
15:03:41 <sayan> yes
15:03:51 <sayan> jcline: meeting time
15:04:01 <jcline> .hello jcline
15:04:01 <zodbot> jcline: jcline 'Jeremy Cline' <jeremy@jcline.org>
15:04:15 <jcline> thanks for reminding me :)
15:04:35 <sayan> #chair jcline
15:04:35 <zodbot> Current chairs: abompard jcline mizmo sayan shillman stickster
15:04:48 <sayan> #Action Items from last meeting
15:05:14 <sayan> #topic Action items from last meeting
15:05:43 <sayan> * jcline to ping about FAS3 PR to get review
15:06:39 <jcline> I did indeed ping about FAS3 (https://github.com/fedora-infra/fas/pull/255), and I got a response, although it sounds like Sayan would prefer some (all?) of this stuff in the hubs DB
15:07:29 <jcline> I confess I got wrapped up in Bodhi work last week and have not had a chance to really think about this yet
15:07:38 <sayan> right, I wanted the data to be in hubs like the irc nick and the irc password in hubs db
15:07:58 <sayan> so that we don't need to do an API call everytime we load up the IRC widget
15:08:36 <sayan> anyways once you are logged in to hubs via ircb you don't need the irc password
15:08:38 <jcline> Okay, so should we leave FAS3 as-is and just pre-populate the hubs DB with the irc nick if it's set?
15:08:41 <stickster> #info currently the team is suspending work on FAS3, although that may not be relevant to FAS3 PR any longer
15:09:08 <sayan> jcline: yes
15:09:26 * stickster wonders if it would make sense as an LDAP attribute
15:09:54 * stickster <-- not a developer and should maybe sit down and try not to hurt himself
15:09:56 <jcline> okay
15:10:00 <sayan> jcline: do you have experience with LDAP?
15:10:15 <jcline> Not really
15:10:22 * abompard has worked with LDAP before, if you need info
15:11:00 <mizmo> irc nick is a reasonable LDAP field
15:11:06 <jcline> sayan, as for the password, we could just shovel it over to ircb and not save it?
15:11:42 <mizmo> if we're worried about the time to retrieve the irc nick from a 3rd party server (be it FAS or LDAP or whatnot) and we store IRC nick in local DB, how do we make sure we're not storing multiple different nicks for the user across Fedora systems?
15:11:43 <sayan> so since FAS3 work is getting suspended, we need to find way to make the integrations with the Hubs and FAS work
15:12:34 <sayan> mizmo: the storage I am talking about is to just to make things fast and avoid calls
15:12:39 <jcline> We could get fedmsg updates about nick changes in FAS after we populate?
15:12:46 <sayan> so whenever there is fas edit we get fedmsg messages
15:12:54 <sayan> so we can update based on that
15:12:57 <jcline> \o/
15:13:19 * jcline wasn't sure if there was a fedmsg for that
15:13:48 <sayan> So, last week I was mostly busy with migrating badges from fedorahosted to pagure, fedimg and autocloud
15:13:48 <chawlanikhil24> .hello chawlanikhil24
15:13:50 <zodbot> chawlanikhil24: chawlanikhil24 'Nikhil Chawla' <chawlanikhil24@gmail.com>
15:14:26 <mizmo> sayan: oh okay perfect, thanks for the explanation
15:14:34 <sayan> but I worked with fhackdroid to see setup was working for ircb and waartaa
15:14:54 <sayan> there were couple of issues but I fixed those
15:15:16 <sayan> This is because I would like more people contribute to ircb
15:16:34 <sayan> I have been documentating the project to get more contributions.
15:16:50 <jcline> :)
15:16:55 <sayan> and people able to understand the codebase quickly.
15:17:40 <sayan> But would be a better method to get more contribute, we have a quite of websocket endpoints to be implemented
15:17:51 <sayan> s/quite/quite a lot of/
15:18:21 <sayan> Should I be creating issues for all the endpoints to be implemented?
15:19:02 <chawlanikhil24> yess
15:19:06 <jcline> Seems like it couldn't hurt
15:19:29 <mizmo> sayan: are the endpoints an easy first step for a new contributor?
15:19:39 <mizmo> sayan: if so i'd file them, and then do say a blog tutorial that walks through how to do one
15:19:48 <mizmo> and we can get the word out about needing contrbutors to write them
15:20:02 <mizmo> and point them to the tutorial and issues (will need a tag on them to make them easy to find)
15:20:32 <sayan> mizmo: could be first in the first go as it as asyncio, aiohttp etc
15:20:54 <sayan> but that's something I would like to sort through documentation
15:21:23 <sayan> and since I will be writing a few the other will be on the same lines
15:22:40 <sayan> mizmo: so recently I went ahead and wrote on how fedimg works as 3-series blog post: https://sayanchowdhury.dgplug.org/redesigning-fedimg-part-i/
15:22:42 <mizmo> i think you need some kind of blog callout to really drum up interest from new contributors, im not sure docs alone will do it
15:22:58 <sayan> I am planning to do the same for ircb
15:23:18 <jcline> You could write most of it as documentation and then add a blog that points to the docs
15:23:31 <mizmo> oh great
15:23:32 <mizmo> that wouldbe perfect
15:23:44 <mizmo> yeh exactly, have the blog point to the docs
15:24:00 <mizmo> kind of give an overview / the highlights / steps
15:24:10 <sayan> jcline: right, but documentation would be in detail, maybe a seperate page on architecture and then I can blogpost the same
15:24:17 <sayan> and ask out for contributors
15:24:31 <sayan> becuase the post goes out fedoraplanet
15:24:49 <jcline> Yeah
15:25:15 <jcline> blog posts are good, but documentation is more "lasting" I think
15:26:11 <sayan> mizmo: another thing for the mockups - can we have a helper text for the mockups? like which classes are used?
15:26:49 <mizmo> sayan: we don't have classes for them yet
15:26:51 <sayan> suppose we have a navbar and then we can have a pointer to the navbar saying which classes were used?
15:27:28 <mizmo> sayan: but i dont think having the classes applied to the mockups is really high priority, getting the data to the screen in the right format is key, it's very easy to style afterwards and i can do that work
15:28:55 <sayan> mizmo: ok so the thing is I was testing over the weekend on how to check if nick is registered and stuffs
15:29:46 <sayan> but then for interactions I will be building a basic ui
15:31:13 <mizmo> ok
15:31:41 <jcline> sayan, okay so you're working on the irc widget UI?
15:32:56 <sayan> jcline: the backend also
15:33:25 <sayan> but I would love to build the UI too
15:33:35 <jcline> Okay, I just didn't want to do work you were already doing. I'll restrict myself to the database stuff
15:34:08 <sayan> jcline: Ok, but there won't be much database changes
15:34:41 <mizmo> sayan: i dont know if you noticed but i updated the nick selection mockups to how we discussed https://pagure.io/fedora-hubs/issue/283#comment-71771
15:34:52 <jcline> Just the username right, and updating it automatically?
15:35:03 <sayan> mizmo: yes, I saw that
15:35:15 <sayan> mizmo: looks good to me now :)
15:35:17 <mizmo> sayan: cool do you think it works, being able to visualize it?
15:35:22 <mizmo> okay awesome! :)
15:35:46 <sayan> jcline: yes, so my plan was we dive things for this ticket https://pagure.io/fedora-hubs/issue/283#comment-71771
15:36:08 <sayan> s/dive/divide
15:36:23 <fm-hubs> pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#283: "Create nick wizard for new IRC users / freenode registration" https://pagure.io
15:36:32 <sayan> and abompard working on the settings page
15:36:44 * sayan goes to dig a link for that
15:36:58 <sayan> https://pagure.io/fedora-hubs/issue/310
15:37:05 <sayan> jcline: abompard ^^
15:37:49 <sayan> and we handle database changes according to our need?
15:38:06 <jcline> sayan, okay, I thought #283 was purely UI work and https://pagure.io/fedora-hubs/issue/291 was for backend changes that needed to happen
15:39:53 <sayan> jcline: yes, but the backend work needs to be divided
15:40:20 * a2batic sorry for getting late
15:40:42 <sayan> the thing is a ticket is blocked on another
15:41:01 <abompard> that's a very nice mockup
15:41:37 <sayan> like the irc enabled/disabled has a number of scenarios: https://pagure.io/fedora-hubs/issue/290
15:42:34 <mizmo> abompard: \o/ :)
15:42:58 <jcline> Yeah, I just want to make sure I know what ticket all this stuff is being written down in
15:43:33 <jcline> If we're using the UI ticket to describe/track all the backend work that's okay, but then we should close #291 or something
15:43:41 <fm-hubs> pagure.issue.comment.added -- abompard commented on ticket fedora-hubs#310: "Mockup UI For configuring hubs-wide IRC settings" https://pagure.io/fedora-hubs/issue/310#comment-72083
15:44:18 <sayan> jcline: hmm
15:44:57 <sayan> jcline: okay, let's mockup discussion happen in it's ticket and the backend in the other ticket
15:45:19 <jcline> okay
15:46:27 <sayan> jcline: abompard: should we sit down tommorow and discuss the things we work on? break down issues into smaller tasks and list them in the respective issue?
15:47:47 <abompard> sayan: yeah, let's find a timeslot that works for all of us
15:48:24 <fm-hubs> pagure.issue.comment.added -- duffy commented on ticket fedora-hubs#310: "Mockup UI For configuring hubs-wide IRC settings" https://pagure.io/fedora-hubs/issue/310#comment-72085
15:48:34 <jcline> I'm flexible, around this time tomorrow should be a reasonable time for everyone, right?
15:49:04 <sayan> jcline: is good to have an hour earlier?
15:49:37 <abompard> so 14:00 UTC?
15:49:38 <sayan> abompard: ^^
15:49:40 <jcline> Whenever is best for you all
15:49:50 <abompard> I can make it.
15:49:50 <fm-hubs> pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#310: "Mockup UI For configuring hubs-wide IRC settings" https://pagure.io
15:50:08 <sayan> abompard: yes
15:50:09 <shillman> I may not be able to make an hour earlier, but I'm not sure that I'm vital to the conversation.
15:50:16 <mizmo> i can do the time for this meeting or an hour earlier
15:50:31 <sayan> shillman: no issues
15:50:43 <sayan> mizmo: cool
15:50:56 <fm-hubs> pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#310: "Mockup UI For configuring hubs-wide IRC settings" https://pagure.io
15:51:27 <sayan> the agenda would be basicaaly to go through #290 and #291. I think we can do two in one hour
15:51:52 <jcline> okay
15:52:07 <fm-hubs> pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#310: "Mockup UI For configuring hubs-wide IRC settings" https://pagure.io
15:52:09 <sayan> and break it into smaller tasks and assign it, and also if possible field names
15:52:27 <fm-hubs> pagure.issue.comment.edited -- duffy edited a comment on ticket fedora-hubs#310: "Mockup UI For configuring hubs-wide IRC settings" https://pagure.io
15:53:31 <sayan> #info meeting tomorrow at 1400 UTC to discuss #290 and #291
15:54:50 <sayan> abompard: btw, you are working on implementing the widgets through class right?
15:54:52 * stickster has to run off to prep for another call
15:56:52 <abompard> sayan: yeah, it's ready
15:57:06 <sayan> abompard: oh cool
15:57:11 <abompard> sayan: I've split the commits into understandable chunks
15:57:15 <sayan> abompard++
15:57:15 <zodbot> sayan: Karma for abompard changed to 2 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:57:31 <abompard> so you can read them in order like a (geeky) story
15:57:54 <abompard> it's based on my other pull requests, so I think they should be merged first
15:58:12 <abompard> and there's even documentation :-)
15:58:52 <abompard> but it's a pretty big structural change, so I'd like to emphasize that I'm here to answer any questions you may have on the widgets you're currently working on
15:59:02 <abompard> and how to convert them to the new system
15:59:25 <sayan> abompard: PR #312 and #314?
15:59:27 <abompard> I can even do it, it's pretty easy once you know how things fit together
15:59:40 <abompard> sayan: yes
16:00:33 <sayan> abompard: I will look into them tomorrow
16:00:44 <abompard> cool, thanks. They should be simple
16:00:45 <sayan> moving to Open Floor
16:00:53 <sayan> #topic Open Floor
16:01:27 <abompard> [buzzing sound]... no, no, not the sharks!
16:01:36 <sayan> abompard: I have been applying query_property all my other projects :)
16:01:45 <sayan> cool, ending in
16:01:47 <sayan> 3
16:01:50 <sayan> 2
16:01:52 <sayan> 1
16:01:54 <sayan> #endmeeting