11:59:58 <atinm> #startmeeting
11:59:59 <zodbot> Meeting started Wed Aug 12 11:59:58 2015 UTC.  The chair is atinm. Information about MeetBot at http://wiki.debian.org/MeetBot.
11:59:59 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:00:38 <atinm> #info agenda is available @ https://public.pad.fsfe.org/p/gluster-community-meetings
12:01:11 <atinm> Roll Call
12:01:23 <atinm> who all do we have here today?
12:01:26 <hchiramm> #topic roll call
12:01:29 * hchiramm is in
12:01:36 * kkeithley is here
12:01:37 * poornimag is here
12:01:41 * msvbhat is here
12:02:04 * tigert is here
12:02:05 <atinm> few more names?
12:02:17 <hchiramm> ........
12:02:46 <atinm> We will wait for couple of minutes and then move on
12:02:50 * raghu is here
12:04:09 <hchiramm> atinm, please proceed :)
12:04:39 <atinm> hchiramm, yes
12:04:47 <atinm> #topic action items from last week
12:05:16 <atinm> tigert to summarize options for integrating a calendar on the website, call for feedback
12:05:21 <tigert> So I looked into the calendar stuff, and mailed gluster-infra asking for feedback on what functionality is needed, I also posted a few possible ideas.
12:05:22 <atinm> tigert, any updates on this?
12:05:27 <tigert> http://www.gluster.org/pipermail/gluster-infra/2015-August/001338.html
12:05:36 <hchiramm> tigert++
12:05:44 <tigert> not much replies yet (since it was pretty last minute to this meeting, sorry about that)
12:05:56 <atinm> #info tigert has asked for feedback about integrating gluster calendar @ http://www.gluster.org/pipermail/gluster-infra/2015-August/001338.html
12:06:08 <tigert> but lets wait a bit for more feedback
12:06:29 <atinm> Yeah, probably send a gentle reminder to that thread after few days?
12:07:04 * kkeithley thought it looked fine. I had one suggestion, which I sent in a reply
12:07:34 <tigert> yeah
12:07:45 <tigert> kkeithley: yeah thanks for that one
12:07:50 <tigert> it was a good one too
12:08:06 <atinm> #action tigert to send a reminder mail to ask for feedback for gluster calendar integration
12:08:12 <atinm> Moving on
12:08:12 <tigert> we are also pondering within our osas team about this since a community events calendar is something many projects need
12:08:15 <tigert> but lets see
12:08:24 <atinm> based on the feed back from the mail sent by raghu , gluster.org need to be updated
12:08:54 <atinm> raghu, I believe most of the members are ok with it, so do you plan to update the site with the release date guidelines?
12:09:01 <hchiramm> https://github.com/gluster/glusterweb/blob/master/source/community/release-schedule.md
12:09:03 * overclk is late to the meeting
12:09:11 <hchiramm> tigert++ has created a sample page in github
12:09:31 <hchiramm> raghu, if u can fill the content in it , tigert can help us to push that page in gluster.org
12:09:51 <atinm> #info release schedule details @ https://github.com/gluster/glusterweb/blob/master/source/community/release-schedule.md
12:10:19 <atinm> raghu, are you there?
12:10:45 <raghu> atinm: sure. I will do fill the contents
12:10:51 <atinm> raghu, ok
12:11:05 <hchiramm> raghu++ thanks !
12:11:24 <atinm> #action raghu to fill in the contents for release schedule and ask tigert to push the page in gluster.org
12:11:40 <atinm> Next action was on rtalur to setup a new project gerrit specs in review.gluster.org
12:11:48 <atinm> seems like rtalur is not here
12:11:54 <atinm> anyone has any update on this?
12:12:19 * anoopcs is here
12:12:33 <atinm> moving this item for next week
12:12:40 <atinm> #action rtalur to setup a new project gerrit specs in review.gluster.org
12:13:09 <atinm> next item is on hagarth and kshlmto do 3.7.3 announcement on the gluster blog and social media
12:13:12 <hchiramm> atinm,
12:13:18 <hchiramm> http://review.gluster.org/#/admin/projects/glusterfs-specs I have setup the project
12:13:42 <hchiramm> have given acls to glusterfs maintainers.
12:13:57 <atinm> hchiramm, ok
12:14:03 <msvbhat> atinm: I have added 3.7.3 in gluster news from the week
12:14:05 <hchiramm> however we will cross check and announce to the gluster infra with the details
12:14:40 <atinm> hchiramm, ok, lets continue with this item for next week
12:14:44 <hchiramm> sure..
12:14:53 <atinm> msvbhat, is it been integrated with planet gluster?
12:15:22 <msvbhat> atinm: Not yet,
12:15:33 <atinm> msvbhat, we would need to do that
12:15:41 <msvbhat> atinm: Someone can help with syndicating? I haven't published it yet
12:15:59 <msvbhat> atinm: Yes, I will ask someone for help.
12:15:59 <atinm> msvbhat, ndevos, tigert  can help you on this
12:16:22 <msvbhat> tigert: I will ping you after the meeting for some help
12:16:29 <atinm> #action msvbhat to  do 3.7.3 announcement on the gluster blog and social media
12:16:39 <atinm> Moving on
12:16:46 <atinm> pranithk to write up a post announcing EC's production readiness.
12:17:15 <atinm> Any updates from others since Pranith is not around?
12:17:21 <hchiramm> atinm, I havent noticed
12:17:28 * atinm echoes the same
12:17:49 <atinm> #action pranithk to write up a post announcing EC's production readiness
12:18:04 <atinm> Next on the plate is rtalur to send update mailing list with a DiSTAF how-to and start discussion on enhancements to DiSTAF
12:18:17 <atinm> msvbhat, do you have any update on this on rtalur's absence?
12:18:36 <msvbhat> atinm: I will send a mail
12:19:13 <atinm> #action msvbhat/rtalur to send update mailing list with a DiSTAF how-to and start discussion on enhancements to DiSTAF.
12:19:17 <msvbhat> There are some update about it and some feedback
12:19:44 <atinm> msvbhat, ok, you can capture all those details in your mail
12:19:48 <atinm> Moving on
12:19:51 <atinm> kshlm  to test the new jenkins slave in ci.gluster.org - did some tests, but  misc did most of the testing
12:20:02 <atinm> kshlm is not around though
12:20:14 <atinm> Not sure whether its been done
12:20:21 <atinm> anyone on this?
12:20:44 <hchiramm> no idea.
12:21:01 <atinm> #action kshlm  to test the new jenkins slave in ci.gluster.org
12:21:14 <atinm> Next items is shyam will announce DHT2 related work efforts and repository for Gl4.0 this week
12:21:19 <atinm> this is done
12:22:00 <atinm> #info Shyam has announced about DHT2 @ http://www.gluster.org/pipermail/gluster-devel/2015-August/046369.html
12:22:32 <atinm> Last one is on rafi about adding a new topic for GlusterFS 3.8
12:22:42 <atinm> and its done
12:22:45 <rafi> atinm: done
12:22:54 <atinm> So we are done with the action items
12:23:05 <atinm> #topic GlusterFS 3.7
12:23:48 <atinm> anything needs to be discussed?
12:24:05 <atinm> since kshlm is not around I feel free to skip it
12:24:36 <atinm> anyone?
12:25:06 <atinm> I take it as "No"
12:25:20 <atinm> #topic GlusterFS 3.6
12:25:56 <atinm> raghu, do you have anything to update here?
12:26:24 <raghu> Not much
12:26:31 <raghu> I will be making the release next week
12:26:39 <raghu> as per the schedule that we decided.
12:26:51 <atinm> #info Gluster 3.6 is getting released in next week
12:26:58 <raghu> more backports are welcome
12:27:04 <atinm> raghu, :)
12:27:17 <raghu> I have some patches in the pipeline to be merged.
12:27:26 <raghu> I am going to do them by couple of days.
12:27:45 <raghu> but I would prefer if there are few more backports
12:28:02 <atinm> #info raghu seeks for more backports for next 3.6 release
12:28:07 <atinm> allright
12:28:12 <atinm> anything else on this front?
12:28:20 <raghu> atinm: nope
12:28:22 <atinm> or else I will move to next topic
12:28:32 <atinm> #topic GlusterFS 3.5
12:28:37 <atinm> ndevos, are you around?
12:28:49 <atinm> ayone has to say about 3.5?
12:29:05 <kkeithley> probably not around
12:29:16 <kkeithley> Lost in Pune
12:29:23 <atinm> kkeithley, :)
12:29:30 <atinm> Ok, moving on
12:29:38 <atinm> #topic Glusterfs 3.8
12:29:50 <poornimag> For 3.5, i think is mainly blocked on one of libgfapi backport, i will backport it next week
12:30:27 <atinm> #action poornimag to backport one of the libgfapi related changes into 3.5
12:30:41 <atinm> Who wants to talk about 3.8
12:31:23 <atinm> #info More information about what we target in for 3.8 can be found @ http://www.gluster.org/pipermail/gluster-users/2015-July/022722.html
12:31:38 <atinm> 5
12:31:39 <atinm> 4
12:31:40 <atinm> 3
12:31:41 <atinm> 2
12:31:42 <atinm> 1
12:31:45 <atinm> 0
12:31:54 <atinm> kkeithley, just using your trick ;)
12:32:07 <atinm> #topic GlusterFS 4.0
12:32:08 <kkeithley> it's a good trick, eh? ;-)
12:32:18 <atinm> kkeithley, yes :)
12:32:49 <atinm> #info Gluster 4.0 Tracker : https://bugzilla.redhat.com/showdependencytree.cgi?id=glusterfs-4.0
12:33:50 <atinm> #info GlusterD 2.0 high level plan for next 2-3 months is out now @ http://www.gluster.org/pipermail/gluster-devel/2015-August/046310.html
12:34:48 <atinm> This talks about what we are exploring now, folks are evaluating different RPC techniques, stabilizing the skeleton and rewritting the volfile generation part
12:35:10 <atinm> We will be sharing the code repo once the skeleton is stable and ready to use
12:35:50 <atinm> As discussed as part of last week's action items, Shyam has also shared the details about DHT2
12:36:00 <atinm> Anything else on 4.0?
12:36:25 * atinm feels its one way traffic now
12:36:56 <atinm> Moving on
12:37:02 <atinm> the last topic
12:37:10 <atinm> #topic Open Floor
12:37:57 <atinm> #info     Weekly reminder to announce Gluster attendance of events: https://public.pad.fsfe.org/p/gluster-events
12:38:09 <atinm> I don't think we are doing a good job with this :(
12:38:24 <atinm> is this up to date?
12:38:49 <hchiramm> atinm, the right place is website..
12:39:06 <hchiramm> may be we can have a sub page for community which list the events..
12:39:12 <hchiramm> tigert what do  u think /
12:39:42 <atinm> hchiramm, we can very well do that
12:39:45 <atinm> hchiramm++
12:40:37 <atinm> #action Instead of maintaining a public pad, integrate the gluster event details in gluster.org, tigert / hchiramm to work on it
12:40:52 <atinm> #info     REMINDER to put (even minor) interesting topics on https://public.pad.fsfe.org/p/gluster-weekly-news
12:41:13 <atinm> Thanks msvbhat to taking it up for publishing for Week 30
12:41:56 <atinm> I would urge everyone to add important achievements in this pad
12:42:21 <atinm> #info Per release documentation. Users are landing on 3.2 documentation from google itseems. How can we make this better
12:42:30 <atinm> I've no idea on this, anyone?
12:43:59 <atinm> The last but not the least
12:44:01 <atinm> #info Spurious failures - status
12:44:50 <atinm> IMHO, I've seen a single patch in this week which tries to fix one of them and that bothers me a bit
12:45:00 <atinm> read it as I've not
12:45:30 <atinm> Who wants to send a reminder mail to the thread which hagarth initiated
12:45:50 <kkeithley> wrt landing on 3.2 doc...  I believe Humble did some google magic to try to fix that. Is that right?
12:46:40 <kkeithley> hchiramm: ^^^
12:46:52 <hchiramm> kkeithley, I tried
12:46:53 <hchiramm> :)
12:47:07 <hchiramm> we are almost in , however stuck with RTD design
12:47:13 <kkeithley> so that takes a little while before it'll have an effect.
12:47:20 <kkeithley> s/an/any/
12:47:32 <hchiramm> yes..
12:47:58 <hchiramm> however this task is on going , hopefully we will have a complete solution soon
12:49:01 <atinm> hchiramm, cool
12:49:17 <atinm> any takers on replying to the mail thread http://www.gluster.org/pipermail/gluster-devel/2015-July/046284.html
12:50:06 <atinm> all right
12:50:15 <atinm> any other topics to be discussed?
12:50:26 <atinm> I will wait for a minute and then we can adjourn
12:50:35 <kkeithley> what kind of reply?  Are we not in agreement that that's a good way to proceed?
12:52:29 <atinm> kkeithley, reminder to fix the spurious failures
12:52:55 <atinm> kkeithley, or remove the test unit to a different folder
12:53:06 <atinm> kkeithley, does that make sense?
12:53:11 <kkeithley> sure
12:53:49 <kkeithley> I'll reply ;-)
12:53:58 <atinm> kkeithley, cool :)
12:54:10 <kkeithley> unless someone else has a strong desire to.
12:54:39 <atinm> #action kkeithley to drop a follow up mail about spurious failure fixes
12:54:55 <atinm> Allright, that brings us to the end of this meeting
12:55:02 <atinm> thanks everyone for participating
12:55:06 <atinm> #endmeeting