At Thu, 10 Sep 2009 12:36:53 +0200, Henne Vogelsang wrote:
Hi,
Takashi Iwai wrote:
At Thu, 10 Sep 2009 11:09:33 +0200, Henne Vogelsang wrote:
Pavol Rusnak wrote:
Takashi Iwai wrote:
OK, will do. But, what should we do really for security issues...? We probably should start thinking about creating a Community Security Team ... We did and have already volunteers. See the thread,
[opensuse-factory] openSUSE 11.2 and maintenance http://lists.opensuse.org/opensuse-factory/2009-08/msg00372.html
So, actually there is no problem to keep the maintainer and bugowner of OBS devel packages empty in practice?
There is no problem if you talk to the other project maintainers and they agree to maintain it (together or someone steps up). Only if you just drop the work on them without talking to them we have a problem.
Fair enough.
Just remember:
* A devel project MUST have a maintainer * A package in a devel project MIGHT have a maintainer * A package in a devel project MIGHT have a bugowner
I think this is also the general challenge we currently face. The transition of working alone on a package to working together in groups.
Right, and there are a few problem around here. So far, not all (maybe most of) devel projects have tight communication channels for maintainers, even no dedicated MLs. Thus, no real consensus has been made wrt how to handle bugs as a group. However, the real problem is, that this situation hasn't been changed for months. I think we really have to consider this more deeply before we rushing into the release -- because most of bug reports come first after RC :) thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org