18:08:19 <gregdek> #startmeeting ansible-cwg
18:08:19 <zodbot> Meeting started Wed Nov 29 18:08:19 2017 UTC.  The chair is gregdek. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:08:19 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:08:19 <zodbot> The meeting name has been set to 'ansible-cwg'
18:08:22 <gregdek> Hey y'all
18:09:03 <misc> o/
18:11:48 <Pilou> if a behavior is choosen for this one https://github.com/ansible/ansibullbot/issues/787, it should be easy to implement :)
18:12:44 * gregdek looks
18:15:24 <gregdek> Hey jtanner you around?
18:15:34 <jtanner> gregdek: hello, what's up?
18:15:45 <gregdek> Got some time to opine on 787? ^^^
18:16:30 <jtanner> been meaning to work on t hat
18:16:34 <gregdek> Seems like saying "holy moly this PR touches 1500 files, maybe that's not right" is a good thing for ansibot to know.
18:16:36 <jtanner> just didn't have time
18:16:38 <gregdek> LOL
18:16:46 <gregdek> Sounds like Pilou is volunteering ;)
18:17:03 <jtanner> 99% of the time, it's because they've done a merge commit, which the bot already detects and we could use to gate the notifications
18:17:04 <gregdek> If we can agree on a behavior.
18:17:26 <jtanner> i'd say just disable all notifications to maintainers if merge commit detected
18:17:29 <gregdek> jtanner if you can propose the behavior in that issue, maybe that's enough to magically generate a PR :)
18:17:31 <jtanner> that should solve the 80% rule
18:18:02 <gregdek> In fact, I can just cut and paste this into the issue.
18:18:16 <jtanner> commented
18:18:34 <gregdek> Thx dude!
18:18:43 <jtanner> np
18:19:19 <jtanner> i put so much time into the component matching engine over the past month, that i've been trying to take a break from the bot and work on other responsibilities
18:19:28 <gregdek> Makes sense.
18:20:30 <gregdek> Any hot issues anyone wants to jump on?
18:20:40 <jtanner> this might interest you https://github.com/ansible/ansibullbot/issues/820
18:22:28 <gregdek> Oooooh.
18:22:30 <gregdek> That's a great idea.
18:23:07 <gregdek> +1'd it. :)
18:23:25 <jtanner> should be an easy patch
18:34:14 <gregdek> I'm around for the next 1/2hr working on backlog, ping me if needed.
18:35:07 * misc do not have anything to say
18:35:34 <misc> (even if I could sopeak in lenght of the contributer training meetup we did in paris and went not as well as in pycon :p )
18:38:07 <gregdek> Any takeaways for why?
18:39:00 <misc> well, we had a lot of people no showing up, but that's expected (at least in paris), even if that was more than 75% :/
18:39:12 <misc> but I guess that people are busy in the evening
18:39:36 <misc> and 3h is not enough to turn people into contributors unless thay are already working on free software
18:40:01 <misc> we took a few notes but most were for internal orgs (like "we shouldn't trust meetup numbers for food")
18:40:42 <misc> so definitely, it work better when coders are not distracted by "familly", "drinks" or "work", e.g., a event :)
18:43:14 <misc> one take away also is that if youprepare bugs for people to wkr on, you need to classify them by platform, cause folks with a Ubuntu will not look at dnf bugs, etc
18:43:57 <gregdek> Yeah.
18:44:14 <gregdek> Consistent with the kinds of problems I've seen in other such efforts.
18:44:34 <gregdek> One of the strengths of open source is that you have literally the entire world from which to choose from.
18:45:23 <gregdek> But that also means you've got 3000 people out of 7.6 billion who have cracked the code, and they could be anywhere. :)
18:45:41 <gregdek> And it's so easy for us to forget how much we already know.
18:46:19 <misc> yep, that's the silver lining, my ego got boosted :p
18:46:25 <gregdek> Hahahaha
18:46:27 <misc> I wonder if we shouldn't get people come with a bug they want to be fixed, and help them for that
18:46:29 <gregdek> Like you need any. :)
18:46:48 <misc> since that would make sure they have at least entered a bug report, so have a github account, etc
18:46:50 <gregdek> That's a good idea.
18:47:01 <gregdek> Maybe a really good idea.
18:47:04 * gregdek hrms.
18:47:38 <misc> of course, people will then come with obscure python 2.4 bugs on aix
18:48:22 <misc> and I am sure our corporate overlord are gonna be thrilled to see that we are doing some support work :)
18:50:46 <misc> (cause a few folks who turned up were customers)
18:51:41 <misc> another idea that did emerge from the post meetup drink session, I think from Pilou, is that we (him and I) could just take a bug and stream our screen while we fix, to show how we do try to debug, etc
18:52:11 <misc> we were looking to do at least a attempt with the french community, cause that's gonna be easier for us to discuss in french :)
18:53:10 <gregdek> THAT WOULD BE AMAZING
18:53:50 <gregdek> That should be a live-stream meetup.
18:54:17 <gregdek> So one of the things about the outreach mailing list (don't know if you're on it) is that we've now got the majority of active meetup organizers all in one place.
18:54:31 <gregdek> So we could say "hey invite your meetups to this live stream session".
18:54:45 <gregdek> Would you be willing?
18:54:53 <gregdek> Well, if you get that far, lmk. :)
18:55:10 <misc> well, I would rather do a few tests first
18:55:29 <misc> because we tried to fix a bug that did look easy at first, and turn out it wasn't so easy
18:55:42 <misc> so i rather fail in small groups a few time :)
18:56:56 <misc> not to mention various issue, bjn audio got desynced with screensharing, webcam and mic, etc
18:58:12 <misc> but yeah, we will see what can happen and report
19:02:28 <gregdek> OK.
19:02:39 <gregdek> Let us know how it goes. I'm anxious to see if it can be scaled.
19:02:43 <gregdek> #enE- Elbereth
19:02:49 <gregdek> LOL
19:02:59 <gregdek> HEY MY NETHACK MACRO JUST KICKED IN
19:03:09 <gregdek> HAHAHAHAHA
19:03:52 <gregdek> #endmeeting