12:00:29 #startmeeting Gluster Community Meetings 12:00:29 Meeting started Web Feb 3 18:00:29 2016 UTC. The chair is kshlm. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:00:29 The meeting name has been set to 'gluster_community' 17:30:46 Good afternoon everyone! 17:30:48 *** bluenemo (~bluenemo@unaffiliated/bluenemo) has joined #gluster- meeting 17:31:14 #topic Roll call 17:31:21 * obnox waves 17:31:45 * ndevos _o/ 17:31:50 *** gem (~gem@106.51.133.241) has joined #gluster-meeting 17:31:59 The meeting agenda is at https://public.pad.fsfe.org/p/ gluster-community-meetings as always: 17:32:08 * amye is here 17:32:13 niels says I should respond to rollcall 17:32:22 * jiffin is here 17:32:26 Hello 17:32:29 * msvbhat is here 17:32:31 * Humble is here 17:32:38 * overclk is here 17:32:41 *** sakshi (sabansal@nat/redhat/x-kjxwjbqdoohgldzf) Quit (Quit: Leaving) 17:32:44 * skoduri is here 17:32:54 Okay. Let's start. 17:33:11 #topic AIs from last week 17:33:20 #topic  ndevos to send out a reminder to the maintainers about more actively enforcing backports of bugfixes 17:33:38 sorry, I'll try next week again 17:33:57 Okay. 17:34:01 #action  ndevos to send out a reminder to the maintainers about more actively enforcing backports of bugfixes 17:34:15 #topic kshlm & csim to set up faux/pseudo user email for gerrit, bugzilla, github 17:34:36 Still on this. 17:34:43 *** anil (ashah@nat/redhat/x-jziegnlazfzmbcxj) Quit (Quit: Leaving) 17:34:45 #action kshlm & csim to set up faux/pseudo user email for gerrit, bugzilla, github 17:35:02 #topic rastar and msvbhat to consolidate and publish testing matrix on gluster:org in two weeks time, amye can help 17:35:17 *** tdasilva (tdasilva@gateway/shell/panicbnc/x-luyjewjbzivsoibn) has joined #gluster-meeting 17:35:24 *** Apeksha (Apeksha@nat/redhat/x-ywvlqbsvpmdttzks) Quit (Ping timeout: 248 seconds) 17:35:26 We have one more week. Haven't done it yet 17:35:32 oh, that is something pranith could give input on too? 17:36:02 can we start a draft for this? 17:36:21 Will try and complete it by 10th Feb 17:36:40 Okay. 17:36:43 got an etherpad where a work-in-progress is getting done? 17:36:49 One more week shouldn't be too much. 17:37:09 #action  rastar and msvbhat to consolidate and publish testing matrix on gluster:org in two weeks time, amye can help 17:37:23 #topic kkeithley to send a mail about using sanity checker tools in the codebase 17:37:33 ndevos: I don;t think we have one. Maybe we should create one 17:37:45 msvbhat: drop the 'maybe' 17:37:54 :) 17:38:13 kkeithley_, Next week? 17:38:19 yeah, sure 17:38:22 Okay. 17:38:44 #action kkeithley to send a mail about using sanity checker tools in the codebase in two weeks: 17:38:55 AIs are done. 17:39:01 Short list this time. 17:39:14 #topic GlusterFS-3.7.7 17:39:29 3.7.7 had some major issues with upgrades. 17:39:40 How soon do we plan 3.7.8? 17:39:49 thats very sad ;-( 17:40:13 we've delayed the 3.7.7 release waaay too long, a quick 3:7.8 should be done, IMHO 17:40:26 pranithk updated the mailing list that he's reverted the offending patches: 17:40:42 Would that be enough for 3.7.8? 17:40:47 the monthly release schedulde for "stable" updates is not really monthly anymore:... and neither "stable"? 17:40:51 (is this a good time to discuss the missing release notes) 17:41:19 yes, release-notes shouldget included in each minor release too:.. 17:41:40 yep.. however most of the recent releases dont have it 17:41:44 re: ndevos's maintainer's post "Gluster-Maintainers Missing release notes for 3:7.7 and 3.6.8 releases?" 17:42:10 I'll add the 3.6.8 release notes. 17:42:16 replies to http://thread.gmane.org/gmane.comp.file- systems:gluster.maintainers/351 are welcome :) 17:42:22 thanks kshlm++ 17:42:27 #action kshlm to add 3.6.8 release-notes 17:42:44 just dont re-do the tagging :) 17:42:56 ndevos, I'll remember that. 17:42:57 and close the 3.7.7 release tracker BZ and make a new one for 3:7.8? 17:43:16 kkeithley_, who's doing that? pranith? 17:43:20 or me? 17:43:35 the person doing the release of that particular version 17:43:48 yes, pranith 17:43:54 we have scripts in https://github.com/gluster/release-tools to help with thta 17:43:57 *that 17:43:58 #action pranithk to close 3.7.7 tracker and open a 3.7.8 tracker: 17:44:08 *** Etzeitet (~Etzeitet@78.158.49.18) has joined #gluster-meeting 17:44:27 it should all be listed on http://gluster.readthedocs.org/ en/latest/Contributors-Guide/GlusterFS-Release-process/ too 17:44:32 Should we fix a date for 3.7.8 btw. 17:44:46 where is pranithk when you need him? 17:44:47   We have an urgent need for that. 17:45:28 Or do we get a new release-manager? 17:45:38 *** csaba (csaba@nat/redhat/x-wneticwsbuadcdap) has joined #gluster- meeting 17:45:39 Any volunteers to do the 3.7.8 quickly? 17:45:40 BTW, same comment for 3.5.8 and 3.6.8 trackers 17:46:13 nm 17:46:49 So we wait for pranith? 17:46:52 praniths mentioning of the patch is in http:// thread:gmane.org/gmane.comp.file-systems.gluster.maintainers/345 17:47:08 nm, just 3.6.8 tracker 17:47:09 but there is no confirmation that he'll do a 3.7.8 with only those changes 17:47:19 #action kshlm to close 3.6.8 tracker. 17:48:01 #action kshlm to ping pranith for 3.7.8 17:48:12 #topic GlusterFS-3.6 17:48:39 *** asriram (~asriram@171.48.29.211) has joined #gluster-meeting 17:48:41 I announced 3.6.8 last week. But I'm yet to complete the other tasks around it: 17:48:53 I'll do them, and I already have AIs for them. 17:49:00 timeline for release? 17:49:31 Later today. 17:49:35 kshlm++ 17:49:37 amye: kshlm's karma is now 2 17:49:38 Definitely later today. 17:49:53 Anything else for 3.6? 17:50:10 rabhat should be able to get back to his maintainership of 3:6. 17:50:20 We should check with him. 17:50:21 ok, sounds good :) 17:51:03 Okay. 17:51:12 #topic GlusterFS-3.5 17:51:19 ndevos, ? 17:51:32 Not much to share here. 17:51:37 some patches are planned for quota, and they should make it in a few days 17:51:52 And a new release follows that? 17:51:58 so 3.5.8 is scheduled on time, aroiund the 10th of feb 17:52:06 ndevos, Cool. 17:52:15 #info 3.5.8 on track for 10th Feb 17:52:19 it's only few fixes, 3.5 is rather quiet 17:52:28 #topic GlusterFS-3.8 17:52:40 and Gluster-4.0 17:52:40 *** lpabon (lpabon@nat/redhat/x-ashbevuguuyovtog) has joined #gluster-meeting 17:53:06 So anyone have any updates here? 17:53:25 I'll Go ahead with GlusterD-2. 17:53:33 seek() is progressing for 3.8 :) 17:54:03 GD2, we've been working on bootstrapping etcd, and gaurav has a pr open: 17:54:51 overclk, DHT2 news? 17:54:57 kshlm, yeh 17:55:04 *** Manikandan (Manikandan@nat/redhat/x-ybypbnndapzsbkxc) Quit (Ping timeout: 250 seconds) 17:55:12 So, nothing much changed from last update on dht2 17:55:57 overclk, Okay. 17:56:11 *** jdarcy (~jdarcy@pool-173-76-100-87.bstnma.fios.verizon.net) has joined #gluster-meeting 17:56:13 probably by next week, shyam and kotresh would put it up in xlators/experimental 17:56:51 kshlm, that's about it. probbaly next week much more updates: 17:57:15 No one is here from NSR. 17:57:24 ? 17:57:29 jdarcy just joined :) 17:57:32 hi jdarcy :) 17:57:33 jdarcy, didn't see you. 17:57:38 Hi! 17:57:44 * obnox waves jdarcy 17:58:08 Hi all.  What's the question about NSR? 17:58:15 Any updates on NSR? 17:58:26 Just a weekly update. 17:58:50 I got the low-level parts (operation replay) of reconciliation working:  Some funky code generation. 17:59:09 funky how? 17:59:11 Avra and I have a whole stack of patches that need to get through review somehow: 17:59:22 amye: Just complicated and weird-looking. 17:59:29 jdarcy: ack 17:59:40 *** baojg (~baojg@107.170.0.159) Quit (Remote host closed the connection) 17:59:42 jdarcy, thank you. 17:59:45 *** hgowtham (hgowtham@nat/redhat/x-yguonlpbhamyzvig) Quit (Quit: Leaving) 17:59:52 #topic Open Floor 18:00:30 #topic Why is the community meeting so silent? 18:00:37 So can we discuss this here? 18:00:47 *** ashiq (ashiq@nat/redhat/x-eziealrvsjthkbfg) Quit (Ping timeout: 264 seconds) 18:00:55 What do we need to get more voices in here? 18:01:00 Would moving times help? 18:01:11 do we have any ideas how we can improve the community contributions from other engineers 18:01:14 *** jiffin1 (Thunderbir@nat/redhat/x-xbnhsoknuembgrdb) has joined #gluster-meeting 18:01:19 kshlm: it would certainly help to get US West coast to rotate times 18:01:24 (engineers includes developers and qa people) 18:01:47 we'd moved to the current timeslot, to get people in India more active: 18:02:01 But that doesn't seem to have worked. 18:02:18 Could we have a trial run in say, March, to move this to some different times? 18:02:25 *** ggarg (ggarg@nat/redhat/x-qancyagbvgmmgcrc) Quit (Ping timeout: 260 seconds) 18:02:44 I'm in for having rotating schedules. 18:03:09 who wants to propose a rotating time? 18:03:11 I will take an AI to propose March rotation on the -devel list 18:03:12 +1 for rotating the times 18:03:32 and move the current time a little earlier for our friends in India? 18:03:55 More aggressively promoting the time/place might help.  For example, a blog post would make it show up in people's RSS feeds: 18:03:56 #action amye to propose a rotating schedule for community meetings: 18:04:03 *** jiffin (Thunderbir@nat/redhat/x-scnxsrpgvqlvqohq) Quit (Ping timeout: 240 seconds) Session Close: Wed Feb 03 18:04:03 2016 Session Start: Wed Feb 03 18:04:04 2016 Session Ident: 18:04:04 I think as long as we keep good notes + AIs, we can make this work: 18:04:04 *** jiffin1 is now known as jiffin Session Close: Wed Feb 03 18:04:04 2016 Session Start: Wed Feb 03 18:04:04 2016 Session Ident: 18:04:08 jdarcy, ack 18:04:40 here is an example of a rotating meeting by OpenStack Nova:  https://wiki:openstack.org/wiki/Meetings/Nova 18:04:55 #url https://wiki.openstack.org/wiki/Meetings/Nova 18:04:56 *** Humble (hchiramm@nat/redhat/x-baulcvjwvtppfajg) Quit (Ping timeout: 240 seconds) 18:05:21 *** Humble (hchiramm@nat/redhat/x-lffswtlhdrgywqta) has joined #gluster-meeting 18:05:35 Rotating schedule coming out in March. We can keep Feb the same: ;) 18:05:50 Other things for open floor? 18:06:00 I was about to ask the same. 18:06:21 who will be hosting the meeting next week? 18:06:36 I can. 18:06:39 actually, we should put that on the weekly open floor bit 18:06:51 thanks kshlm! 18:07:09 *** ashiq (ashiq@nat/redhat/x-xofowsshzyarvant) has joined #gluster- meeting 18:07:10 Release notes - should we update the RTDocs or is what we have good enough? 18:07:35 Did we put up release-notes on rtdocs. 18:07:41 http://gluster.readthedocs.org/en/latest/Contributors-Guide/ GlusterFS-Release-process/ 18:08:18 Or am I confusing things? This release process gets us release notes, yes? 18:08:51 Those are the guides. We actually do have release notes at https://gluster:readthedocs.org/en/latest/release-notes/ 18:08:51 the release notes should be part of the glusterfs repo, they get packaged for different distributions that way 18:08:55 yes, release notes are part of rtd. 18:09:14 Humble: how do we get the release notes synced from the glusterfs repo to rtd? 18:09:16 Are the guides that we have currently suitable or do they need to be revisited? (better question) 18:09:19 Do the notes get populated at rtd automatically? 18:09:49 we have release notes rendered in RTD from glusterdocs repo:. 18:09:54 not from glusterfs  repo.. 18:10:24 we dont have rendering of glusterfs source code doc repo anywhere in RTD: 18:10:26 Humble, So who adds it to the rtd repo. 18:10:27 We should at least update this to note what social media things we aren't putting releases out on: (The LinkedIn group, G+) 18:10:47 its automatic. .as soon as patch is merged in glusterdocs it wil be rendered 18:10:50 in RTD. 18:11:11 http://gluster.readthedocs.org/en/latest/release-notes/ 18:11:12 Humble, but who adds it to the glusterdocs repo? 18:11:22 the release maintainer. 18:11:22 but the release-notes are in the glusterfs repo, not glusterdocs 18:11:44 Humble, then we need to have an additional step in the release-process: 18:11:49 like https://github.com/gluster/glusterfs/tree/release-3.7/ doc/release-notes 18:12:13 Can't rtd be configured somehow to pull the notes from the glusterfs repo? 18:12:39 That would be awesome. Where do we start with that? 18:12:40 we can .. 18:12:44 I always assumed it can, but I have no real clue about it 18:12:58 but we need a different poroject in RTD. 18:12:59 So can we set it up then? 18:13:00 who has the power to take care of that? 18:13:08 it will confuse users .. Isnt it 18:13:23 thats one of the reason for not rendering glusterfs-specs till now:. 18:13:48 right, that needs the same solution 18:13:58 ndevos, either me or Amye can  :) 18:14:22 amye, Humble: who of you can get the #action then? 18:14:23 So until we come up with a solution, release-managers need to send the notes to glusterdocs as well: 18:14:53 Humble, care to add a note in the release process guide. 18:15:15 maybe, but does glusterdocs have different versions? 18:15:39 the docs should have different version, I guess, but release notes can be gathered from any version:.. 18:15:49 kshlm, sure.. will do .. 18:16:01 ndevos, what do you mean by different versions? 18:16:04 ndevos, http://gluster.readthedocs.org/en/latest/release- notes/ 18:16:14 Different versions of the docs ? 18:16:21 u have the index page from there u can navigate 18:16:28 *** aravindavk (aravinda@nat/redhat/x-ercfgghyxaprrpyd) Quit (Ping timeout: 248 seconds) 18:16:33 docs for 3.7 would be different from 3.8, right? new features will not be available in 3:7 18:16:37 They'd be the same in both the glusterfs repo and glusterdocs repo, wouldn't they: 18:16:38 ndevos, from next version onwards we will have a tagging .. 18:16:49 currently only one exist.. 18:17:03 ndevos, but the notes are named with different versions so that should be clear: 18:17:13 ndevos, again the release notes are arranged in a way where you can find the information for a particular release 18:17:18 kshlm, yep 18:17:31 kshlm: yes, for the notes yes, I was just wondering if we need to send a pull request for all branches in glusterdocs 18:17:42 ndevos, Oh. 18:17:45 only master/latest 18:17:49 Humble can answer that. 18:18:00 thats the only branch which is getting rendered. 18:18:21 #action Humble to add a note to https:// gluster:readthedocs.org/en/latest/Contributors-Guide/GlusterFS-Release-process/ about adding release-notes to glusterdocs as well: 18:18:27 thanks :) 18:18:43 Okay. 18:18:55 So any more topics to discuss today? 18:19:13 amye, tigert: once that is in place, can the version on gluster:org pull in that information too? 18:19:36 I think it currently lists 3.5.x as latest release... 18:19:39 ndevos: I think that is separate, that comes from Middleman 18:19:44 Yep, because it's manual. 18:19:56 so, more steps in the release process? :-/ 18:20:05 So add a note in the release process to 'pester amye '.. yes. 18:20:24 We can work on making this less manual in the future. 18:20:27 Humble, please add this too :) 18:20:31 Sorry Humble. :) 18:20:33 amye: I think you can add that to the process page, you can phrase it anyway you like :) 18:20:43 'Please to make an email' :D 18:20:43 amye, whats the plan for media wiki migration  ? :) 18:20:46 or Humble, I dont mind! 18:20:49 *** ashiq (ashiq@nat/redhat/x-xofowsshzyarvant) Quit (Ping timeout: 250 seconds) 18:20:52 amye, np \o/ 18:21:18 Humble: Shaun McC is going to walk us through what he's found as part of the documentation inventory 18:21:22 and we can decide from there. 18:21:31 cool .. thanks for the update amye 18:21:38 we keep finding things from mediawiki that didn't get migrated, and we'll probably want to keep 18:22:27 amye, may be adding an Event Calendar to gluster.org would be a good idea :) 18:22:43 Ack, but please keep the events pad updated if you've submitted talks 18:22:48 things like Vault are coming up 18:22:50 sure.. 18:23:12 I will be checking on the events pad next week for Monthly Newsletter, coming out Feb 12ish 18:23:38 wait, did I not see an email about a calendar for the website just yesterday or so? 18:23:41 Other things that people want highlighted? I will be repurposing the Weekly News https://public:pad.fsfe.org/p/gluster-weekly-news - into monthly 18:24:06 https://www.gluster.org/news/ 18:24:24 amye, do u think updating weekly news in the website is a good idea ? 18:24:26 ndevos, ?? 18:24:55 Humble, that's a separate repo, blog.gluster.org/blog is where we've been updating things 18:25:09 hmm, maybe it was in an email search... http:// thread:gmane.org/gmane.comp.file-systems.gluster.infra/406 18:25:12 ok. 18:25:38 blog.gluster.org/blog isn't linked to from anywhere on gluster:org 18:25:50 I can't seem to find a link. 18:26:12 I thought blog.gluster.org is deprecated? 18:26:25 ndevos, we could revisit the thread... 18:26:35 That's where planet feeds from. The home page should be deprecated, I agree: 18:26:54 ndevos, yeah, the plan was to deprecate blog.gluster.org 18:27:01 Humble: I think we should pick that up, now we have amye on board, and she surely is the right person for it ;-) 18:27:07 blog.gluster.org is the old gluster.org! 18:27:13 amye, there you go :) 18:27:15 We have too many places to update 'news' in. :( 18:27:22 So let's start consolidating. 18:27:31 Right now? 18:27:33 btw, www.gluster.org has breaking news like "Looking for a Gluster Community Manager"      I guess it's good that it doesn't still say the latest release is 3:5.something 18:27:42 kkeithley_, yeah 18:27:45 We can double-check with Shaun about what other communities are doing: 18:28:17 #action amye to start killing various news on the gluster.org properties: 18:28:26 I think we should enable google indexing for both gluster:org and gluster.readthedocs.org . 18:28:42 amye, if we can get some help on that , it would be appreciated :) 18:28:50 #action  amye to start killing various news on the gluster:org properties 18:30:27 Ok, I can also take an AI on google indexing for g.o and g:rtd.org. 18:30:28 amye, also we can consolidate gluster videos in gluster.org :) 18:30:41 amye++ , thanks !! 18:30:47 amye will be consolidating everything. 18:30:52 Anyways. 18:31:00 Who owns the videos? 18:31:11 I think we're done. 18:31:17 Humble: you're also looking into fixing the search on readthedocs? 18:31:29 We've hit the time limit. 18:31:56 I'll end the meeting if we're done. 18:31:59 amye, there are different presentation coming from events like FOSDEM :.etc 18:32:22 we have to filter those and place it 18:32:38 #action Humble will try to fix the search results on RTD 18:32:42 there is no official channel for us in youtube or similar afaik 18:32:48 On Blog.gluster.org is where those links have been coming in. That's what sends out tweets + posts automagically: 18:33:02 Sorry, blog.g.o/blog - (yes, that needs to get resolved too) 18:33:22 kshlm, we can pick this up again. Plenty to do. Thanks for chairing! 18:33:32 Okay. 18:33:39 #endmeeting 18:33:45 thanks kshlm! 18:33:53 thanks .. bye . 18:34:02 *** Saravanakmr (~Saravana@223.227.12.13) has left 18:34:09 Thanks everyone! 18:36:32 *** jdarcy (~jdarcy@pool-173-76-100-87.bstnma.fios.verizon.net) Quit (Remote host closed the connection) 18:37:56 *** kkeithley_ (kkeithle@nat/redhat/x-pepajoftjpovlkzs) has left 18:42:26 *** pppp (prasanth@nat/redhat/x-twlcbaeqscmnmovt) Quit (Ping timeout: 245 seconds) 18:46:20 *** ira_ (~ira@samba/team/ira) has joined #gluster-meeting