[opensuse-packaging] OBS package bugowners wanted for git and mercurial
Hi, due to the lack of time, I'd like to give away my maintainership of two packages: git and mercurial. More strictly speaking, it's about "Bugowner" field that needs to be re-assigned. Since both are commonly used programs, I hope someone will take over it and I can avoid submitting deletereq for them :) Thanks! Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi Takashi, talking about only mercurial here. Am 12.10.18 um 15:15 schrieb Takashi Iwai:
due to the lack of time, I'd like to give away my maintainership of two packages: git and mercurial. More strictly speaking, it's about "Bugowner" field that needs to be re-assigned.
Since both are commonly used programs, I hope someone will take over it and I can avoid submitting deletereq for them :)
I'm a bit surprised: wolfi@Hygiea:~> osc maintainer -e mercurial Defined in package: devel:tools:scm/mercurial bugowner of mercurial : wolfgang@rosenauer.org, tiwai@suse.com maintainer of mercurial : wolfgang@rosenauer.org, tiwai@suse.com, develop7@develop7.info The package is actually well maintained AFAICT. develop7 is very quick in getting new versions in and I also care. It's true that for maintenance requests (aka security fixes) it mainly fell back to you. Not sure if that is because you were faster in reacting or you carry a suse.com address and the security people consider this primary above a community contributor? Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Fri, 12 Oct 2018 15:20:56 +0200, Wolfgang Rosenauer wrote:
Hi Takashi,
talking about only mercurial here.
Am 12.10.18 um 15:15 schrieb Takashi Iwai:
due to the lack of time, I'd like to give away my maintainership of two packages: git and mercurial. More strictly speaking, it's about "Bugowner" field that needs to be re-assigned.
Since both are commonly used programs, I hope someone will take over it and I can avoid submitting deletereq for them :)
I'm a bit surprised:
wolfi@Hygiea:~> osc maintainer -e mercurial Defined in package: devel:tools:scm/mercurial bugowner of mercurial : wolfgang@rosenauer.org, tiwai@suse.com
maintainer of mercurial : wolfgang@rosenauer.org, tiwai@suse.com, develop7@develop7.info
The package is actually well maintained AFAICT. develop7 is very quick in getting new versions in and I also care. It's true that for maintenance requests (aka security fixes) it mainly fell back to you. Not sure if that is because you were faster in reacting or you carry a suse.com address and the security people consider this primary above a community contributor?
I don't think we have any big issue regarding the develproject itself. We can take the latest-and-greatest version if any security problem comes up, and that's easy. It's all for TW. And we are lucky that there are multiple great people contributing to these packages. So, I think I can just step down from devel:tools:scm/mercurial. But, as you stated, it comes to an interesting question when the topic is about security, especially for Leap (that is actually SLE). In general, the security issues are shared only among limited people at an initial state. That's the reason SUSE people may get information earlier (and hence often responsible to react earlier, too). How can it be communicated with the external community maintainer? I don't know -- it's a question to security team, I suppose. thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Friday 2018-10-12 15:32, Takashi Iwai wrote:
So, I think I can just step down from devel:tools:scm/mercurial. But, as you stated, it comes to an interesting question when the topic is about security, especially for Leap (that is actually SLE).
In general, the security issues are shared only among limited people at an initial state. [...] How can it be communicated with the external community maintainer? I don't know -- it's a question to security team, I suppose.
The initial state (or the state-right-after) usually includes the bugowner/maintainer. At least that is what regularly seems to happen to ffmpeg reports. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 13/10/2018 00:02, Takashi Iwai wrote:
On Fri, 12 Oct 2018 15:20:56 +0200, Wolfgang Rosenauer wrote:
Hi Takashi,
talking about only mercurial here.
Am 12.10.18 um 15:15 schrieb Takashi Iwai:
due to the lack of time, I'd like to give away my maintainership of two packages: git and mercurial. More strictly speaking, it's about "Bugowner" field that needs to be re-assigned.
Since both are commonly used programs, I hope someone will take over it and I can avoid submitting deletereq for them :)
I'm a bit surprised:
wolfi@Hygiea:~> osc maintainer -e mercurial Defined in package: devel:tools:scm/mercurial bugowner of mercurial : wolfgang@rosenauer.org, tiwai@suse.com
maintainer of mercurial : wolfgang@rosenauer.org, tiwai@suse.com, develop7@develop7.info
The package is actually well maintained AFAICT. develop7 is very quick in getting new versions in and I also care. It's true that for maintenance requests (aka security fixes) it mainly fell back to you. Not sure if that is because you were faster in reacting or you carry a suse.com address and the security people consider this primary above a community contributor?
I don't think we have any big issue regarding the develproject itself. We can take the latest-and-greatest version if any security problem comes up, and that's easy. It's all for TW. And we are lucky that there are multiple great people contributing to these packages.
So, I think I can just step down from devel:tools:scm/mercurial. But, as you stated, it comes to an interesting question when the topic is about security, especially for Leap (that is actually SLE).
In general, the security issues are shared only among limited people at an initial state. That's the reason SUSE people may get information earlier (and hence often responsible to react earlier, too).
How can it be communicated with the external community maintainer? I don't know -- it's a question to security team, I suppose.
If the package is part of SLE releases then it must have a maintainer / bugowner inside SUSE that is responsible for fixing security issues and L3 customer issues raised in SLE. That person must also be one of the bugowners / maintainers in obs so they can submit maintenance fixes from the community into SLE then Leap. As you seem to be the maintainer inside SUSE you actually need to speak to the maintenance team inside SUSE and find a new maintainer inside SUSE, they can then be set as the bugowner alongside Wolfgang in obs to deal with those issues. As a side note there is a number of packages where the system I described above is not happening. Hopefully we will get those fixed soon. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Fri, 12 Oct 2018 15:15:42 +0200, Takashi Iwai wrote:
Hi,
due to the lack of time, I'd like to give away my maintainership of two packages: git and mercurial. More strictly speaking, it's about "Bugowner" field that needs to be re-assigned.
As no one volunteered, so far, now I just removed myself from bugowner and maintainer from these packages in OBS. Currently git has no bugowner, and Wolfgang is the sole bugowner of mercurial. thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 10/18/18 7:37 AM, Takashi Iwai wrote:
On Fri, 12 Oct 2018 15:15:42 +0200, Takashi Iwai wrote:
Hi,
due to the lack of time, I'd like to give away my maintainership of two packages: git and mercurial. More strictly speaking, it's about "Bugowner" field that needs to be re-assigned.
As no one volunteered, so far, now I just removed myself from bugowner and maintainer from these packages in OBS.
Currently git has no bugowner, and Wolfgang is the sole bugowner of mercurial.
What sort of average weekly time commitment has bugowner of git taken? Although, as I it seems, someone from SUSE needs to be a bugowner for security issues. thanks, -- Jason Craig -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Fri, 19 Oct 2018 19:02:27 +0200, Jason Craig wrote:
On 10/18/18 7:37 AM, Takashi Iwai wrote:
On Fri, 12 Oct 2018 15:15:42 +0200, Takashi Iwai wrote:
Hi,
due to the lack of time, I'd like to give away my maintainership of two packages: git and mercurial. More strictly speaking, it's about "Bugowner" field that needs to be re-assigned.
As no one volunteered, so far, now I just removed myself from bugowner and maintainer from these packages in OBS.
Currently git has no bugowner, and Wolfgang is the sole bugowner of mercurial.
What sort of average weekly time commitment has bugowner of git taken?
The bugs are rare, at most one per month; and for TW, mostly it's just a matter of upgrading to the freshly released version. There have been a few reports about packaging, though.
Although, as I it seems, someone from SUSE needs to be a bugowner for security issues.
The bugowner will be filled by SUSE soon later in anyway. Don't worry about that. But I raised the question to opensuse-packaging nevertheless because the bugowner is not a field to be occupied by a single person at all. i.e. even if SUSE employee filled one position, it doesn't mean that it's healthy for the whole community. Ideally speaking, each package should be covered by both a community member and SUSE, to take a balance of governance. thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 10/21/18 12:41 AM, Takashi Iwai wrote:
On Fri, 19 Oct 2018 19:02:27 +0200, Jason Craig wrote:
Although, as I it seems, someone from SUSE needs to be a bugowner for security issues.
The bugowner will be filled by SUSE soon later in anyway. Don't worry about that.
But I raised the question to opensuse-packaging nevertheless because the bugowner is not a field to be occupied by a single person at all. i.e. even if SUSE employee filled one position, it doesn't mean that it's healthy for the whole community. Ideally speaking, each package should be covered by both a community member and SUSE, to take a balance of governance.
Well if that's the case then I would be willing to be a community bugowner for Git. thanks, -- Jason Craig -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, 23 Oct 2018 20:45:16 +0200, Jason Craig wrote:
On 10/21/18 12:41 AM, Takashi Iwai wrote:
On Fri, 19 Oct 2018 19:02:27 +0200, Jason Craig wrote:
Although, as I it seems, someone from SUSE needs to be a bugowner for security issues.
The bugowner will be filled by SUSE soon later in anyway. Don't worry about that.
But I raised the question to opensuse-packaging nevertheless because the bugowner is not a field to be occupied by a single person at all. i.e. even if SUSE employee filled one position, it doesn't mean that it's healthy for the whole community. Ideally speaking, each package should be covered by both a community member and SUSE, to take a balance of governance.
Well if that's the case then I would be willing to be a community bugowner for Git.
Thanks Jason! Which username do you have on OBS? Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 10/24/18 3:23 AM, Takashi Iwai wrote:
Thanks Jason! Which username do you have on OBS?
It's "poorboywilly". On a related but off topic note, does anyone know if I can get my OBS username changed? I've wanted to change it so it is based of my real name. If not, no big deal. -- Jason Craig -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hello, Am Mittwoch, 24. Oktober 2018, 17:22:29 CEST schrieb Jason Craig:
On a related but off topic note, does anyone know if I can get my OBS username changed? I've wanted to change it so it is based of my real name. If not, no big deal.
You can't change the username - but nobody stops you from creating another account with the username you want ;-) Note that you'll need to "migrate" your OBS permissions etc. manually. Regards, Christian Boltz -- I understand, I am also sure that they would not let me at their code and internal tools. If they do, I switch disto in a hartbeat, because that means others with the same level as I have can change stuff. I don't trust myself. :-) [houghi in opensuse-wiki] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wed, 24 Oct 2018 17:22:29 +0200, Jason Craig wrote:
On 10/24/18 3:23 AM, Takashi Iwai wrote:
Thanks Jason! Which username do you have on OBS?
It's "poorboywilly".
Now added. Enjoy :) thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (6)
-
Christian Boltz -
Jan Engelhardt -
Jason Craig -
Simon Lees -
Takashi Iwai -
Wolfgang Rosenauer