Mailinglist Archive: yast-devel (63 mails)

< Previous Next >
Re: [yast-devel] who is the maintainer?
Hi today we faced it again. So if noone is against it, I will do
migration of MAINTAINER file to obs/ibs tomorrow ( 18.9.2014 ).

Plan is that I create one example pull request with change and it will
be approved I will do it automatic in master branch.


On Fri, 4 Jul 2014 13:43:33 +0200
Josef Reidinger <jreidinger@xxxxxxx> wrote:

Well, some time already passed and there is still some incorrect
information in build service. I propose to reserve one day to fix all
problems and to mass change MAINTAINER file ( I can do it ).


On Fri, 10 Jan 2014 17:40:16 +0100
Arvin Schnell <aschnell@xxxxxxx> wrote:

On Thu, Jan 09, 2014 at 11:48:06AM +0100, Arvin Schnell wrote:

while reassigning yast-maintainers bugs I noticed that once again
the maintainer/bugowner information is inconsistent: The content
of the MAINTAINER file in git differs from the output of 'osc
maintainer' or 'osc bugowner'. This leads to confusion.

We had this problem before and apparently fail to solve the
inconsistency long term. So I propose to drop the MAINTAINER file
in git and rely on osc.

Instead we can have a AUTHORS files so that people not knowing
about osc can still reach the authors.

During a telco we reached following conclusion:

- The buildservice is the offical source for maintainer

- The MAINTAINER files will be changed to include a note: "use
'osc maintainer / bugowner <package-name>' to query the
maintainer and bugowner"

- Martin will commit a README that will also include notes how to
reach developers.

Martin, it would be cool if you could also update the
MAINTAINER files during the README mass-commit.

- The MAINTAINER files could be removed in the future when
everybody has learn to use osc.

ciao Arvin

To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups