gluster-meeting
MINUTES

#gluster-meeting Meeting

Meeting started by ndevos at 12:01:27 UTC (full logs).

Meeting summary

  1. Roll Call (ndevos, 12:01:44)
  2. hchiramm to create/request a bugs@gluster.org mailinglist and have it as default assignee of any Gluster product bug (ndevos, 12:05:12)
    1. ACTION: hchiramm to create/request a bugs@gluster.org mailinglist and have it as default assignee of any Gluster product bug (ndevos, 12:06:04)

  3. ndevos to describe how to 'watch' gluster-bugs@redhat.com and filter email (ndevos, 12:06:11)
    1. AGREED: ndevos to create a wiki page to describe how to 'watch' gluster-bugs@redhat.com and filter email (ndevos, 12:08:19)

  4. hchiramm to create "doc" component under GlusterFS in bugzilla (ndevos, 12:08:30)
    1. ACTION: hchiramm to create "doc" component under GlusterFS in bugzilla (ndevos, 12:09:10)

  5. ndevos to prepare some bugzilla queries that show untriaged bugs per component(-group) (ndevos, 12:09:23)
    1. ACTION: lalatenduM will add bugzilla queries (per component) to the Bug triage wiki page (ndevos, 12:19:44)

  6. Group Triage (ndevos, 12:20:27)
    1. ACTION: lalatenduM requests iptables, df, SElinux and logs for bug 1109613 (ndevos, 12:38:11)
    2. https://bugzilla.redhat.com/show_bug.cgi?id=1136349 (lalatenduM, 12:39:19)
    3. ACTION: lalatenduM asks the reporter of bug 1136349 to: a. make the private comments public, or b. post a summary that explains the issue/situation (ndevos, 12:45:03)
    4. IDEA: we should create a "how to clone" best practises wiki page if we do not have one yet (ndevos, 12:48:38)
    5. http://www.gluster.org/community/documentation/index.php/Bug_triage#Bugs_present_in_multiple_Versions (lalatenduM, 12:49:31)
    6. ACTION: hchiramm will split the Bug Triage page into smaller ones, starting with a "How to clone" best practise (ndevos, 12:51:48)

  7. Open Floor (ndevos, 12:54:59)
    1. https://bugzilla.redhat.com/show_bug.cgi?id=969020 (lalatenduM, 12:55:36)
    2. ACTION: ndevos to add a bugzilla query with untriaged bugs that have been filed in the last week (ndevos, 12:57:08)
    3. IDEA: if you need a bug triaged by the group during this meeting, set NEEDINFO for gluster-bugs@redhat.com (ndevos, 13:01:15)
    4. ACTION: ndevos to create a bugzilla query to list the NEEDINFO gluster-bugs@redhat.com for group triage (ndevos, 13:02:01)
    5. ACTION: lalatenduM will update the Bug Triage page to mark bugs for group triage (NEEDINFO on gluster-bugs@redhat.com) (ndevos, 13:03:18)


Meeting ended at 13:04:06 UTC (full logs).

Action items

  1. hchiramm to create/request a bugs@gluster.org mailinglist and have it as default assignee of any Gluster product bug
  2. hchiramm to create "doc" component under GlusterFS in bugzilla
  3. lalatenduM will add bugzilla queries (per component) to the Bug triage wiki page
  4. lalatenduM requests iptables, df, SElinux and logs for bug 1109613
  5. lalatenduM asks the reporter of bug 1136349 to: a. make the private comments public, or b. post a summary that explains the issue/situation
  6. hchiramm will split the Bug Triage page into smaller ones, starting with a "How to clone" best practise
  7. ndevos to add a bugzilla query with untriaged bugs that have been filed in the last week
  8. ndevos to create a bugzilla query to list the NEEDINFO gluster-bugs@redhat.com for group triage
  9. lalatenduM will update the Bug Triage page to mark bugs for group triage (NEEDINFO on gluster-bugs@redhat.com)


Action items, by person

  1. hchiramm
    1. hchiramm to create/request a bugs@gluster.org mailinglist and have it as default assignee of any Gluster product bug
    2. hchiramm to create "doc" component under GlusterFS in bugzilla
    3. hchiramm will split the Bug Triage page into smaller ones, starting with a "How to clone" best practise
  2. lalatenduM
    1. lalatenduM will add bugzilla queries (per component) to the Bug triage wiki page
    2. lalatenduM requests iptables, df, SElinux and logs for bug 1109613
    3. lalatenduM asks the reporter of bug 1136349 to: a. make the private comments public, or b. post a summary that explains the issue/situation
    4. lalatenduM will update the Bug Triage page to mark bugs for group triage (NEEDINFO on gluster-bugs@redhat.com)
  3. ndevos
    1. ndevos to add a bugzilla query with untriaged bugs that have been filed in the last week
    2. ndevos to create a bugzilla query to list the NEEDINFO gluster-bugs@redhat.com for group triage


People present (lines said)

  1. ndevos (102)
  2. lalatenduM (61)
  3. elico (29)
  4. hagarth (18)
  5. hchiramm (13)
  6. jdarcy (10)
  7. kkeithley (8)
  8. glusterbot (6)
  9. zodbot (2)
  10. Thilam (2)


Generated by MeetBot 0.1.4.