15:06:45 #startmeeting hubs-devel 15:06:45 Meeting started Tue May 9 15:06:45 2017 UTC. The chair is sayan. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:06:45 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:06:45 The meeting name has been set to 'hubs-devel' 15:06:52 #topic Roll Call 15:06:56 .hello sayanchowdhury 15:06:58 sayan: sayanchowdhury 'Sayan Chowdhury' 15:07:22 abompard: mizmo: meeting time 15:07:34 .hello duffy 15:07:35 mizmo: duffy 'Máirín Duffy' 15:08:35 #chair mizmo 15:08:35 Current chairs: mizmo sayan 15:08:47 #chair abompard 15:08:47 Current chairs: abompard mizmo sayan 15:08:53 #topic IRC Widget 15:09:04 .hello abompard 15:09:13 abompard: abompard 'Aurelien Bompard' 15:10:14 last week I was working on the IRC widget turn on/off feature 15:10:29 https://pagure.io/fedora-hubs/issue/290 15:11:05 here is the mockup for the widget https://pagure.io/fedora-hubs/issue/284 15:11:43 nice! any luck so far? 15:11:46 The basic widget is complete 15:11:52 \o/ 15:12:05 the things that are left is the FAS avatars that I need to see from the list of users online 15:12:22 and "Hide this notification" 15:12:44 cool 15:12:50 mizmo: can you explain what "Hide this notification" mean here -https://pagure.io/fedora-hubs/issue/raw/files/21560aaa4f66e397249bcfadb220822eb3b42867eabd32403933918eefb065b9-irc-empty-state.png 15:13:41 sayan: it would just shade the widget - e.g., if the user doesn't want to enable the irc widget, it lets them hide it 15:14:48 mizmo: so the complete complete irc widget will be gone? 15:14:58 sayan: no it'll just be shaded 15:15:22 sayan: i think only an admin could remove it completely 15:15:34 mizmo: kind of an overlay which would denote it's inactive state 15:15:44 mizmo: yes, that's right, only admin can remove it 15:16:06 sayan: i think you could just show the title bar, and see the arrow pointing up? you could clikc on that to do the same thing, to shade / minimize it. when it's shaded, the arrow will point down (so they could re open it) 15:16:27 ^^ that makes sense 15:17:14 I'll just go an update the ticket 15:17:43 cool! 15:20:20 Also, I started working on this ticket's backend: https://pagure.io/fedora-hubs/issue/283#comment-71771 15:21:08 eek pagure is crawling 15:21:11 did pagure went down? 15:21:12 * mizmo still waiting for it to laod 15:21:18 could be :-/ 15:21:53 Okay, so this ticket is the wizard step for choosing the nickname 15:22:18 ah ok 15:23:14 are you doing it thru matrix? 15:23:40 mizmo: nope 15:24:07 that's what I wanted to discuss, I could not find something to query the irc through the matrix sdk 15:24:23 so I was wondering if I should do raw query to IRC 15:24:41 mizmo: do you know the matrix folks, if we can contact them? 15:24:48 if you can do irc raw, that should be ok (and perhaps more reliable) to do the nickserv registration step 15:25:29 mizmo: I am worried about the abuse, of check availability 15:25:35 they are in the Matrix HQ room on matrix (do you use it?) Matthew is in here this channel too 15:26:04 no, i don't 15:26:32 what is the abuse concern? 15:27:01 mizmo: if we are doing a raw query, the concern is if we are doing too many of them 15:27:13 it could be possible that Freenode blocks us 15:27:35 I really don't know, but I am just taking that as a worst-case scenario 15:27:47 i did talk to the freenode opers about it and showed them mockups 15:27:49 this was a few weeks ago 15:27:54 they didnt seem to think it'd be problematic 15:28:10 but it would be worth talking to them specifically about the abuse concern - i didnt bring that up to them 15:28:10 I am totally +1 on doing raw query 15:28:28 i was more concerned about their 24 hour email verification thing 15:28:37 ah ok 15:28:57 * Matthew[m] waves 15:29:27 you can send raw commands through the matrix->freenode IRC bridge via the admin room 15:30:11 e.g. https://github.com/matrix-org/matrix-appservice-irc/pull/133 15:30:37 i'm not sure why freenode would object to that as abuse 15:30:50 (we currently have 14K odd connections to freenode, so a few raw messages here and there should be not a big deal ;) 15:31:05 plus all messages are obviously raw at some level :) what commands are you doing? a custom auth sequence? 15:31:31 Matthew: we're querying to see what nicks area available for registration - the front end is for walking users through the nick registration process 15:31:37 Matthew[m]: right, no, we would just check if a irc nick name exists 15:32:00 ah, okay - that should be fine 15:32:09 Matthew[m]: can we send the raw commands through the matrix python sdk? 15:32:18 although the raw interface the bridge provides currently doesn't have any way of receiving responses 15:32:21 afaik 15:32:41 you could use its !nick API to try to set your nick until you find one that works, though? 15:33:12 as per https://github.com/matrix-org/matrix-appservice-irc/blob/master/HOWTO.md#changing-nicks 15:33:22 yeah, I can try that 15:33:28 i'm not sure why you'd be doing that via python SDK though (and i'm just stepping into a meeting) 15:33:36 can try to scrollback later though 15:33:39 or come ask about it in #matrix-dev:matrix.org 15:33:43 (or #matrix-dev on FN) 15:33:50 where more folks will be able to help in my absence 15:34:26 Matthew[m]: setting the context, we would be having this interface: https://pagure.io/fedora-hubs/issue/raw/files/84a3001e2fb94a4be30c8520d56933924b09dd25c2501ccb08043cc1a631aeb8-irc-alt-nick-selection-1.png 15:35:26 where the user can check for the availability of the nick, if it's available the user sets it their irc nick 15:38:33 mizmo: I will then check out the possibilities and build 15:38:48 Ok cool 15:39:13 Thanks Matthew! 15:39:18 * sayan joins #matrix-dev channel 15:39:26 thanks Matthew[m] 15:39:37 That's the update from my side 15:40:04 Another thing is hubs-dev.fic.org is moved to a persistent system 15:40:11 I did the setup last week 15:41:16 right now there is some config issues with oidc, so it's been throwing errors :) 15:41:18 will fix them 15:41:32 #topic Feed & Stream Widget 15:41:49 abompard: can you update on the widget? 15:42:07 sayan: yeah 15:42:33 So, last week I got the auto-update working 15:42:35 https://pagure.io/fedora-hubs/issue/346 15:42:49 it required some changes in the backend files too of course 15:42:58 And this morning I just finished the SSE server 15:43:37 it's based on Twisted and sends to web browser the instruction to reload a widget when its content has changed because of a message recieved on the bus 15:43:42 so I'm currently testing all that 15:44:00 It seems to work :-) 15:44:21 Then I'll add some unit tests, and rework the commits to make them understandable 15:44:22 woohoo! 15:44:51 awesome :) 15:45:05 I'd like to briefly discuss this issue: I think we're lacking manpower on the reviewing side 15:45:16 abompard: rework the commits? 15:45:37 sayan: yeah, split them and merge them so the reviewer has something clean to review 15:45:53 abompard: yeah! I scheduled the PR to test this week 15:46:22 Cool, thanks! The thing is, I have a pretty big pile of things to review next... 15:46:30 I am not getting much time to do review 15:46:56 sayan: I totally understand that, that's why I think we need some more people to do reviews 15:47:37 this week it's Infrastructure hackfest on CI, so other folks won't be available either 15:48:18 to give you an idea, my branch is currently 38 commits ahead of devel... 15:48:59 I'll merge more commits than I'll split before pushing, but it probably won't go down much 15:49:14 abompard: in that case, I guess we should ping other folks in #fedora-apps to help us with the review 15:49:28 sayan: yeah, will do. 15:49:45 I'll try to make the PR as readable as I can 15:50:00 but it's about 3 weeks of work 15:50:07 so it can't really be a one-liner :) 15:50:39 abompard: your PRs are quite understandable, given the description you put in, along with the comments :) 15:50:48 sayan: cool :) 15:51:20 abompard: I will move on the open floor then to talk more one this 15:51:24 #topic Open Floor 15:51:25 that's one of the things I learned working on Mailman: if your PR aren't clear, you just won't be reviewed :) 15:51:48 abompard: mizmo: we need to start planning for the Flock 15:51:58 yes 15:51:59 yeh 15:52:17 flock's focus this year is more on working sessions 15:52:22 than presentations 15:52:25 so, it would be good if we start maintaining the hubs-devel instance, update the ansible scripts for deployemnts 15:52:47 so that it's easy to deploy, and quickly review and push PRs 15:53:38 mizmo: yes, we need to start updating the documentation, so that it's easier to get started 15:54:04 for people to build widgets quickly 15:54:26 agreed 15:54:40 we could prepare a "template" to create a widget 15:54:48 abompard wrote the documentation for the Widget, WidgetParameters which is easy to understand 15:55:16 abompard: yes, that's what I was going to say next, on writing a template for a widget 15:55:22 :) 15:55:43 it should be pretty simple since we have a lot of simple widgets to look at 15:56:06 the good thing is also that it doesn't need to be in the hubs source anymore 15:56:22 so people can make their own repos 15:57:46 abompard: mizmo: so we will be doing one big workshop for Hubs? 15:57:59 workshop + hackfest? 15:58:12 maybe a workshop first then a hackfest following so ppl who attended the workshop can work on it? 15:58:53 Okay, that's a good idea 15:59:11 yeah 15:59:17 I was planning on mostly a hackfest and helping during the hackfest itself 16:00:05 In that case, should we start on a mailing list thread on what do we do during the hackfest? 16:00:20 yeh definitely 16:00:30 it's a good thing if there's more than one person helping for the hackfest because people will have questions 16:00:31 workshop could be write your first widget or something like that 16:00:33 or have another meeting to discuss? 16:00:35 I'll be happy to help 16:00:36 during the hackfest we could have people pick up widgets 16:00:45 sort of how we do the badge artwork workshops 16:01:04 let's start a ML thread 16:01:52 mizmo: can you drop the mail to ML? 16:01:57 sure 16:02:18 mizmo: abompard: btw, I will be away for PyCon US from next week 16:02:36 sayan: OK. Say hello to the Mailman team for me please :) 16:02:43 abompard: sure :) 16:02:45 sayan: and to Kushal of course :) 16:03:03 abompard: the Mailman team was here at PyCon Pune too :) 16:03:12 that's right! :) 16:03:36 sweet enjoy sayan, where is it this year 16:03:37 so somebody needs to chair for next two weeks 16:03:47 Portland 16:04:03 i can chair 16:04:04 ah, Portland ) 16:04:05 :) 16:04:18 mizmo: hopefully I can attend next week, but seems like the meeting starts at 7:00 AM Portland time 16:04:30 we could keep it at this time, it'd be easier, if you want 16:04:44 would be 8 (still early in my opinion lol) 16:05:40 This time works for me too 16:05:58 mizmo: I would be doing a 45 hrs journey, and reaching Portland at post-midnight on Tuesday 16:06:06 so I don't know what state I would be in 16:06:10 omg 16:06:23 lol likely exhausted, no mind! 16:06:32 let's do 1400 UTC as planned 16:06:50 (can someone with ops change the topic for me) 16:07:03 sure 16:07:14 its a pain in matrix lol 16:08:31 oops, I cannot go op in this channel :( 16:10:27 !op sayan 16:10:30 grr 16:10:46 do i have ops now? 16:10:50 mizmo: yes 16:10:58 chanserv doesn't tell you 16:10:59 ok 16:11:38 do you have ops now sayan? 16:11:46 mizmo: yes, I have now 16:11:50 thanks 16:12:39 i dont know how to add you permanently, i might not be able to. it says pingou is the owner 16:12:56 should we end the meeding? 16:12:58 meeting? 16:13:23 (I'm eager to see if my dev Feed page updates when you end it ;-) ) 16:13:31 abompard: sure 16:13:37 Ending the meeting in 16:13:39 3. 16:13:41 2. 16:13:43 1 16:13:45 #endmeeting