gluster-meeting
LOGS
12:01:38 <ndevos> #startmeeting
12:01:38 <zodbot> Meeting started Tue Oct 28 12:01:38 2014 UTC.  The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:38 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:01:49 <ndevos> Agenda for today: https://public.pad.fsfe.org/p/gluster-bug-triage
12:01:54 <ndevos> #topic Roll Call
12:02:07 <ndevos> Hi, my name is niels and I am here, am I alone?
12:02:17 * overclk is there
12:02:24 * hchiramm_ is here
12:04:17 <ndevos> #chair overclk hchiramm_
12:04:17 <zodbot> Current chairs: hchiramm_ ndevos overclk
12:04:44 <ndevos> lalatenduM: are you here too?
12:04:52 <lalatenduM> yes
12:05:00 * lalatenduM is here
12:05:01 <ndevos> #chair lalatenduM
12:05:01 <zodbot> Current chairs: hchiramm_ lalatenduM ndevos overclk
12:05:05 * kkeithley is here
12:05:07 <ndevos> #topic Status of last weeks action items
12:05:19 <ndevos> #topic lalatenduM will think about splitting the "Bug Triage" wiki page, and make suggestions
12:05:27 <ndevos> lalatenduM: any comments?
12:05:30 <lalatenduM> ndevos, missed it last week
12:05:45 <lalatenduM> will do it this week
12:05:46 <ndevos> lalatenduM: try again next week?
12:05:50 <ndevos> okay :)
12:05:51 <lalatenduM> yeah
12:05:54 <ndevos> #action lalatenduM will think about splitting the "Bug Triage" wiki page, and make suggestions
12:06:08 <ndevos> #topic hagarth will look for somebody that can act like a bug assigner manager kind of person
12:06:18 <ndevos> hagarth: any news on that one?
12:06:57 <ndevos> ... I guess he's busy with 3.6 now
12:07:08 <ndevos> #action hagarth will look for somebody that can act like a bug assigner manager kind of person
12:07:12 <ndevos> #topic pranithk to report how his team is assigning triaged bugs
12:07:23 <ndevos> argh, pranith isnt here :-/
12:07:48 <ndevos> and neither is jdarcy...
12:08:02 <ndevos> #topic Add distinction between "problem reports" and "enhancement requests"
12:08:21 <ndevos> nobody cared to respond to http://supercolony.gluster.org/pipermail/gluster-devel/2014-October/042569.html
12:08:48 <lalatenduM> ndevos, FEAT looks fine
12:08:51 <ndevos> so, I think we'll just document the FutureFeature keyword as marker
12:09:05 <ndevos> lalatenduM: why that, and not the keyword?
12:09:30 <lalatenduM> ndevos, I have seen this is been used in soem bugs
12:09:40 <ndevos> lalatenduM: so is the keyword :)
12:10:24 <ndevos> lalatenduM: any reason to not use the keyword?
12:10:35 <lalatenduM> ndevos, :) , keyword is better to manage , lets go with keyword
12:10:45 <ndevos> hchiramm_, overclk: got an opinion on that?
12:11:02 <hchiramm_> FutureFeature
12:11:20 <ndevos> okay, that settles it
12:11:29 <overclk> ndevos: I'll go with keyword.
12:11:30 <hchiramm_> its clear from that string..
12:11:59 <ndevos> #agreed We will use the FutureFeature for marking 'bugs' an enhancement request
12:12:41 <ndevos> #action ndevos should respond to the email with the decision
12:12:59 <ndevos> any one of you want to update the Bug Triage wiki page for this?
12:13:22 <ndevos> mainly http://www.gluster.org/community/documentation/index.php/Bug_triage#Keywords
12:13:46 <ndevos> overclk, hchiramm_, lalatenduM ?
12:13:52 <hchiramm_> I can
12:14:19 <ndevos> #action hchiramm_ will add the FutureFeature keyword to the Bug Triage wiki page
12:14:22 <ndevos> thanks!
12:14:43 <ndevos> #topic Group Triage
12:15:14 <ndevos> no bugs are waiting on needinfo from  gluster-bugs@redhat.com
12:15:27 <ndevos> but, maybe we should modify that to bugs@gluster.org too
12:16:30 <ndevos> I've updated the etherpad with the new link, we should update the wiki too
12:16:47 <ndevos> hchiramm_: can you update that when you add the keyword?
12:16:56 <hchiramm_> will do
12:17:30 <ndevos> #action hchiramm_ will update the Bug Triage page to reference the NEEDINFO for bugs@gluster.org
12:17:34 <ndevos> thanks :)
12:17:51 <hchiramm_> :)
12:18:15 <ndevos> #topic New bugs to triage (filed since last week)
12:18:34 <ndevos> we have several new bugs that need some triage: http://goo.gl/0IqF2q
12:19:35 <ndevos> I'll take care of the 'disperse' bugs, you should post here which bugs you want to triage :)
12:20:28 <lalatenduM> https://bugzilla.redhat.com/show_bug.cgi?id=1155421 , is a no brainer , a patch is already sent
12:20:51 <ndevos> hchiramm_: btw, did you look into getting xavih more bugzilla permissions?
12:21:08 <hchiramm_> ahh. my bad.. missed it..
12:21:12 <overclk> ndevos: bz #1156404 has a patch committed upstream (bz still is in NEW state)
12:21:19 <hchiramm_> I will check it soon..
12:24:35 <ndevos> overclk: just mark the bug as MODIFIED if the patch has been merged, and assign the bug to whoever posted the patch
12:27:08 <lalatenduM> For the bugs which are cloned from master to backport patches , does need much work right?
12:27:15 <lalatenduM> ndevos, ^^
12:28:07 <ndevos> lalatenduM: no, just add the Triaged + Patch keywords, maybe point out which patches need backporting in case there is more than one
12:31:44 <ndevos> lalatenduM: I just did something like that in bug 1157107
12:32:26 <lalatenduM> ndevos, ok
12:33:19 <ndevos> hchiramm_, overclk, lalatenduM: 3 bugs left in the list - which do you want to triage?
12:33:59 <lalatenduM> ndevos, https://bugzilla.redhat.com/show_bug.cgi?id=1156022
12:34:46 * ndevos takes https://bugzilla.redhat.com/show_bug.cgi?id=1156003
12:34:47 <overclk> lalatenduM: that could be related to one of the rebalance bugs
12:35:36 <lalatenduM> overclk, cool, is it already fixed in master?
12:35:50 <lalatenduM> overclk, you want to triage this bug?
12:36:01 <overclk> lalatenduM: better to check with shylesh.
12:36:11 <overclk> lalatenduM: yeh, I can take that.
12:36:31 <lalatenduM> overclk, cool, will take up the next bug
12:36:57 <lalatenduM> triaging https://bugzilla.redhat.com/show_bug.cgi?id=1155181
12:37:01 <ndevos> lalatenduM: that leaves 1155181
12:37:08 * hchiramm_ on a call
12:39:59 <ndevos> there are still many bugs that have not been triaged: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&f1=keywords&list_id=2954007&o1=nowords&product=GlusterFS&v1=Triaged
12:40:56 <ndevos> #info there are currently 339 bugs untriaged, we were close to 500 a while back, things look promising!
12:41:11 * ndevos wonders if there was a #info command...
12:41:42 <lalatenduM> who is the OSX maintainer for us?
12:42:02 <lalatenduM> do u guys think https://bugzilla.redhat.com/show_bug.cgi?id=1155181 is an easyfix gug
12:42:08 <lalatenduM> s/gug/bug/
12:42:30 <overclk> lalatenduM: harsha (y4m4) would be the one who you can get in touch with.
12:42:55 <lalatenduM> overclk, thanks
12:43:37 <ndevos> lalatenduM: hmm, so many warnings might not be easyfix
12:44:18 <lalatenduM> ndevos, agree
12:45:35 <ndevos> lalatenduM: comment #3 also makes it clear that the warnings can not be disabled as jclift suggests - so yeah, leave it for Harsha and mark it Triaged, they know what they need to do
12:45:57 <lalatenduM> ndevos, yeh
12:48:29 <lalatenduM> who is lookin in to https://bugzilla.redhat.com/show_bug.cgi?id=1156003
12:49:13 <ndevos> lalatenduM: I've put it on NEEDINFO(reporter)
12:49:31 <lalatenduM> ndevos, cool
12:49:34 <ndevos> lalatenduM: until we have more details, it is not finished with the triage yet
12:49:58 <lalatenduM> ndevos, cool, we should look at it again next week
12:50:09 <overclk> ndevos: just FYI, for bz #1156022, I'll check with the rebalance folks and update as required.
12:50:14 <ndevos> lalatenduM: this is not a weekly excersise!
12:50:24 <ndevos> overclk: cool, thanks
12:50:48 <ndevos> lalatenduM: I hope you (and others!) try to triage some bugs each day?
12:51:14 <lalatenduM> ndevos, I understand
12:51:15 <ndevos> I'm checking my RSS feeds in Thunderbird for 3.5 and nfs bugs regulary now
12:51:39 <ndevos> lalatenduM: what is your preference to check for bugs that need triage?
12:52:32 <lalatenduM> ndevos, mostly 2 to 3 days out of whole week
12:54:17 <lalatenduM> ndevos, as of now my thunderbird filter is in bad shape , all upstream and downstream bugs coming to one dir
12:54:22 <lalatenduM> need to fix that
12:55:50 <ndevos> lalatenduM: so, you are using the bugs@gluster.org list for receiving mails?
12:56:26 <lalatenduM> ndevos, I think it is gluster-bugs@redhat.com, I have not updated the filter
12:57:26 <ndevos> lalatenduM: oh, okay
12:59:15 <lalatenduM> ndevos, I followed http://www.gluster.org/community/documentation/index.php/Bugzilla_Notifications , unless it is updated recently
13:00:10 <ndevos> lalatenduM: yeah, that works, but that page also contains RSS feeds that may be easier to use
13:00:59 <lalatenduM> ndevos, should I watch  bugs@gluster.org instead of gluster-bugs@redhat.com
13:01:07 <lalatenduM> hchiramm, ^^
13:01:36 <ndevos> lalatenduM: yes, bugs@gluster.org should be used
13:01:42 <lalatenduM> cool
13:02:08 <ndevos> lalatenduM: if you find any references to the @redhat.com address, please update the docs :)
13:02:19 <lalatenduM> ndevos, ok
13:02:44 <ndevos> #topic Open Floor
13:03:00 <ndevos> Any other things we should discuss now?
13:03:51 <lalatenduM> none from me
13:04:27 <ndevos> okay, I guess that's it for today then
13:04:28 <kkeithley> nope
13:04:37 <ndevos> #endmeeting