12:00:58 <ndevos> #startmeeting
12:00:59 <zodbot> Meeting started Tue Oct 21 12:00:58 2014 UTC.  The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:59 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:01:14 <ndevos> welcome all, agenda is at https://public.pad.fsfe.org/p/gluster-bug-triage
12:01:23 <ndevos> #topic Roll Call
12:01:32 * kkeithley_ is here
12:01:38 <ndevos> please raise your hand when you're attending this meeting
12:01:44 * ndevos _o/
12:02:38 * overclk is here
12:02:54 * lalatenduM is here
12:03:59 <ndevos> okay, we seem to have some people here now, good!
12:04:24 <ndevos> #topic Status of last weeks action items
12:04:53 <ndevos> #topic hchiramm to make sure that bugs@gluster.org becomes the default owner of new bugs
12:05:00 <ndevos> Humble: I guess that has been done?
12:05:13 <Humble> ndevos, I am not sure it is possible , however checking with bugzilla team
12:05:36 <Humble> I mean default Cc list has bugs@gluster.org , but not default assignee
12:06:00 <ndevos> #action Humble checks with the Bugzilla team if bugs@gluster.org can become the default owner of bugs
12:06:05 <ndevos> #topic     hchiramm will split the Bug Triage page into smaller ones, starting with a "How to clone" best practise
12:06:27 <Humble> not sure what else we need to be documented separately .. any thoughts?
12:06:34 <Humble> to be documented/document
12:06:35 <ndevos> Humble: you did the "how to clone" bit, maybe other topics could do too?
12:07:06 <Humble> I am not sure what comes in 'other topics' . any thoughts ?
12:07:10 <ndevos> http://www.gluster.org/community/documentation/index.php/Bug_triage is the big page that could become smaller
12:08:11 <Humble> yep, I was looking at it  and got a feel that , its better to be in a document..
12:08:19 <ndevos> I also do not know what we could move out of there, maybe the component list?
12:08:20 <Humble> so that u can fetch all the information in one shot
12:08:25 <Humble> Isnt it ?
12:09:07 <ndevos> is there nobody with any ideas or advice/suggestions on this topic?
12:09:09 <lalatenduM> Lengthy documents are difficult to go through, so we should make it short
12:09:22 <Humble> lalatenduM, then please suggest what has to be split
12:09:52 <lalatenduM> Humble, sure I can do that, we can take that for later discussion
12:10:04 <ndevos> #action lalatenduM will think about splitting the "Bug Triage" wiki page, and make suggestions later
12:10:09 <Humble> :)
12:10:11 <lalatenduM> :)
12:10:18 <Humble> ndevos++ thanks
12:10:21 <ndevos> #topic hchiramm_ to include a suggestion to assign a clone of a bug (and keep/add bugs@gluster.org on CC) in his 'how to clone' steps
12:10:23 <Humble> lalatenduM++
12:10:43 <ndevos> Humble: do you remember if you did that?
12:10:59 <Humble> not yet, because
12:11:24 <Humble> if the default assignee is bugs@gluster.org , even in the clone scenario it remains
12:11:29 <ndevos> Humble: hmm, but http://www.gluster.org/community/documentation/index.php/How_to_clone seems to have something about it in the "Best practises"?
12:12:05 <ndevos> oh. could it be that not everyone can assign bugs to someone else?
12:12:25 <Humble> can .. but by default it will be assigned to bugs/gluster-bugs..
12:12:31 * ndevos seems to be able to do that, but others mentioned they could not find the option
12:12:44 <ndevos> the default is OK
12:12:44 * Humble not sure who failed there ?
12:13:05 <ndevos> I think that was xavih
12:13:20 <Humble> xavih, Is it ? :)
12:13:36 <ndevos> he might be having lunch ;)
12:13:47 <Humble> :)
12:14:40 <ndevos> well, I do not think we need to add something to the wiki page anymore, I'm happy the way it currently is
12:14:47 <Humble> even I am
12:14:53 <ndevos> #topic Humble and ndevos will figure out how to get "a report on how many bugs exist in each version of glusterfs
12:14:59 <Humble> thanks for ur help to make it good
12:15:06 <ndevos> Is this what we want? http://goo.gl/VxQPwc
12:15:11 <Humble> ndevos, not exatcly
12:15:25 <ndevos> okay, so what do we want?
12:15:26 <Humble> the page talks the "priority" lsiting
12:15:37 <Humble> is nt it better to have it in "status" ?
12:16:01 <Humble> so that we have the idea of how many bugs were reported and closed in each release ?
12:16:10 <ndevos> Humble: not sure, but we can change that
12:16:15 <Humble> cool ..
12:16:19 <Humble> that what I think
12:16:29 <Humble> but others can pitch in with their thoughts
12:16:39 <ndevos> like this: https://bugzilla.redhat.com/report.cgi?x_axis_field=bug_status&y_axis_field=version&z_axis_field=product&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=GlusterFS&bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=
12:17:00 <ndevos> or a little easier: http://goo.gl/IA7zaq
12:17:32 <Humble> looks good !!!!
12:17:44 <ndevos> hmm, we have some ON_DEV bugs, that is a status we do not use!
12:18:15 <Humble> negligible count
12:18:27 <ndevos> #agreed http://goo.gl/IA7zaq is a useful report for the number of bugs per Gluster version
12:18:43 <lalatenduM> can we close bugs for versions which are not supported now
12:18:44 <lalatenduM> ?
12:18:46 <ndevos> each bug is important, we should look at those and fix the status
12:19:07 <Humble> true ..
12:19:13 <Humble> we cant just close them
12:19:19 <ndevos> lalatenduM: depends, if the bug would still be in the master branch, you rather should change the version
12:19:50 <ndevos> lalatenduM: some bugs will have been closed, and then you can close them as a duplicate of the fix
12:19:53 <lalatenduM> ndevos, I understand
12:20:05 <kkeithley_> 3.3-beta, 3.4.0-{alpha,beta}, pre-2.0, pre-release?
12:20:26 <kkeithley_> 213 bugs filed against pre-release. Whatever that is
12:20:50 <ndevos> yeah, those versions are difficult to work with, personally I'd prefer to see a 3.5 version, and no 3.5.x
12:20:57 <lalatenduM> we have 100 bugs for 3.6.0
12:21:09 <lalatenduM> we did so much testing of betas?
12:21:29 <ndevos> probably done for backports
12:21:48 <Humble> probbaly by default the version is 3.6
12:21:49 <Humble> ?
12:22:11 <ndevos> no, the default should be mainline, and most 3.6 bugs are ON_QA
12:22:12 <lalatenduM> ndevos, may be
12:22:19 <Humble> yeah, its mainline
12:22:40 <lalatenduM> ndevos, most of them are on on_qa
12:23:13 <Humble> Isnt it good ? :)
12:23:20 <ndevos> lalatenduM: you're the qa guy, I guess there is work to do :D
12:23:45 <Humble> :P
12:23:51 <lalatenduM> :)
12:23:51 <ndevos> but well, these details do not really matter to us now, we've got an agenda to keep!
12:23:56 <ndevos> #topic     EVERYONE to review http://www.gluster.org/community/documentation/index.php/How_to_clone and give feedback to Humble, or update the page themselves
12:24:07 <kkeithley_> Humble: next time you have BZ people make changes, please have them add 3.4.7 to Target Milestone
12:24:21 <ndevos> is there anyone who did read the page?
12:24:38 <Humble> ok.. I already have a request for bugs@gluster.org , may be I will try to include this as well in the same . kkeithley_
12:25:14 * kkeithley_ read it once, a long time ago. ;-)
12:25:36 <ndevos> it can not be *that* long ago, the page is relatively new
12:26:05 <ndevos> overclk, lalatenduM: did you read that page yet?
12:26:50 <Humble> yep :)
12:26:53 <lalatenduM> ndevos, nope
12:26:56 <ndevos> kkeithley_: anything you can comment on?
12:27:22 <lalatenduM> will do that
12:27:26 <kkeithley_> "long time" being a relative term.   No, I was not unhappy with it.
12:27:33 <ndevos> if nobody feels like improving it, we'll just mark it as done
12:27:34 <Humble> kkeithley_, :)
12:27:55 <ndevos> #agreed The "How to clone" wiki page should be fine as it is
12:27:59 <ndevos> #topic hagarth will look for somebody that can act like a bug assigner manager kind of person
12:28:05 <lalatenduM> ndevos, agree
12:28:09 <hagarth> ndevos: still working on that
12:28:19 <hagarth> ndevos: can carry forward that AI
12:28:20 <ndevos> hagarth: okay, thanks
12:28:27 <ndevos> #action hagarth will look for somebody that can act like a bug assigner manager kind of person
12:28:42 <ndevos> #topic pranithk to report how his team is assigning triaged bugs
12:28:50 <ndevos> hmm, pranith just dropped off :-/
12:29:20 <ndevos> and jdarcy isnt there either...
12:29:27 <hagarth> ndevos: pranithk is a bit sick today and there have been consecutive tuesdays that have been off in BLR
12:29:43 <ndevos> hagarth: no problem
12:29:46 <hagarth> ndevos: we can probably remind pranithk again next week before the meeting
12:29:58 <ndevos> hagarth: yeah, I will :)
12:30:35 <ndevos> overclk, hagarth: did you guys use any of the Bugzilla Notifications to track new bugs?
12:31:00 <ndevos> like, the bugs@gluster.org list with some mail filters, or the RSS-feeds?
12:31:07 <hagarth> ndevos: yes, I am on the ML
12:31:17 <ndevos> http://www.gluster.org/community/documentation/index.php/Bugzilla_Notifications#RSS_Feeds
12:31:21 <hagarth> and use some filters to check for new bugs
12:31:49 <overclk> hagarth, I've to start that.. :)
12:31:59 <ndevos> hagarth: okay, but do you know of any preferences of others?
12:32:23 <hagarth> I also have a daily whine that sends me an email about bugs logged the previous day
12:32:30 <ndevos> overclk: are you more of a mailinglist or RSS-feed person?
12:32:43 <overclk> ndevos, ML
12:33:07 <ndevos> hagarth: yes, I imagine you do, but we'd prefer something that anyone from the community can use too
12:33:22 <ndevos> and, hopefully a little filtered, somehow
12:33:46 <hagarth> ndevos: +1 for a twitter feed ;)
12:33:55 <ndevos> overclk: okay, so bugs@gluster.org and filtering on the X-Bugzilla-* headers works for you?
12:34:05 <ndevos> twitter feed?!
12:34:25 <overclk> ndevos, yep, that would do for me.
12:34:31 <hagarth> we do have a twitter feed for all patches committed (@glusterdev)
12:34:35 <ndevos> there was the request for a weekly blog post...
12:35:02 <hagarth> maybe we should start a weekly news letter and have a section on bugs too
12:35:39 <hagarth> but this rss feed is also pretty cool
12:35:54 <ndevos> a twitter feed is a little difficult to filter, how would components and bug status be shown... like marked as 'Triaged', or 'EasyFix'
12:36:33 <ndevos> we should be able to separate the new bugs, and triaged bugs somehow
12:36:39 <ndevos> new bugs for the bug triagers
12:36:46 <hagarth> we can format the message .. but let us not worry about twitter right now
12:36:50 <ndevos> and triaged bugs for the developers and sub-maintainers
12:37:37 <ndevos> for that the RSS_feed is pretty nice, triagers can even pick a stream for a component they are interested in
12:37:40 <hagarth> ndevos: right
12:38:26 <ndevos> I would like to not overwhelmi new contributors with *all* bugs that get filed
12:38:50 <ndevos> #topic Add distinction between "problem reports" and "enhancement requests"
12:38:58 <ndevos> How can we adapt our Bug Triage guidelines to mark bugs as a "problem report" or "enhancement request"
12:39:06 <ndevos> http://supercolony.gluster.org/pipermail/gluster-devel/2014-October/042569.html for [FEAT] 'tag' or FutureFeature keyword
12:39:24 <hagarth> don't we have anything in severity to indicate that?
12:39:42 <ndevos> not really, at least I do not think so
12:40:14 <ndevos> there is the 'Doc Type
12:40:21 <hagarth> ndevos: right, we used to have in gluster bugzilla IIRC
12:40:29 <hagarth> ndevos: I like the keyword idea
12:40:50 <ndevos> I most of us are in favour of the keyword
12:41:09 <ndevos> but there are quite some bugs with the [FEAT] tag in them too
12:42:05 <ndevos> #agreed leave the email for 'FutureFeature' keyword or '[FEAT]' open for a few days
12:42:25 <hagarth> ndevos: +1
12:42:33 <ndevos> #topic Group Triage
12:42:49 <ndevos> nobody added bugs to the list, so thats good
12:42:52 <ndevos> I think
12:43:16 <hagarth> ndevos: like "no news is good news"? :)
12:43:30 <ndevos> no bugs are waiting on gluster-bugs@redhat.com either
12:44:01 <kkeithley_> FWIW, that list you gave me of 3.4 bugs last week, I got down to 81 bugs from 100+. I'm still working on it
12:44:03 <ndevos> yes, no news is good news, people can add their most urgent bugs, but if they do not, I assume they are happy
12:44:15 <ndevos> kkeithley_: awesome!
12:44:31 <lalatenduM> :)
12:44:52 <ndevos> #topic bugs files since last week
12:44:53 <hagarth> kkeithley_++
12:44:57 <ndevos> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&chfield=[Bug creation]&chfieldfrom=-1w&chfieldto=Now&f1=keywords&o1=notsubstring&product=GlusterFS&v1=Triaged
12:45:18 <ndevos> there are 12 of them - that do not have the Triaged keyword yet
12:46:17 <ndevos> please have a look at some, I'll take the disperse ones ;)
12:47:39 <ndevos> bugs that have patches posted, should be moved to POST - that is sufficient, no need to set the Triaged keyword
12:47:52 <ndevos> just maybe assign the bug to whoever posted the patch
12:48:05 <hagarth> ndevos: right
12:53:21 <hagarth> oops, almost ended up overwriting ndevos' changes for 1154491
12:53:59 <ndevos> oh, go ahead :)
12:54:40 <ndevos> we can continue the exersice after the meeting
12:54:51 <ndevos> unless someone found a bug that needs some discussion?
12:55:05 <ndevos> Humble, kkeithley_, lalatenduM, overclk: ?
12:55:14 <lalatenduM> none from me
12:55:52 <kkeithley_> found a bug? No, but there are three or four that have been languishing
12:55:59 <ndevos> 4 left in the list, the chance on mid-air collisions is increasing!
12:56:23 <ndevos> #topic Open Floor
12:56:37 <ndevos> so, a few minutes to discuss *your* topic?
12:57:51 <Humble> ndevos, before we close, the default assignee is changed to bugs@gluster.org
12:58:36 <ndevos> Humble: oh, cool!
12:58:55 <lalatenduM> Humble++
12:59:02 <ndevos> Humble: so, we could drop the gluster-bugs@redhat.com list everywhere now?
12:59:20 <Humble> looks like :)
12:59:32 <kkeithley_> oh, btw, although it's probably more suitable for tomorrow's meeting, there's now a 3.4.7 tracker bug. I moved a couple bugs from the 3.4.6 tracker to it
12:59:58 <ndevos> Humble: can you check that, and update the bugs that have gluster-bugs@redhat.com in CC/assigned?
13:00:26 <Humble> ndevos, I had asked them to keep gluster-bugs in Cc list for a backup
13:00:29 <ndevos> Humble: and, send a note to the gluster-bugs@redhat.com list so that there is a record that it is depricated?
13:00:56 <Humble> but in all the docs we will mention "bugs@gluster.org"
13:01:05 <Humble> we can just forget about gluster-bugs
13:01:20 <ndevos> Humble: oh, hmm, not sure if we need a backup when it always will have bugs@gluster.org in CC and assignee by default?
13:01:54 <Humble> its other way around, bugs@gluster.org as the default assignee and gluster-bugs@ in Cc list
13:02:38 <hagarth> Humble: maybe we should send a note on gluster MLs and provide a link to the mailman page for bugs@gluster.org
13:02:48 <ndevos> Humble: uh, okay, but bugs@gluster.org should always be on CC - is that still the case?
13:02:57 <Humble> should not be any more ndevos
13:02:58 <Humble> hagarth, yep
13:03:44 <ndevos> Humble: hmm, so if I file a new bug, and assign it to you while reporting it, bugs@gluster.org does not get an email, but the old list does?
13:04:41 <Humble> ok.. let me make it clear  :) .. previously when u report a bug , the default assignee was gluster-bugs and later we asked bugs@gl in Cc list for all the bugs
13:04:45 <ndevos> Humble: ah, no, it seems that (at least for the 'build' component) that bugs@ and gluster-bugs@ are *both* on CC
13:05:04 <Humble> now the default assignee is bugs@gluster
13:05:29 <ndevos> yes, that is good - gluster-bugs@redhat.com should get completely removed one day
13:05:34 <Humble> yep
13:05:46 <Humble> we can think about it when we have proper assignee per component
13:06:13 <ndevos> and, as long as bugs@gluster.org is always on CC (and/or assignee), things will work out just fine
13:06:23 <Humble> yep .. till then this should serve I feel ..
13:06:33 <ndevos> yes, it should
13:07:04 <ndevos> anyone that is interested in receiving notifications has multiple ways of getting and filtering them
13:07:17 <ndevos> there should not be a need for a
13:07:23 <ndevos> assignee per component
13:08:10 <ndevos> that just makes that person a bottleneck, and it gives the community more difficulties in triaging bugs - as it is different from other components
13:08:37 <Humble> hagarth, do we need  a seperate mail about subscribing bugs@gluster.org , or it should be part of some doc ?
13:08:38 <ndevos> was there anything I missed, and we should discuss before ending the meeting?
13:09:06 <Humble> http://gluster.org/mailman/listinfo/bugs -> link to subscribe
13:09:07 <ndevos> Humble: its in the bug-notifications wiki page, you can link that from your email
13:09:10 <xavih> ndevos: I was out, sorry. Regarding self-assigning bugzilla bugs, I still cannot do it (the link does not appear). Once a bug is assigned to me I can see and do much more things
13:09:24 <ndevos> Humble: see!
13:09:28 <ndevos> xavih: thanks :)
13:10:07 <Humble> ndevos, not sure any restriction exist for outside redhat email address.
13:10:10 * ndevos thinks that assigning bugs needs some ACL setting in bugzilla...
13:10:11 <hagarth> Humble: a mail and doc would be even better
13:10:19 <Humble> hagarth, ok ..
13:10:38 <Humble> ndevos, I will check with bugzilla team
13:10:50 <ndevos> Humble: no, I think it has to do with being a package maintainer, team-lead or manager or something
13:10:53 <Humble> xavih++ , thanks for pointing out !
13:11:19 <xavih> Humble: no problem :)
13:11:20 <Humble> ndevos, but I am not sure how it matter to self assign a bug
13:11:26 <ndevos> Humble: I do not think you need to check that, xavih can poke us for his bugs
13:11:53 <Humble> ndevos, if he can do himself , why the poke :)
13:11:55 <ndevos> or, we just assign them to him when we triage some bugs :)
13:12:36 <ndevos> Humble: getting the permissions might be difficult - but well, if you want to take care of that :)
13:12:48 <Humble> ndevos, I can cross check any way
13:12:50 <Humble> lets see.
13:12:58 <Humble> other ways we will traige for him :)
13:13:01 <Humble> thanks..
13:13:03 <ndevos> sure, and keep us informed :)
13:13:06 <ndevos> #endmeeting