15:00:36 <kshlm> #startmeeting Gluster Community Meeting 2017-04-26
15:00:36 <zodbot> Meeting started Wed Apr 26 15:00:36 2017 UTC.  The chair is kshlm. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:36 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:36 <zodbot> The meeting name has been set to 'gluster_community_meeting_2017-04-26'
15:00:43 <kshlm> #topic Roll call
15:00:54 <kshlm> Welcome everyone!
15:01:39 * kkeithley is here
15:01:43 <kshlm> We have no topics of discussion yet. So please add anything you want to discuss into the meeting agenda at https://bit.ly/gluster-community-meetings
15:01:47 <kshlm> Hey kkeithley!
15:01:57 <kkeithley> howzit
15:02:08 <kshlm> Good!
15:02:29 <kshlm> I'll wait for 3 more minutes before continuing.
15:03:02 * amye is here
15:03:35 <kshlm> Hey amye!
15:03:49 <amye> How goes. My attention's split because E_TOO_MANY_MEETINGS
15:06:06 * ndevos here for an other ~25 minutes
15:06:10 <JoeJulian> o/
15:06:32 <kshlm> Hey ndevos JoeJulian !
15:06:37 * shyam is here
15:06:46 <kshlm> We can start now.
15:07:00 <JoeJulian> Sorry, I'm always going to be 5 minutes after. That's when I am sitting on my bus.
15:07:15 <kshlm> Is there anything anybody wants to discuss?
15:07:57 <kshlm> nigelb_, Added a topic about covscan.
15:08:03 <kshlm> nigelb_, Are you here?
15:08:34 <kkeithley> already raised the covscan issue in the maintainers meeting.  I presume people have seen the daily covscan emails
15:08:49 <JoeJulian> +1
15:09:02 <kkeithley> nigelb and misc fixed quite a few issues, got the number down to 850. Now it's up to 857
15:09:22 <kkeithley> nigelb's magic spreadsheet will tell us which ones are the new ones.
15:09:41 <kkeithley> anyway, that's about all I wanted to say on teh topic
15:09:48 <kshlm> That will be helpful.
15:10:22 <kshlm> But when do we get to see it?
15:10:30 <kkeithley> good question ;-)
15:10:37 <kkeithley> soon I hope
15:11:03 <kkeithley> I believe he's going to add a job in jenkins that will do something with it
15:11:13 <kkeithley> need to ping him for more details
15:11:17 <kshlm> Ah good.
15:11:32 <kshlm> I can do that after the meeting.
15:11:53 <kkeithley> but people can look at the covscan results too
15:12:37 <kkeithley> it's a bit hard atm because you have to grind through 850+ issues
15:13:10 <kshlm> I just looked at the text file, it's really hard to parse.
15:13:20 <kkeithley> yeah, don't. Look at the HTML
15:13:56 <JoeJulian> Just need to get major to have it tickle his fancy and he would probably fix them all. :)
15:14:34 <kkeithley> If he fixed half of them I'd buy him a bottle of his favorite adult beverage
15:14:43 <kkeithley> (and expense it)
15:14:48 <JoeJulian> He's owed that just for the snapshot work.
15:14:50 <kshlm> Just curious. The new covscan reports aren't from the community instance of coverity, are they?
15:15:00 <kkeithley> nope
15:15:12 <kshlm> Ah, thought so. That used to run like only once a week.
15:15:23 <kkeithley> covscan runs on a server in our internal lab
15:15:42 <kshlm> I've been sort of away last few weeks. So I've lost lots of context.
15:16:01 <kkeithley> I think we still get the community reports periodically
15:16:07 <ndevos> the community scan has the fancy website that lets you filter things easier, and mark them resolved etc...
15:16:31 <kshlm> Yes. They even highlighted the new issues.
15:16:34 <ndevos> yes, depending on the size of the project, you may run a scan every X days
15:17:01 <ndevos> indeed, that highlighting is very helpful, we have that in the nfs-ganesha project too
15:17:03 <kkeithley> I could run the Coverity Developer Workbench and internally we could do the same thing. Can't run it "outside" because it requires access to the internal license server
15:17:40 <kshlm> I guess nigelb_'s spreadsheet would do the same as well.
15:17:54 <ndevos> sounds like it
15:18:04 <kshlm> Cool.
15:18:41 <kshlm> It's all on nigelb_ for now then.
15:18:59 <kshlm> Anything more to talk about this?
15:19:22 <shyam> I added a qquick update for 3.11
15:19:30 <kshlm> shyam, I was getting to that.
15:19:31 <shyam> Oops (missed thee this)
15:19:40 <kshlm> Let's move on to 3.11
15:19:45 <kshlm> #topic Update on 3.11
15:19:57 <shyam> Very quick update
15:20:12 * kshlm has been behind his 3.11 reponsiblities and is sorry about that.
15:20:21 <shyam> We are at branching point and have identified features that we may backport, so things look good from that perspective
15:20:40 <shyam> Branching will be done tomorrow, so any last minute shouts has to happen now
15:20:50 * kkeithley needs reviews for https://review.gluster.org/16958
15:20:59 * shyam will be nagging a lot more on the lists going forward on 3.11
15:21:00 <kkeithley> or I'm just going to merge it today then
15:21:30 <shyam> Just starred it, so that it appears in the review prio link...
15:21:47 <shyam> Any other reviews people need attention on, shout/mail me.
15:22:15 * shyam is done with 3.11 updates
15:22:16 <kkeithley> I had reviews. lost them due to resubmit after merge conflicts
15:22:23 <kshlm> shyam, Just to be clear, branching will be done tomorrow your time.
15:22:53 <shyam> Yup, Branching 12:00 PM Eastern ;)
15:23:06 <ndevos> hmm, I'm out tomorrow (Kings Day in .nl) and may not be able to review/update changes the last minute
15:23:40 <shyam> Which ones are you looking at? If I have the list we can possibly request others to focus on that...
15:25:09 <ndevos> the one kaleb pointed out, and the SELinux ones
15:26:05 <shyam> ndevos: thanks, starred them
15:26:31 <ndevos> I was hoping to have time for xreaddirp() from skoduri, but that may be more suitable for 3.12 - https://review.gluster.org/15663
15:27:00 <JoeJulian> bummer. That's the one I was looking forward to seeing.
15:27:31 <shyam> ndevos: That has been granted as a backport
15:27:44 <ndevos> shyam: ok, that is an other option
15:27:45 <kkeithley> but or a STM couldn't we put it in 3.11.1?
15:27:54 <shyam> So if it is backported my May 5th then we can get it in
15:27:54 <kkeithley> but _for_ a STM
15:28:12 <shyam> kkeithley: I would say lets keep .z to its scope, bugs !features
15:28:16 <kshlm> kkeithley, shyam is talking about a backport before the .0 release.
15:29:31 <kshlm> I'll call out one last time in the office tomorrow.
15:30:02 <kshlm> But I believe most of the people who should be aware of it are already aware.
15:30:30 <shyam> ^^^ yup I think so too!
15:30:49 <kshlm> Great!
15:31:24 <kshlm> Thanks for your awesome release planning shyam!
15:31:47 <kshlm> Anything else do discuss about 3.11?
15:31:49 <JoeJulian> shyam++
15:31:49 <zodbot> JoeJulian: Karma for shyam changed to 2 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:31:51 <kshlm> Anyone?
15:31:59 <kshlm> shyam++
15:32:02 <shyam> Oh! ummm... thanks, I would still like it if we stuck to our focus areas though ;)
15:32:16 <shyam> anyway different topic for a different day!
15:32:21 <kshlm> Yeah.
15:33:23 <kshlm> I guess that's about 3.11 then.
15:33:37 <kshlm> And also, that's all for todays meeting.
15:34:01 <kshlm> We have no other topics on the agenda.
15:34:14 <kshlm> The action items are all on people not here.
15:34:21 <kshlm> So the floor is open here.
15:34:24 <kkeithley> what's with the low turnout? This time was supposed to make it easier for more people to attend
15:34:35 <major> JoeJulian, what am I fixing?
15:34:41 <major> Besides a boat
15:34:53 <kshlm> kkeithley, I've got no answers to that.
15:35:18 <kkeithley> just finish the snapshot work you've been doing
15:35:32 <amye> Anyone else from BLR office that had a conflict with this time?
15:35:36 <major> Gonna rebuild the top end of this starboard motor.. I just don't trust the previous mechanic...
15:35:36 <shyam> major: Your snapshot work is posted to master? Sorry, I missed that and wanted to see if that is ready for 3.11 (which is being branched in a day)
15:35:41 <JoeJulian> I've got all sorts of questions about morale, but they're all none of my business. :)
15:35:56 <ndevos> amye: lol, if they have a conflict, they would not be in this meeting :)
15:36:03 <amye> Which is why they're not here.
15:36:18 <major> Yah.. been a busy week
15:36:58 <amye> It's only Wednesday too!
15:37:11 <kkeithley> does "posted" mean merged? On master?
15:37:19 <kkeithley> Or it's still sitting in gerrit?
15:37:50 <ndevos> posted != merged
15:37:59 <shyam> ^^^ that
15:38:28 <kkeithley> So not posted[sic] on master. Just posted for review in gerrit
15:38:44 <major> Shyam, I posted it to GitHub.. but.. been on the water for almost a week now.. I need to catch up.
15:38:51 <shyam> kkeithley: ok :) the addition of the branch master was not needed, I agree
15:39:18 <shyam> major: no worries, I was thinking I missed something that maybe getting into the 3.11 release
15:40:28 <major> There is a bug in the btrfs code that is made evident when cloning a snap shot..
15:40:49 <major> But zfs passes all my tests so far
15:41:15 <JoeJulian> Speaking of tests... did you also add those to the codebase?
15:41:30 <JoeJulian> (I'm being lazy and not looking at github)
15:42:09 <major> ... I was working on it.. but.. fixing the testing stuff to support all the fs targets was distracting
15:42:30 <JoeJulian> I'm also going to be a pest about documentation, too.
15:42:50 <major> My current tests are just a stop gap
15:43:21 <major> Hah.. I can't wait till you tell me I write too much documentation.
15:43:48 <shyam> JoeJulian: I would welcome that for the list of 3.11 features documentation as well (i.e being a pest, feels lonely at times ;) )
15:45:13 <JoeJulian> Sorry, shyam, I once was a pest but then releases happened regardless and I became demoralized. Seemed like nobody else cared. I'll happily start pestering again.
15:46:46 <shyam> JoeJulian: I can understand, till critical mass changes to such direction, getting such things done are difficult... Hope I last till that happens and not get demoralized before then!
15:47:30 <JoeJulian> And on that note, I'm arriving at the office and need to bag this computer up. I'll catch up on anything I miss once I'm all plugged back in. ttfn
15:47:41 <kshlm> I hope so too.
15:47:49 <kshlm> Thanks JoeJulian
15:48:06 <kshlm> Thanks major for your updates on your work.
15:48:24 <kshlm> shyam, I'll catchup with you after the meeting (after I've had dinner).
15:48:29 <shyam> kshlm: sure
15:49:11 <kshlm> I'll end this meeting now.
15:49:40 <kshlm> See you in the next meeting on 10th(?) May.
15:49:51 <kshlm> I"ll send out the meeting minutes ASAP.
15:50:04 <shyam> kshlm++
15:50:05 <zodbot> shyam: Karma for kshlm changed to 1 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:50:05 <kshlm> Have a good day everyone.
15:50:06 <shyam> thanks
15:50:11 <kshlm> #endmeeting