12:01:28 <ndevos> #startmeeting
12:01:28 <zodbot> Meeting started Wed Jul  8 12:01:28 2015 UTC.  The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:28 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:01:33 <ndevos> #info Agenda: https://public.pad.fsfe.org/p/gluster-community-meetings
12:01:39 <ndevos> #topic Roll Call
12:01:46 <ndevos> hi all, who's there today?
12:01:46 * jdarcy is
12:01:47 <hagarth> o/
12:01:53 * hagarth is here
12:01:54 * rafi1 is here
12:02:12 * overclk is here
12:02:18 * kkeithley is aqui
12:02:21 * raghu is here
12:02:53 <ndevos> well, thats not too bad, but I hope we can convince more others to join next time :)
12:03:14 <ndevos> #topic Last weeks action items
12:03:24 <ndevos> #topic kkeithley to check on new Forge hand-off from JustinClift
12:03:45 * soumya is here
12:03:46 * jiffin here
12:03:49 <kkeithley> Justin contacted me after the meeting
12:03:58 <kkeithley> he says he's still going to do it.
12:04:19 <ndevos> okay, you mean the hands-over, or the actual work?
12:04:30 <kkeithley> I have not contacted anyone else, e.g. his former manager, to find out if someone else will pick up where he leaves off
12:04:33 <kkeithley> the actual work
12:04:54 <ndevos> oh, good :)
12:05:29 <ndevos> I'm not sure if there is a Justin-replacement, or if there is any pressure to move quick(er)
12:05:50 <ndevos> hagarth: do you know more about that?
12:05:54 <spot> ndevos: i don't have any real insight into that. I asked, but I did not get a good answer.
12:06:12 <ndevos> spot: ah, ok
12:06:13 <hagarth> ndevos: I know that there is a candidate in sight, but don't have any further details beyond that.
12:06:25 <kkeithley> maybe something for the new community manager — if one ever gets hired — to take up
12:07:08 <ndevos> yeah, I guess a new community manager would lead it, but we still need someone doing the technical bits'n pieces that Justin did
12:07:12 * obnox is here but late (sorry)
12:07:18 * RaSTar is here
12:07:50 <ndevos> hagarth, spot: who of you would be able to find out more details before next meeting?
12:08:04 <spot> ndevos: i'll ask about it later today.
12:08:11 <ndevos> spot: thanks!
12:08:39 <ndevos> #action spot Will ask about a potential Justin replacement
12:08:45 <ndevos> #topic tigert summarize options for integrating a calendar on the website, call for feedback
12:08:55 <ndevos> tigert: are you there, or still on holidays?
12:09:18 * ndevos assumes holidays
12:09:22 <ndevos> #topic hagarth will start with planned roadmaps for all gluster.next releases
12:09:35 <hagarth> ndevos: plan to complete this week
12:09:49 <hagarth> in fact have a discussion on 3.8 plans added in the agenda today
12:09:54 * msvbhat arrives late to the meeting
12:10:21 <ndevos> #action hagarth *will* complete roadmap planning for the next gluster releases *this* *week*
12:10:37 <ndevos> #topic csim/misc to pickup the requesting of public IPs and those kind of things for our new servers
12:10:58 <ndevos> csim: you've started some workaround with a VPN if I understood correctly?
12:11:38 <ndevos> well, he did, see #gluster-dev earlier today
12:11:52 <ndevos> but, he's blocked on some firewall issue...
12:12:11 <ndevos> might be the iWeb firewall, I did not ask for the details from him
12:12:21 <ndevos> #topic hagarth to push 4.0 roadmap on the site
12:12:41 <csim> ndevos: yup, but firewall on both side block, so waiting to open and looking back at setting some VM
12:12:59 <ndevos> hagarth: once the plans are ready later this week, when will we have a nice page on gluster.org with them?
12:13:02 <csim> basically, RH firewall block the VPN when the server is RH side, and iweb when on iweb side :)
12:13:07 <hagarth> ndevos: that's the plan
12:13:14 <ndevos> csim: ah, thanks!
12:13:15 <csim> (so i choose RH firewall to be opened, as I know who to ping/annoy)
12:13:29 <csim> (I could make it run over ssh, but this did look too much a hack)
12:13:30 <ndevos> hagarth: you missed the "when" in my question :)
12:13:41 <hagarth> ndevos: this week of course :)
12:13:50 <ndevos> hagarth: heh, ok!
12:14:13 <ndevos> #action hagarth will publish the 4.0 roadmap to gluster.org later this week
12:14:25 <ndevos> #topic overclk to put up feature page for lockdep
12:14:37 <ndevos> overclk: did you put something togther?
12:14:53 * ndevos did not see an email about it, but could easily have missed that
12:14:56 <overclk> ndevos, nope. later this week.
12:15:26 <ndevos> #action overclk will create a feature page about lockdep later this week
12:15:41 <ndevos> overclk: btw, where are feature pages created now?
12:15:46 <ndevos> the wiki is read-only...
12:16:08 <ndevos> hchiramm: any suggestion from you?
12:16:14 <hagarth> ndevos: is it in hchiramm's doc repository?
12:16:26 <hchiramm> hagarth, ndevos yes
12:16:30 <hchiramm> it has to be in github project
12:16:42 <ndevos> hagarth: maybe, but for work-in-progress documents sending pull-requests does not make much sense?
12:17:20 <hagarth> ndevos: hmm, why not? maybe we mark it as a draft somewhere?
12:17:29 <hchiramm> ndevos, u can even have a collb. tool like google docs
12:17:36 <hchiramm> and have a feature page linked
12:17:53 <ndevos> hchiramm: ew, who wants to use google docs!?
12:18:05 <hchiramm> its an example :)
12:18:10 <ndevos> :)
12:18:21 <hagarth> hchiramm: no to google docs please ;)
12:18:31 <obnox> same here
12:18:54 <ndevos> #action overclk will experiment with getting a feature page added to the readthedocs repo, and send *many* pull requests
12:19:39 <ndevos> #topic krishnan_p to send out email on devel list about improving our epoll solution
12:19:48 <ndevos> krishnan_p: no email about that yet?
12:19:48 <jdarcy> Somebody should create an open-source collaborative text editing platform with at least half the functionality of Google Docs.  Haven't seen one yet.
12:19:54 <krishnan_p> ndevos,  I will be sending the email out by end of this week
12:20:21 <ndevos> krishnan_p: thanks!
12:20:39 <ndevos> #action krishnan_p will send an email about improving epoll this week
12:21:06 <ndevos> jdarcy: something like etherpad, but with a git backend of some kind?
12:21:06 <obnox> jdarcy: vi + git ? ;)
12:21:21 <RaSTar> agree with jdarcy here, we have seen two proposals on google docs last month
12:21:33 <ndevos> #topic Documenting work in progress stuff
12:21:49 * hagarth even thinks of a name .. gitterpad
12:21:52 <jdarcy> ndevos: And inline commenting.  That's a huge difference between mature and not-so-mature tools.
12:22:26 <ndevos> #info documentation moved to the readthedocs project with a github repository, questions on editing are not all answered yet
12:23:12 <krishnan_p> jdarcy, agree.
12:23:12 <ndevos> jdarcy: yeah, commenting is extremely helpful...
12:23:50 <jdarcy> Sorry about derailing the conversation.  Just kind of a pet peeve.
12:24:24 <ndevos> hchiramm: GitHub offers a wiki too, and is backed by a git repo, it is easier to edit that, any reason why we are not using that for the documentation?
12:25:16 <ndevos> jdarcy: I like to have a discussion with some clarity about how we should proceed with documenting things, its rather messy at the moment
12:25:59 <ndevos> nobody can find an etherpad (or, ew, a Google doc) because those are not linked from the main documentation
12:26:34 <ndevos> and, linking them would be wrong too, we wanted nicely integrated docs, not distributed over many different systems
12:26:53 <krishnan_p> ndevos, agree. Please include me in that discussion.
12:27:20 <ndevos> krishnan_p: you just included yourself :)
12:27:43 * ndevos was actually expecting hchiramm to respond with ... something
12:27:43 <krishnan_p> ndevos, :)
12:27:55 <jdarcy> Do planning/tracking docs need to be linked from the (semi) permanent doc, or are they more like BZ?
12:28:51 <ndevos> I would like to see all/most docs reachable from the same entry point, like gluster.readthedocs.org, something users can easily find
12:29:30 <ndevos> where it is kept does not really matter to me, but users should be able to find it and contribute ideas, suggestions and fixes
12:30:48 <ndevos> #action hchiramm to come up with suggestions on how/where to post work-in-progress documentation
12:31:27 <ndevos> one of the other things that is still open, is what documentation should we (if any) keep in the soure repository?
12:31:36 <jdarcy> Then we have a dilemma.  If we want it to be usable by non-developers then we exclude anything involving a pull request, but if we want it to be on the same site as our main doc we've excluded everything else.
12:31:56 <hchiramm> ndevos, is github wiki browsable ?
12:32:02 <hagarth> ndevos: I would prefer design docs to be in the repo
12:32:30 <ndevos> hagarth: me too, but not everyone agrees :)
12:32:49 <krishnan_p> ndevos, hagarth, yes. What happens while it is being worked on?
12:32:58 <ndevos> hchiramm: sure, pages are listed on the right side of the wiki
12:33:02 <RaSTar> a little crazy idea, have WIP design docs in repo and use gerrit for inline comments
12:33:21 <obnox> RaSTar: i was thinking of the same - gerrit as a commenting tool
12:33:21 <kshlm> I have a suggestion. Wiki while being worked on, and push to repo when final.
12:33:44 <RaSTar> obnox: :)
12:33:45 <krishnan_p> kshlm, do we retire the wiki afterwards?
12:33:54 <kshlm> Obviously.
12:34:04 <RaSTar> kshlm: wiki's aren't that helpful for comments
12:34:11 <ndevos> with a pointer to the docs that got merged :)
12:34:13 <krishnan_p> kshlm, I hope so.
12:34:37 <ndevos> I like the gerrit idea, that is how all developers do inline commenting already
12:35:09 <hchiramm> ndevos, well, we can not have multiple places for documentation
12:35:34 <hchiramm> and lot many people want to help to improve documentation
12:35:36 <ndevos> hchiramm: didnt *you* just suggest to use Google docs?
12:35:45 <hchiramm> ndevos, no..
12:35:53 <kshlm> How about just use PRs on the docs repo for discussion.
12:35:55 <hchiramm> I said collb.tools like google docs
12:36:19 <hchiramm> or etherpad..or whatever it it
12:36:40 <ndevos> well, what collab tool can be used for documentation in a git repository? ... gerrit and what else?
12:36:42 <RaSTar> kshlm: personally I find that a lot of work compared to double-click and comment
12:36:50 <hchiramm> the only point what I am trying to bring here is, u can link those pages from our docs repo
12:37:14 <kshlm> RaSTar, It's the same on github PRs. I don't think you'll be doing any more work.
12:37:36 <hchiramm> more or less, nobody really worried to give responses on the thread started in MLs
12:37:50 <RaSTar> kshlm: oh ok, did not know that
12:38:04 <kshlm> Github also has an online editor, so you could complete the whole review without ever leaving the browser.
12:38:42 <kshlm> For documentation I don't think the online editor will be a problem.
12:39:01 <ndevos> hchiramm: I think the email was pretty clear on the path forward, but we are missing a workflow for documents that are continously updated while design is being done
12:39:36 <hchiramm> ndevos, the thread was intended to collect the ideas as well
12:39:37 <ndevos> hchiramm: the wiki was a good solution for that, just edit and save, we dont have the wiki anymore, so we need a replacement
12:39:47 <hagarth> is gist an option? or is it more like fpaste?
12:40:17 <hchiramm> ndevos, who will make sure the authenticity of media wiki content ?
12:40:21 <ndevos> can you comment in a gist? if so, that could work
12:40:27 <kshlm> gist's can have comments. So they can be used for discussions.
12:40:35 <hagarth> ndevos: you can try here - https://gist.github.com/vbellur/78baaef077267a6f9594
12:40:50 <hchiramm> ndevos, if u google u land into gluster wiki with GLusterFS 3.2 content ..
12:40:58 <hchiramm> then people try that and come back with issues..
12:41:04 <ndevos> hchiramm: dont get me wrong, we dont need the media wiki back ;)
12:41:26 <hchiramm> and there were lots of complaints were people dont want to go through
12:41:39 <hchiramm> review process ( review.gluster.org) for correcting a typo
12:42:00 <hchiramm> as a new user they dont want to configure the gerrit for sending a documentation patch
12:42:02 <kshlm> I still believe using PRs will be the best.
12:42:04 <hagarth> ndevos: probably no inline commenting in gist
12:42:17 <ndevos> hchiramm: its not about the final user documentation, the old wiki pages now have redirects to the up-to-date docs, right?
12:42:17 <hchiramm> we were trying to address these type of issues..
12:42:21 <kshlm> I'll do one just as a test.
12:42:38 <hchiramm> ndevos, we have ported most of the docs..
12:42:47 <hchiramm> however we would have missed some
12:42:58 <ndevos> hchiramm: we need something that makes it easy to edit something, and get inline comments from others
12:43:00 <RaSTar> yes, gist does not seem to have inline comments
12:43:26 <RaSTar> and IMO we should differentiate between developer documentation and user documentation
12:43:28 <hchiramm> ndevos, well, the feedback/suggestions/thoughts were invited couple of times
12:43:41 <hchiramm> but nobody really responded with the inputs.
12:43:50 <ndevos> hchiramm: can you write an email with what was discussed here?
12:43:54 <hagarth> hchiramm: probably we should ask feedback in a less formal language :D
12:44:27 <ndevos> RaSTar, kshlm, krishnan_p, jdarcy, obnox: please respond to the email hchiramm will put together!
12:44:40 <hchiramm> hagarth, ^^ may be u can take above AI then :)
12:44:58 <ndevos> #action hchiramm summarizes todays discussion about documentation
12:45:00 <hagarth> hchiramm: no, I have plenty on my plate already for this week ;)
12:45:12 <hchiramm> hagarth, :)
12:45:44 <ndevos> #action RaSTar, kshlm, krishnan_p, jdarcy, obnox, ndevos reply to hchiramms email
12:46:05 <ndevos> #topic GlusterFS 3.7
12:46:19 <ndevos> atinm, hagarth: ?
12:47:02 <hagarth> ndevos: plan to release 3.7.3 next week
12:47:14 <hagarth> please have all backports sent by end of this week
12:47:29 <ndevos> #info GlusterFS 3.7.3 is scheduled to be released nenxt week
12:47:35 <hagarth> I plan to run some tests with distaf before we release
12:47:54 <ndevos> hagarth: who is the release manager for this one?
12:48:21 <hagarth> ndevos: defaults to me, happy if someone else wants to pick this up
12:48:56 <ndevos> #help maintainers can volunteer to become release manager for 3.7.3
12:49:08 <ndevos> #topic GlusterFS 3.6
12:49:17 <kkeithley> I haven't submitted any of those Mac OS X fixes to release-3.7.  Does anyone care?
12:49:21 <ndevos> raghu: your turn!
12:49:26 <raghu> I have made glusterfs-3.6.4beta2 and announced it as well.
12:49:52 <ndevos> #info glusterfs-3.6.4beta2 has been announced
12:50:05 <raghu> want to make 3.6.4 GA by end of this week. But there seem to be a NetBSD compilation error. So want to get that fix in before making GA
12:50:12 <ndevos> raghu: still waiting for some NetBSD/FreeBSD compile fixes, I think?
12:50:20 <raghu> ndevos: yes
12:50:46 <raghu> I probably wont make another beta. Want to directly GA 3.6.4 with that fix
12:51:05 <ndevos> #info there seem to be a NetBSD compilation error, waiting with GA release until that is fixed
12:51:18 <ndevos> sounds good to me
12:51:35 <ndevos> #topic GlusterFS 3.5
12:51:50 <ndevos> glusterfs-3.5.5 has been released yesterday
12:52:02 <hagarth> ndevos: yay!
12:52:13 <ndevos> 4 bugs should have been fixed with that, RPMs have not been made yet
12:52:22 <kkeithley> 3.5.5 RPMs are building. I'll release to hchiramm momentarily to sign and upload to d.g.o
12:52:31 <ndevos> there is no ETA for 3.5.6 yet
12:52:44 <ndevos> kkeithley: awesome!
12:53:05 <ndevos> #topic Gluster 4.0
12:53:19 <ndevos> jdarcy: do you have something to share?
12:53:36 <jdarcy> Not really.  I was on PTO last week, and Summit before that.
12:54:02 <ndevos> okay, no hangouts or meetings planned?
12:54:12 <hchiramm> kkeithley, I will take care of it :) thanks!
12:54:18 <jdarcy> Not currently.
12:54:31 <ndevos> ok
12:54:44 <ndevos> #topic Open Floor / Bring Your Own Topic
12:54:47 <ndevos> - Gluster 3.8 plans
12:54:53 <ndevos> hagarth: thats yours?
12:55:01 <hagarth> I wanted to share plans about 3.8 with the community
12:55:09 <hagarth> here are things from the top of my mind:
12:55:36 <hagarth> 1. Storage as a Service - Heketi, Intelligent volume creation
12:55:51 <hagarth> 2. Quality - populate distaf with more tests from all our components
12:56:00 <hagarth> 3. Hyperconvergence with oVirt
12:56:34 <hagarth> 4. Integration with containers ..(have some ideas, to be built out more)
12:57:02 <hagarth> 5. ec improvements for doing more erasure coded algos
12:57:12 <hagarth> anything else that we would want to add in this list?
12:57:31 <hagarth> I want to check what the community feels about this initial list and what else they would like to see
12:57:31 <ndevos> 2b. integrate distaf in Jenkins
12:57:46 <hagarth> ndevos: right
12:58:00 <atinm> ndevos, hagarth : kerberizing gluster?
12:58:04 <ndevos> and, I'd like Kerberos support in 3.8 too
12:58:13 <atinm> *kerborizing
12:58:25 <hagarth> right, I think it fits well into the SaaS paradigm
12:58:53 <pranithk> hagarth: timelines?
12:59:14 * kkeithley has to drop off for another meetiung
12:59:17 <hagarth> pranithk: tentatively towards the end of this year
12:59:39 <ndevos> #info main ideas for Gluster 3.8 can be found in the IRC logs
12:59:44 <jdarcy> How about multiple-network support?
13:00:08 <hagarth> jdarcy: seems like a good one to have.. will propose that too
13:00:12 <jdarcy> Currently on the 4.0 plan, but might be doable in 3.8 and I think it would be significant for users.
13:00:16 <soumya> hagarth, delegations/lease-lock support or improvements
13:00:21 <hagarth> soumya: ok
13:00:41 <hagarth> I think we will have multi-threaded self-heal + IPv6 support also getting in
13:01:05 <atinm> hagarth, probably having volumes URCU protected as well ?
13:01:08 <ndevos> thats quite a big list already :)
13:01:28 <hagarth> atinm: would it be user visible?
13:01:39 <atinm> hagarth, no
13:01:44 <kshlm> atinm, Are you volunteering?
13:01:50 <hagarth> ndevos: yeah! :) .. I want to keep 3.8 light since most of our attention will be towards 4.0
13:02:02 <hagarth> however we should start viewing 3.8 as an interim release for 4.0
13:02:03 <ndevos> hagarth: that was what I was thinking too :)
13:02:10 <ndevos> next BYOT: IRC office hours
13:02:20 <atinm> kshlm, I want to get that done, but need to prioritize things
13:02:26 <hagarth> 3.8 should kind of be a preview of the bigger things to come by in 4.0
13:02:32 <hagarth> ndevos: that was mine too
13:02:41 * ndevos points at the clock
13:02:47 <hagarth> I was wondering if we can publish a IRC schedule on gluster.org
13:03:15 <ndevos> do we know if the office hours that KB does for CentOS are helpful?
13:03:24 <hagarth> with information on which volunteers will be around & responsible in what time slots.
13:03:36 <hagarth> so that users know whom to look for in #gluster
13:03:56 <atinm> hagarth, rebalance daemon is yet to be refactored with the current framework which can be done in 3.8 as well
13:04:02 <hagarth> volunteers need not have answers for everything, we can encourage users to log a bug, hit the mailing lists etc.
13:04:33 <hagarth> but having somebody responsive (apart from JoeJulian) will help I think :)
13:04:53 <hagarth> atinm: ok, I think you can add things from your list to the email I send on -devel
13:05:04 <hagarth> any thoughts on IRC hours?
13:05:06 <atinm> hagarth, sure will do that
13:05:17 <ndevos> I think #gluster and #gluster-dev *is* our office, nobody who works on Gluster should be ignoring that...
13:05:28 <hagarth> we can pick up 2 hr slots or so and have a nice volunteer spread across the week
13:05:48 <hagarth> ndevos: agree, but not having somebody own a particular slot helps
13:05:58 <hagarth> s/not having/having/
13:06:18 <ndevos> hagarth: yes, I agree that we need more participation from a more diverse group :)
13:06:41 <hagarth> maybe I will drop a note on -users, -devel and see if we can get coverage through the week?
13:06:56 <ndevos> hagarth: suggest someone who can create a schedule?
13:07:07 <hagarth> atinm: can you help here please?
13:07:51 <hagarth> ndevos: will check with atinm/others and get back on this one
13:07:51 <atinm> hagarth, yes I will
13:07:58 <hagarth> atinm: great, thanks!
13:08:03 <ndevos> atinm: maybe start an etherpad like https://public.pad.fsfe.org/p/gluster-office-hours and have people sign up there?
13:08:21 <ndevos> #action atinm will start a schedule for office hours in #gluster
13:08:35 <ndevos> thanks atinm!
13:08:41 <atinm> ndevos, np :)
13:09:00 <ndevos> #info Weekly reminder to announce Gluster attendance of events: https://public.pad.fsfe.org/p/gluster-events
13:09:15 <hagarth> who's speaking this week?
13:09:21 <ndevos> #help <someone> propose a roster/schedule for hosting the weekly meeting (all maintainers should participate)
13:09:48 <ndevos> I dont know if there are any events this week, but it should be in the etherpad and on announce@gluster.org
13:10:18 <ndevos> thanks all for joining! sorry we took a little longer than planned
13:10:26 <ndevos> #endmeeting