[Gluster-users] Minutes from Gluster Bug Triage meeting today

2017-04-04 Thread Saravanakumar Arumugam 

Hi,

Thanks all who joined!

Next week at the same time (Tuesday 12:00 UTC) we will have an other bug
triage meeting to catch the bugs that were not handled by developers and
maintainers yet. We'll stay repeating this meeting as safety net so that
bugs get the initial attention and developers can immediately start
working on the issues that were reported.

Bug triaging (in general, no need to only do it during the meeting) is
intended to help developers, in the hope that developers can focus on
writing bug fixes instead of spending much of their valued time
troubleshooting incorrectly/incompletely reported bugs.

More details about bug triaging can be found here:
http://gluster.readthedocs.io/en/latest/Contributors-Guide/Bug-Triage/

Meeting minutes below.

Thanks,
Saravana



Meeting summary

agenda:https://github.com/gluster/glusterfs/wiki/Bug-Triage-Meeting 
(Saravanakmr, 12:01:02)


Roll call (Saravanakmr, 12:01:08)

Next week’s meeting host (Saravanakmr, 12:03:18)
ACTION: skumar will host next week's meeting (Saravanakmr, 
12:04:12)


ndevos need to decide on how to provide/use debug builds 
(Saravanakmr, 12:04:42)
ACTION: ndevos need to decide on how to provide/use debug 
builds (Saravanakmr, 12:05:17)


jiffin needs to send the changes to check-bugs.py also 
(Saravanakmr, 12:05:26)
ACTION: jiffin needs to send the changes to check-bugs.py also 
(Saravanakmr, 12:06:01)

http://bit.ly/gluster-bugs-to-triage (Saravanakmr, 12:06:14)

open floor (Saravanakmr, 12:14:04)


Meeting ended at 12:14:30 UTC (full logs).

Action items

skumar will host next week's meeting
ndevos need to decide on how to provide/use debug builds
jiffin needs to send the changes to check-bugs.py also



Action items, by person

jiffin
jiffin needs to send the changes to check-bugs.py also
ndevos
ndevos need to decide on how to provide/use debug builds
skumar
skumar will host next week's meeting


People present (lines said)

Saravanakmr (35)
rafi (8)
skumar (6)
zodbot (5)
jiffin (4)
ndevos (3)
kkeithley (3)
hgowtham (1)

___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Minutes from Gluster Bug Triage meeting today

2017-02-21 Thread Saravanakumar Arumugam 

Hi,

Thanks all who joined!

Next week at the same time (Tuesday 12:00 UTC) we will have an other bug
triage meeting to catch the bugs that were not handled by developers and
maintainers yet. We'll stay repeating this meeting as safety net so that
bugs get the initial attention and developers can immediately start
working on the issues that were reported.

Bug triaging (in general, no need to only do it during the meeting) is
intended to help developers, in the hope that developers can focus on
writing bug fixes instead of spending much of their valued time
troubleshooting incorrectly/incompletely reported bugs.

More details about bug triaging can be found here:
http://gluster.readthedocs.io/en/latest/Contributors-Guide/Bug-Triage/

Meeting minutes below.

Thanks,
Saravana



Meeting summary


Agenda:https://github.com/gluster/glusterfs/wiki/Bug-Triage-Meeting 
(Saravanakmr, 12:00:38)


Roll call (Saravanakmr, 12:00:44)
Next week’s meeting host (Saravanakmr, 12:01:52)
ACTION: jiffin will host on 28 February (Saravanakmr, 12:04:03)

Action items (Saravanakmr, 12:04:36)
ndevos need to decide on how to provide/use debug builds 
(Saravanakmr, 12:04:48)
ACTION: ndevos need to decide on how to provide/use debug 
builds (Saravanakmr, 12:05:04)


jiffin needs to send the changes to check-bugs.py also 
(Saravanakmr, 12:05:09)
ACTION: jiffin needs to send the changes to check-bugs.py also 
(Saravanakmr, 12:05:30)


Group Triage (Saravanakmr, 12:05:38)
you can find the bugs to triage here in 
http://bit.ly/gluster-bugs-to-triage (Saravanakmr, 12:05:43)
https://gluster.readthedocs.io/en/latest/Contributors-Guide/Bug-Triage/ 
(Saravanakmr, 12:05:49)


Open Floor (Saravanakmr, 12:15:11)



Meeting ended at 12:16:12 UTC (full logs).

Action items

jiffin will host on 28 February
ndevos need to decide on how to provide/use debug builds
jiffin needs to send the changes to check-bugs.py also



Action items, by person

jiffin
jiffin will host on 28 February
jiffin needs to send the changes to check-bugs.py also
ndevos
ndevos need to decide on how to provide/use debug builds



People present (lines said)

Saravanakmr (34)
jiffin (5)
ndevos (5)
zodbot (3)
kkeithley (3)
rafi (3)
skoduri (1)


___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Minutes from Gluster Bug Triage meeting today

2017-01-17 Thread Saravanakumar Arumugam 

Hi,

Thanks all who joined!

Next week at the same time (Tuesday 12:00 UTC) we will have an other bug
triage meeting to catch the bugs that were not handled by developers and
maintainers yet. We'll stay repeating this meeting as safety net so that
bugs get the initial attention and developers can immediately start
working on the issues that were reported.

Bug triaging (in general, no need to only do it during the meeting) is
intended to help developers, in the hope that developers can focus on
writing bug fixes instead of spending much of their valued time
troubleshooting incorrectly/incompletely reported bugs.

More details about bug triaging can be found here:
http://gluster.readthedocs.io/en/latest/Contributors-Guide/Bug-Triage/

Meeting minutes below.

Thanks,
Saravana



Meeting summary
agenda:https://github.com/gluster/glusterfs/wiki/Bug-Triage-Meeting 
(Saravanakmr, 12:00:24)


Roll call (Saravanakmr, 12:00:31)
Next week’s meeting host (Saravanakmr, 12:03:39)

ndevos need to decide on how to provide/use debug builds (Saravanakmr, 
12:06:15)
ACTION: ndevos need to decide on how to provide/use debug builds 
(Saravanakmr, 12:06:27)


jiffin needs to send the changes to check-bugs.py also (Saravanakmr, 
12:06:47)
ACTION: jiffin needs to send the changes to check-bugs.py also 
(Saravanakmr, 12:07:23)


Group Triage (Saravanakmr, 12:08:13)
you can find the bugs to triage here 
inhttp://bit.ly/gluster-bugs-to-triage (Saravanakmr, 12:08:21)

http://bit.ly/gluster-bugs-to-triage (Saravanakmr, 12:08:53)

Open Floor (Saravanakmr, 12:16:01)


Meeting ended at 12:18:53 UTC (full logs).

Action items
ndevos need to decide on how to provide/use debug builds
jiffin needs to send the changes to check-bugs.py also


Action items, by person
jiffin needs to send the changes to check-bugs.py also
ndevos need to decide on how to provide/use debug builds


People present (lines said)
Saravanakmr (40)
ndevos (9)
kkeithley (5)
skoduri (3)
jiffin (3)
zodbot (3)

___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Minutes from Gluster Bug Triage meeting today

2016-12-06 Thread Saravanakumar Arumugam 

Hi,

Thanks all who joined!

Next week at the same time (Tuesday 12:00 UTC) we will have an other bug
triage meeting to catch the bugs that were not handled by developers and
maintainers yet. We'll stay repeating this meeting as safety net so that
bugs get the initial attention and developers can immediately start
working on the issues that were reported.

Bug triaging (in general, no need to only do it during the meeting) is
intended to help developers, in the hope that developers can focus on
writing bug fixes instead of spending much of their valued time
troubleshooting incorrectly/incompletely reported bugs.

More details about bug triaging can be found here:
http://gluster.readthedocs.io/en/latest/Contributors-Guide/Bug-Triage/

Meeting minutes below.

Thanks,
Saravana


Meeting summary :

agenda: https://public.pad.fsfe.org/p/gluster-bug-triage(Saravanakmr 
, 
12:00:20)



1. *Roll call*(Saravanakmr
   
,
   12:00:30)
2. *Next week’s meeting host*(Saravanakmr
   
,
   12:03:19)
3. **/ACTION/:ndevos need to decide on how to provide/use debug
   builds(Saravanakmr
   
,
   12:06:11)
4. /ACTION/:jiffin will try to add an error for bug ownership to
   check-bugs.py(Saravanakmr
   
,
   12:07:14)


1. *hgowtham to close all 3.6 bugs as 3.9 is out; after the discussion
   on the devel list*(Saravanakmr
   
,
   12:07:45)
1. 
http://www.gluster.org/pipermail/gluster-devel/2016-December/051623.html(Saravanakmr
   
,
   12:09:25)

2. *Group Triage*(Saravanakmr
   
,
   12:10:07)
1. you can find the bugs to triage here in
   https://public.pad.fsfe.org/p/gluster-bugs-to-triage(Saravanakmr
   
,
   12:10:16)

3. *Open Floor*(Saravanakmr
   
,
   12:17:47)


Meeting ended at 12:18:32 UTC (full logs 
).



 Action items

1. ndevos need to decide on how to provide/use debug builds
2. jiffin will try to add an error for bug ownership to check-bugs.py


Action items, by person

1. jiffin
1. jiffin will try to add an error for bug ownership to check-bugs.py


 People present (lines said)

1. Saravanakmr (38)
2. hgowtham (14)
3. anraj (5)
4. zodbot (3)
5. ankitraj (2)
6. jiffin (2)

 Meeting ended Tue Dec  6 12:18:32 2016 UTC. Information about 
MeetBot at http://wiki.debian.org/MeetBot .
 Minutes: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-12-06/gluster_bug_triage.2016-12-06-12.00.html
 Minutes (text): 
https://meetbot.fedoraproject.org/gluster-meeting/2016-12-06/gluster_bug_triage.2016-12-06-12.00.txt
 Log: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-12-06/gluster_bug_triage.2016-12-06-12.00.log.html




___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Minutes from Gluster Bug Triage meeting today

2016-09-13 Thread Saravanakumar Arumugam 

Hi,

Thanks all who joined!

Next week at the same time (Tuesday 12:00 UTC) we will have an other bug
triage meeting to catch the bugs that were not handled by developers and
maintainers yet. We'll stay repeating this meeting as safety net so that
bugs get the initial attention and developers can immediately start
working on the issues that were reported.

Bug triaging (in general, no need to only do it during the meeting) is
intended to help developers, in the hope that developers can focus on
writing bug fixes instead of spending much of their valued time
troubleshooting incorrectly/incompletely reported bugs.

More details about bug triaging can be found here:
http://gluster.readthedocs.io/en/latest/Contributors-Guide/Bug-Triage/

Meeting minutes below.

Thanks,
Saravana

==
Meeting summary :

agenda: https://public.pad.fsfe.org/p/gluster-bug-triage 
(Saravanakmr, 12:00:50)


Roll call (Saravanakmr, 12:01:02)
Next weeks meeting host (Saravanakmr, 12:04:25)
ACTION: Next weeks meeting host hgowtham (Saravanakmr, 12:06:11)
skoduri hosts the meeting on 27 September (ndevos, 12:06:12)

ndevos need to decide on how to provide/use debug builds 
(Saravanakmr, 12:07:16)
ACTION: ndevos need to decide on how to provide/use debug 
builds (Saravanakmr, 12:07:57)


jiffin will try to add an error for bug ownership to check-bugs.py 
(Saravanakmr, 12:08:15)
ACTION: jiffin will try to add an error for bug ownership to 
check-bugs.py (Saravanakmr, 12:09:03)


Group Triage (Saravanakmr, 12:09:23)
you can fine the bugs to triage here in 
https://public.pad.fsfe.org/p/gluster-bugs-to-triage (Saravanakmr, 12:09:32)
http://www.gluster.org/community/documentation/index.php/Bug_triage Bug 
triage guidelines can be found here ^^ (Saravanakmr, 12:09:44)


Open Floor (Saravanakmr, 12:21:14)



Meeting ended at 12:22:13 UTC (full logs).

Action items

Next weeks meeting host hgowtham
ndevos need to decide on how to provide/use debug builds
jiffin will try to add an error for bug ownership to check-bugs.py



Action items, by person

hgowtham
Next weeks meeting host hgowtham
jiffin
jiffin will try to add an error for bug ownership to check-bugs.py
ndevos
ndevos need to decide on how to provide/use debug builds



People present (lines said)

Saravanakmr (34)
skoduri (8)
ndevos (7)
hgowtham (7)
zodbot (3)
jiffin (1)
kkeithley (1)
==
Minutes: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-09-13/gluster_bug_triage.2016-09-13-12.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/gluster-meeting/2016-09-13/gluster_bug_triage.2016-09-13-12.00.txt
Log: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-09-13/gluster_bug_triage.2016-09-13-12.00.log.html




___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users