On Mittwoch, 30. Mai 2018 11:54:52 CEST Ludwig Nussel wrote:
Leap has no dedicated maintainers. It's all
inherited from Factory
and the output of "osc maintainer" counts, rather than any personal
interpretation of the data.
"osc maintainer" outputs very different information than your email for most
of the cases in the original list, example (randomly picked):
$ osc maintainer rpmdevtools
Defined in package: devel:tools/rpmdevtools
bugowner of rpmdevtools :
maintainer of rpmdevtools :
still I was listed as maintainer in your email . The bugowner is explicitely
set here, and the wiki page (not my personal interpretation) says:
You inheritingly are the guy everyone reports issues to, the only difference
compared to the maintainer is that you don't have direct write access to the
project/package you are set as bugowner to.
Plus the page doesn't mention anything about Leap, and leap seems to have more
complicated rules (for packages that comre from SLE). is there any way to
understand which information is actually correct? how does "osc maintainer"
look that up?
The notification mail did not refer to maintenance and
updates at all. It just asked to review the packages you are
responsible for to check whether everything is correct in Leap.
Taking acct as example again, if Katarina is the actual package
maintainer then don't add yourself as maintainer also. You are
project maintainer so can and have to act as backup anyways. Any
notifications, bot reviews etc would always go to an explicitly set
maintainer if there is one.
maintainer or bugowner in that last sentence?
what am I
missing? I've reread your email now twice, and I'm jetlagging..
sleep before harassing people then.
Successfully completed sleep step :-)
To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org