15:02:17 <ndevos> #startmeeting
15:02:17 <zodbot> Meeting started Wed Jul 16 15:02:17 2014 UTC.  The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:17 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:02:45 <ndevos> #link https://public.pad.fsfe.org/p/gluster-community-meetings
15:03:03 <ndevos> ^ thats the agenda, please add topics in case you notice something it missing
15:03:23 <ndevos> so, lets gets started, who do we have attending today?
15:03:28 <ndevos> #topic roll call
15:03:56 * pranithk here
15:04:03 * Eco_ present
15:04:11 <ndevos> good, I'm not alone \o/
15:04:19 * xavih is here
15:04:26 <semiosis> here
15:04:28 <Eco_> ndevos, you're never alone with us
15:04:56 <Eco_> we were there in your heart the whole time  ;)
15:05:14 <ndevos> Eco_: wonderful!
15:05:31 <ndevos> #topic Action items from last meeting
15:05:45 <ndevos> "JustinClift to add freebsd slave node to Jenkins"
15:06:06 <ndevos> anyone knows about this, other than JustinClift?
15:06:41 * ndevos guesses not
15:06:54 <ndevos> next: hagarth to send out an email on abandon policy for gerrit patches
15:07:06 <pranithk> ndevos: he updated the pad with '(Sometime in the next few weeks?)'
15:07:17 <ndevos> pranithk: no, that was me :)
15:07:22 <pranithk> ndevos: ah!
15:07:26 * lalatenduM is here
15:07:44 <pranithk> ndevos: Vijay won't be attending the meeting but he gave me things he wanted to tell. But this is not one of them :-(
15:07:50 <ndevos> hagarth was online earlier, but seems to be offline again...
15:08:06 <ndevos> does anyone else have details about the "abandon policy for gerrit patches"?
15:08:09 <pranithk> ndevos: Hagarth left office just a while back. So he can't make it to the meeting
15:08:38 <ndevos> pranithk: ok, we'll move on then
15:08:40 <pranithk> ndevos: yes
15:08:51 <ndevos> Eco_: for you: get initial GlusterFS Consultants and Support Companies page online
15:09:18 <Eco_> ndevos, that is still pending getting the site to a more managed state
15:09:29 <ndevos> Eco_: ok
15:09:34 <Eco_> the launch occurred but there are several problems we didn't see in staging
15:10:20 <ndevos> I guess it's the same for any deployment... how are things progressing?
15:11:07 <Eco_> still figuring out what all is wrong but getting a better sense of what the major pain points are
15:11:17 <Eco_> ill be monitoring for 404's and fixing as i can
15:11:23 <lalatenduM> Eco_, do we have plans to search box in http://www.gluster.org/documentation/ to find pages using strings
15:11:40 <Eco_> documentation for how the community should help will be out today or tomorrow
15:12:08 <Eco_> lalatenduM, not right now we are still putting out fires but down the road yes certainly
15:12:20 <lalatenduM> Eco_, cool
15:12:22 <jdarcy> I've had a request to make sure some of the hekafs.org content gets to gluster.org before the domain expires.
15:12:27 <ndevos> Eco_: okay, that documentation is very important, and as JoeJulian mentioned in the email, a very low burdon to submit some updates (no git!) should be available
15:12:45 <Eco_> jdarcy, good to know i didn't realize it was going to expire1
15:13:28 <jdarcy> Hekafs.org expires next month, cloudfs.org in December.  I'm not going to keep paying for either myself, and Red Hat has declined to take them over.
15:13:51 <ndevos> we'll move on to the next topic, please add any additional website topics to the agenda
15:14:10 <ndevos> "pranithk & Nithya to write documentation for dht"
15:14:35 <ndevos> pranithk: hows progress there?
15:14:36 <jdarcy> I wrote most of a document, still being reviewed/improved on Gerrit.
15:14:45 <pranithk> ndevos: jdarcy wrote the initial draft. Once that is accepted it will be improved.
15:14:48 <ndevos> jdarcy: nice, link?
15:15:05 <jdarcy> http://review.gluster.org/#/c/8240/
15:15:56 <ndevos> good, noted
15:16:06 <pranithk> ndevos: Dht is one BIG xlator. So getting all of it by just one person is too hectic IMO. Now that jdarcy started things off, we shall add more stuff on top.
15:16:51 <ndevos> pranithk: use common sense? maybe at least mention which topics/chapters are TODO and add those when time comes?
15:17:11 <pranithk> ndevos: It is there in the comments I think.
15:17:27 <ndevos> pranithk: thats all good then, I did not read the document yet
15:17:39 <pranithk> ndevos: cool :-)
15:17:51 <ndevos> pranithk: and I'm painfully aware that DHT is a little complex ;-)
15:18:16 <ndevos> anything else related to DHT documentation?
15:18:41 <pranithk> ndevos: none from me
15:18:45 <ndevos> okay
15:18:47 * lalatenduM thinks dht is black magic :) ( in a positive way)
15:19:01 <ndevos> next item was again for JustinClift: JustinClift to get new cleanup patch finished and merged
15:19:14 <ndevos> pranithk: anything you were involved with?
15:19:48 <pranithk> ndevos: No sir!
15:20:00 <ndevos> hmm, wel'll skip it then
15:20:06 <pranithk> ndevos: yep
15:20:13 <ndevos> #topic glusterfs-3.4
15:20:40 <ndevos> we don't have kkeithley here today, did he pass any 3.4 tasks on to someone else?
15:21:02 <lalatenduM> ndevos, nope, release task remains with him
15:21:15 <pranithk> ndevos: I may want to send a patch on 3.4 about glustershd leak reported by chalkogen
15:21:57 <ndevos> pranithk: make sure to add it to the glusterfs-3.4.5 blocker, and put kkeithley as reviewer of the patch
15:22:16 <ndevos> but I think you're well aware of that procedure by now :)
15:22:47 <pranithk> ndevos: yes sir.
15:22:48 <ndevos> is there any general feedback on 3.4.5beta2 that we should pass on to Kaleb?
15:24:15 <ndevos> I guess thats a "no"
15:24:26 <ndevos> #topic glusterfs-3.5
15:25:02 <ndevos> we're still accepting patches for 3.5, post them for review and add your bugs to the 3.5.2 blocker
15:25:18 <pranithk> ndevos: I just posted one today :-)
15:25:52 <ndevos> pranithk: you post patches almost every day!
15:25:57 <ndevos> #link https://bugzilla.redhat.com/showdependencytree.cgi?hide_resolved=1&id=glusterfs-3.5.2
15:26:12 <pranithk> ndevos: :-)
15:26:33 <ndevos> the number of bugs that will get resolved in 3.5.2 is increasing, we should start thinking of a date to do a beta release
15:26:53 <pranithk> ndevos: Why not by next community meeting?
15:27:28 <ndevos> well, I (the 3.5 release maintainer) will be unavailable most of next week
15:27:59 <ndevos> depending on how things go, I can probably get it done in two weeks
15:28:14 <pranithk> ndevos: cool :-)
15:28:14 <ndevos> or, well, in the end of the 2nd week from now
15:28:19 * ndevos check calendar
15:29:05 <ndevos> how does a 1st beta of 3.5.2 on the 1st of august sound?
15:29:56 <pranithk> ndevos: Good :-)
15:30:31 <ndevos> in that case, concider that done :)
15:30:50 <ndevos> anything else in need of discussion for 3.5?
15:31:12 <ndevos> no, seems not
15:31:13 <ndevos> #topic glusterfs-3.6
15:31:35 <ndevos> ah, vijay isnt there, and I have not seen an announcement for the branching
15:31:37 <pranithk> ndevos: This is what vijay wanted to tell.
15:31:56 <pranithk> ndevos: branching is happening tomorrow. qa release will be done tomorrow after branch is created
15:32:10 <ndevos> cool, sounds good
15:32:28 <pranithk> ndevos: Since the freeze date is pushed many times we need to also push community testing day
15:32:53 <pranithk> ndevos: it was supposed to be 18th of this month it seems. We need to come up with new date for that.
15:32:54 <jdarcy> I'm hoping to get 8276 in before then.  Less data loss = good.
15:33:21 <ndevos> #action hagarth to branch release-3.6 tomorrow (17th of July) and start the qa-release process
15:33:57 <pranithk> jdarcy: ndevos: I feel there should be at least 1 week gap between 3.5 beta release and 3.6 community day?
15:33:59 <ndevos> jdarcy: anything urgent that is not included in the release-3.6 branch, should get backports
15:34:44 <ndevos> pranithk: we can keep the 3.5.2-beta available for an extended period of time, thats not a problem I think
15:35:02 <ndevos> and, probably we address different testers with 3.6 and 3.5 too
15:35:06 <pranithk> ndevos: oh cool
15:35:19 <pranithk> ndevos: What date then?
15:36:03 <ndevos> pranithk: what I mean is, we do not need to push 3.5.2-beta for testing as much/early as a 3.6 release
15:36:20 <pranithk> ndevos: What was the first date we decided for feature freeze?
15:36:27 <ndevos> I expect that the people who filed bugs against 3.5 have a higher interest in testing 3.5 than 3.6
15:36:39 <pranithk> ndevos: What was the first date we decided for community testing day for 3.6?
15:36:46 <pranithk> ndevos: We can probably have same gap I guess.
15:37:02 <pranithk> ndevos: I agree on the interest part :-)
15:37:41 <ndevos> pranithk: I have no idea, not sure if we really need to take care of a dependency between the two releases and their test-days
15:38:27 <pranithk> ndevos: Let me do one thing. Let me talk to Vijay tomorrow in office and send out a mail. Put that as action item on me
15:38:38 <ndevos> pranithk: I'd suggest to announce the 3.6 test days very clearly and obvious, the 3.5 testing of the beta will be announced through the bug reports
15:39:05 <pranithk> ndevos: All we need to decide on is date :-)
15:39:23 <ndevos> #action pranithk discuss with vijay about community test days for 3.6 and its potential conflict with a 3.5.2 beta
15:40:00 <pranithk> ndevos: Other agenda items?
15:40:04 <ndevos> #action pranithk propose a date for the community test-days of 3.6, and whatnot
15:40:22 <ndevos> yes, we have some other agenda items
15:40:33 <ndevos> #topic Documenting Gluster internals
15:40:42 <ndevos> oh, thats pranithk again...
15:41:24 <pranithk> ndevos: We got good response on that. Quite a few volunteers. Goal is to get all xlators, data structures documentation done by End of this year.
15:41:36 <ndevos> pranithk: are all components you listed in your email assigned?
15:41:51 <pranithk> ndevos: I can take care of the ones that are not assigned by anyone.
15:42:07 <ndevos> #link http://supercolony.gluster.org/pipermail/gluster-devel/2014-July/041531.html
15:42:13 <pranithk> ndevos: assigned to* anyone
15:42:43 <ndevos> #action pranithk to send a list with components and their assignees - soliciting others to contribute too
15:42:54 <pranithk> ndevos: yes sir!
15:43:35 <ndevos> pranithk: next topic?
15:43:48 <ndevos> or, anyone else with input on that?
15:43:56 <pranithk> ndevos: Shall we change the time for this meeting?
15:44:12 <ndevos> pranithk: is that on the agenda for today?
15:44:25 <pranithk> ndevos: Not really. I am adding it now :-|
15:44:32 <ndevos> pranithk: add it at the end :D
15:44:43 <xavih> ndevos, pranithk: I would like to create a new component: ec
15:45:15 <ndevos> xavih: for the documentation task? I think thats a good thing :)
15:45:15 <pranithk> ndevos: done
15:45:28 <pranithk> ndevos: No he means bugzilla I think
15:45:31 <xavih> ndevos: sorry, I meant for BZ...
15:45:36 <ndevos> xavih: the bugzilla component should get done, but thats off-topic now
15:45:49 <xavih> ndevos: yes, I know, sorry :(
15:45:59 <pranithk> ndevos: what is the topic now?
15:46:14 <ndevos> #topic Bug triage is getting started
15:46:39 <ndevos> Humble and lalatenduM have been working to get the bug triaging process documented
15:46:43 <ndevos> #link  http://www.gluster.org/community/documentation/index.php/Bug_triage
15:47:18 <ndevos> there is still a little more to document/explain, mainly by giving some examples
15:47:48 <lalatenduM> ndevos, yup will work on it
15:48:07 <ndevos> we've been slacking on triaging new bugs, hopefully we can get some traction of new contributros that want to help with debugging and identifying issues
15:48:59 <ndevos> so, anyone is invited to follow up on the emails to gluster-devel, or ping any of us in #gluster-dev
15:49:44 <ndevos> lalatenduM: can you take an AI for sending an announcement email with the bug triage process?
15:50:03 <lalatenduM> ndevos, sure
15:50:13 <ndevos> #action lalatenduM send a bug triage email announcing the process, and call for volunteers
15:50:23 <ndevos> thanks!
15:50:30 <lalatenduM> ndevos, before that we need to create the email alias
15:50:38 <ndevos> #topic change of the meeting time?
15:50:52 <lalatenduM> like bugs@gluster.org
15:51:11 <ndevos> lalatenduM: definitely, but I dont think that is a major issue
15:51:56 <ndevos> so, what would be a way to figure out a more suitable (if there is such a thing) meeting time?
15:52:37 <pranithk> ndevos: I think the main reason for this timing was to make sure Avati can attend. Considering he is not active on these meetings may be we can have it early as well?
15:52:47 <ndevos> it's 17:50 where I live, and not optimal for me, but we're spread globaly and picking a time isnt very straight forward (I think)
15:53:29 <lalatenduM> pranithk, which timing will suit Avati ?
15:53:40 <ndevos> pranithk: yes, but it probably is very early for Eco_ too...
15:53:52 <pranithk> ndevos: Hmm...
15:54:00 <ndevos> Eco_: how active do you want to participate in these meetings?
15:54:47 * ndevos wonders if that is Ecos answer
15:55:34 <ndevos> jdarcy: how much earlier would for for you and the guys in your timezone?
15:55:57 <ndevos> pranithk: how many hours would you like to move the meeting earlier?
15:56:01 * jdarcy scrolls back to get the context.
15:56:10 <pranithk> ndevos: 3?
15:56:10 <ndevos> jdarcy: change in the meeting times
15:56:24 <ndevos> jdarcy: does 3 hours earlier work for you?
15:56:41 <jdarcy> Fine for me personally.
15:56:49 <ndevos> xavih: 3 hours earlier for you, should just be after lunch?
15:56:59 <ndevos> jdarcy: what time is that in Boston?
15:57:15 <jdarcy> That would make it 8am.
15:57:16 <xavih> ndevos: more in the middle of the lunch...
15:57:23 <ndevos> hey lpabon: any opinion on moving the meeting 3 hours earlier?
15:57:30 <xavih> ndevos: I could adjust a little if needed
15:57:50 <jdarcy> Not everyone's favorite time, but it's hard to argue it's unreasonable.
15:58:20 <pranithk> ndevos: This way people from redhat bangalore office can also participate is my feeling.
15:58:27 * ndevos would personally not prefer a meeting at 8am
15:58:37 <ndevos> pranithk: yes, and that really makes sense
15:58:50 <jdarcy> Past experience has been that the early mornings here (mid-evening in BLR) work best.  Late evening here (early in BLR) kinda-sorta works.  Anything else just plain sucks.
15:59:01 <Eco_> ndevos, sorry computer locked up
15:59:07 <Eco_> reading backlog
15:59:07 <jdarcy> And of course the late-evening time is a disaster for Europe/ME.
15:59:08 <ndevos> pranithk: instead of 3 hours earlier, maybe 2 hours?
15:59:45 <pranithk> ndevos: That will make people stay at office till 7:30 may not be good
16:00:01 * lalatenduM is ready to adjust if it encourages more people to attend
16:00:03 <pranithk> ndevos: I know quite a few people don't mind 6:30
16:00:37 <lalatenduM> pranithk, for 6:30 metteing they have stay till 7:30
16:00:38 <pranithk> ndevos: Let me send out a mail in bangalore mailing list to get a good timing and getback?
16:00:39 <ndevos> pranithk: yeah, I assume 6:30 pm is the latest we can expect people to stay at the office
16:00:48 <ndevos> pranithk: yeah, sounds good
16:00:52 <Eco_> ndevos, i planned on attending but 6AM would be difficult
16:01:11 <pranithk> Eco_: hmm.. :-(
16:01:23 <ndevos> #action pranithk to solicit feedback on who would join the weekly meeting when it takes place 2 or 3 hours earlier
16:01:31 <Eco_> pranithk, ndevos if that is the decision of the entire group i can make the sacrifice
16:01:37 <ndevos> Eco_: I fully understand
16:01:42 <Eco_> can't do -3 or -1 though
16:01:42 <pranithk> Eco_: Nothing is decided.
16:02:05 <pranithk> Eco_: Let me ask people around then will get back to you guys in the next meeting
16:02:39 <Eco_> pranithk, sounds good
16:02:39 <pranithk> lalatenduM: May ask for your help on this....
16:02:41 <ndevos> pranithk: do send the email early next week, include the result and clear time suggestions
16:02:50 <pranithk> ndevos: yes sir!
16:02:54 <lalatenduM> pranithk, sure
16:03:03 <pranithk> thats it from me then
16:03:22 <ndevos> pranithk, lalatenduM: with that, the others in different timezones can then respond with their suggestions/issues
16:04:01 <pranithk> ndevos: agreed
16:04:14 <ndevos> pranithk: if this does not work out, we should maybe create a doodle or similar for it, and request all community members to fill that in
16:04:32 <pranithk> ndevos: That may be a good thing I suppose
16:05:01 <pranithk> ndevos: I feel there are lot of engineers in blr office who just are not at all exposed to upstream. This way at least they get a taste...
16:05:01 <ndevos> #topic new bugzilla component requests and default assignees
16:05:05 <jdarcy> Note that there is simply no time that can cover both US coasts plus Europe plus India without someone having to be up at an unreasonable time.
16:05:19 <pranithk> jdarcy: yes :-(
16:05:43 <ndevos> #action xavih email Humble with the request to add a 'ec' component
16:05:45 <pranithk> jdarcy: We can may be evolve a rotation policy
16:05:58 <xavih> ndevos: ok
16:06:13 <pranithk> jdarcy: Lets get some data and we shall talk about it again in the next meeting...
16:06:27 <ndevos> jdarcy: yes, and we need to see what time suits most community members, some will have to sacrifice some sleep (or skip the meeting)
16:07:04 <ndevos> any other topics? be quick, we've passed the scheduled time already
16:07:12 <pranithk> ndevos: none frome me
16:07:24 * jdarcy zips it.
16:07:32 <ndevos> #endmeeting