[opensuse-project] openSUSE Project Meeting Minutes
Meeting started by sysrich at 15:00:35 UTC. The full logs are available at http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-projec... . Meeting summary --------------- * Action Item Review (sysrich, 15:04:10) * No action items from last meeting (sysrich, 15:04:18) * Non-publically accessible Bug Reports (sysrich, 15:04:40) * PJessen wrote the following into the openSUSE Project Meeting Agenda - Proposed change in Bugzilla policy wrt duplicates of non-publicly accessible reports. See my posting to opensuse-project from 13 October which went unanswered. I may not be able to attend the meeting tomorrow, hence the following: it is a little annoying when one's report is marked duplicate of something one cannot see. I totally appreciate having two reports (sysrich, 15:05:53) * Good discussion about the topic, some suggestions, but at the core, this requires SUSE to change how they work internally, so Richard to discuss inside SUSE (sysrich, 15:43:47) * ACTION: Richard to discuss options for making SLE bugs more publically visible within SUSE (sysrich, 15:43:58) * Tumbleweed (sysrich, 15:44:12) * Any other Business? (sysrich, 15:49:23) * openSUSE are planning to have a summit co-located with SCALE in Los Angeles in Feb 2015 (sysrich, 15:52:38) * Tumbleweed - Take 2 (sysrich, 15:54:13) * LINK: http://lists.opensuse.org/opensuse-factory/2014-11/msg00120.html (sysrich, 16:08:33) * If you're an OBS Project Maintainer, please make sure you've read http://lists.opensuse.org/opensuse-factory/2014-11/msg00120.html and setup your OBS Project accordingly (sysrich, 16:15:26) * Next Meeting (sysrich, 16:18:13) * Next meeting will be on 26th November at 1500 UTC, See you think (sysrich, 16:18:35) Meeting ended at 16:18:43 UTC. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Richard Brown wrote:
Meeting started by sysrich at 15:00:35 UTC. The full logs are available at
http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-projec...
.
Meeting summary ---------------
* Action Item Review (sysrich, 15:04:10) * No action items from last meeting (sysrich, 15:04:18)
* Non-publically accessible Bug Reports (sysrich, 15:04:40) * PJessen wrote the following into the openSUSE Project Meeting Agenda - Proposed change in Bugzilla policy wrt duplicates of non-publicly accessible reports. See my posting to opensuse-project from 13 October which went unanswered. I may not be able to attend the meeting tomorrow, hence the following: it is a little annoying when one's report is marked duplicate of something one cannot see. I totally appreciate having two reports (sysrich, 15:05:53) * Good discussion about the topic, some suggestions, but at the core, this requires SUSE to change how they work internally, so Richard to discuss inside SUSE (sysrich, 15:43:47) * ACTION: Richard to discuss options for making SLE bugs more publically visible within SUSE (sysrich, 15:43:58)
Apologies for not being present yesterday. Richard, if I may, I would suggest there is probably little point in trying to change the SUSE policy on this point. When reports contain sensitive customer data, they will never be open to the public. That's why I thought we might be able to look at how we (openSUSE) work with this instead. Disallowing duplicates as per my proposal ought to be a fairly trivial change in bugzilla. thanks Per -- Per Jessen, Zürich (8.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On 13 November 2014 08:14, Per Jessen
Apologies for not being present yesterday. Richard, if I may, I would suggest there is probably little point in trying to change the SUSE policy on this point. When reports contain sensitive customer data, they will never be open to the public. That's why I thought we might be able to look at how we (openSUSE) work with this instead. Disallowing duplicates as per my proposal ought to be a fairly trivial change in bugzilla.
thanks Per
Hi Per, I understand what you're trying to say, and I realise my decision to carry this forward might seem a little strange given your perspective. But to shed a light on it from mine, consider the following options 1. The recent changes to our Bugzillas did not just include the transformation into one Bugzilla, with many frontends. Changes were made to handle SUSE handle Private Comments. There is potentially a technical answer where SUSE may be able to have the 'bugs' private, but keep the information they are concerned about safely hidden away in Private Comments. 2. openSUSE does not operate in a 'bubble' - while we have exceptional independence to do what we want, we should embrace the fact we share common technologies with SUSE and try to avoid duplication of work. That's good for both of us. Or in simple English - if SUSE are working on a bug, I think it's madness for openSUSE to work on the same bug independently without collaboration. So on those grounds, I'm really opposed to any idea where openSUSE creates more work for itself unless there is really absolutely most certainly no other option :) From a certain point of view, I could even argue that the current situation is better than what you suggest - while obviously its demotivating for the bug reporter who suddenly finds their bug 'Private', they can at least have faith that it happened because someone at SUSE has looked at it and it therefore _will_ be tackled. 3. Internally at SUSE, there are ongoing discussions about how they can work closer with openSUSE for the benefit of both our project and their own development processes. This current situation with SLE/openSUSE duplicates in Bugzilla is a perfect example of a practical issue that will need to be resolved for SUSE to travel in that direction. So, you raise the issue at a good time for me to take it to them and see what can come of it. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
I want to correct the terrible english in my point 1.
1. The recent changes to our Bugzillas did not just include the
transformation into one Bugzilla, with many frontends. Changes were
made to handle Private Comments. There is potentially a
technical answer where SUSE may be able to have the 'bugs' _PUBLIC_,
but keep the information they are concerned about safely hidden away
in Private Comments.
On 13 November 2014 10:38, Richard Brown
On 13 November 2014 08:14, Per Jessen
wrote: Apologies for not being present yesterday. Richard, if I may, I would suggest there is probably little point in trying to change the SUSE policy on this point. When reports contain sensitive customer data, they will never be open to the public. That's why I thought we might be able to look at how we (openSUSE) work with this instead. Disallowing duplicates as per my proposal ought to be a fairly trivial change in bugzilla.
thanks Per
Hi Per,
I understand what you're trying to say, and I realise my decision to carry this forward might seem a little strange given your perspective. But to shed a light on it from mine, consider the following options
1. The recent changes to our Bugzillas did not just include the transformation into one Bugzilla, with many frontends. Changes were made to handle SUSE handle Private Comments. There is potentially a technical answer where SUSE may be able to have the 'bugs' private, but keep the information they are concerned about safely hidden away in Private Comments. 2. openSUSE does not operate in a 'bubble' - while we have exceptional independence to do what we want, we should embrace the fact we share common technologies with SUSE and try to avoid duplication of work. That's good for both of us. Or in simple English - if SUSE are working on a bug, I think it's madness for openSUSE to work on the same bug independently without collaboration. So on those grounds, I'm really opposed to any idea where openSUSE creates more work for itself unless there is really absolutely most certainly no other option :) From a certain point of view, I could even argue that the current situation is better than what you suggest - while obviously its demotivating for the bug reporter who suddenly finds their bug 'Private', they can at least have faith that it happened because someone at SUSE has looked at it and it therefore _will_ be tackled. 3. Internally at SUSE, there are ongoing discussions about how they can work closer with openSUSE for the benefit of both our project and their own development processes. This current situation with SLE/openSUSE duplicates in Bugzilla is a perfect example of a practical issue that will need to be resolved for SUSE to travel in that direction.
So, you raise the issue at a good time for me to take it to them and see what can come of it. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Richard Brown wrote:
Hi Per,
I understand what you're trying to say, and I realise my decision to carry this forward might seem a little strange given your perspective. But to shed a light on it from mine, consider the following options
1. The recent changes to our Bugzillas did not just include the transformation into one Bugzilla, with many frontends. Changes were made to handle SUSE handle Private Comments. There is potentially a technical answer where SUSE may be able to have the 'bugs' private, but keep the information they are concerned about safely hidden away in Private Comments. 2. openSUSE does not operate in a 'bubble' - while we have exceptional independence to do what we want, we should embrace the fact we share common technologies with SUSE and try to avoid duplication of work. That's good for both of us. Or in simple English - if SUSE are working on a bug, I think it's madness for openSUSE to work on the same bug independently without collaboration. So on those grounds, I'm really opposed to any idea where openSUSE creates more work for itself unless there is really absolutely most certainly no other option :) From a certain point of view, I could even argue that the current situation is better than what you suggest - while obviously its demotivating for the bug reporter who suddenly finds their bug 'Private', they can at least have faith that it happened because someone at SUSE has looked at it and it therefore _will_ be tackled. 3. Internally at SUSE, there are ongoing discussions about how they can work closer with openSUSE for the benefit of both our project and their own development processes. This current situation with SLE/openSUSE duplicates in Bugzilla is a perfect example of a practical issue that will need to be resolved for SUSE to travel in that direction.
So, you raise the issue at a good time for me to take it to them and see what can come of it.
Thanks for the explanation Richard, much appreciated. cheers Per -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
participants (2)
-
Per Jessen
-
Richard Brown