Re: [gentoo-dev] [PATCH] glep-0067: Add 'proxied' and 'watcher' maint types

[Hasan Calisir]

Hi,

Pleased to meet you i am proxy-maintainer in gentoo :) What i see here i
got a new title something like proxied or
without-commit-acces-proxy-maintainer or super-proxy-maintainer still

As a very active proxy-maintainer in gentoo for a year i think it is not
important how you are splitting things in metadata like person, proxied,
non-proxied, robot, cyborg .. Also it is not important who has @gentoo

I am trying to manage many package in gentoo (without paycheck) and i
can say that proxy-maint has lost its function because of super-busy
gentoo-devs. Sorry but if you are super-busy give it up. If you have no
time to test PRs or your own packages then simply retire. If you don't
have time to install manpages with use flag then retire. Being only 7/24
online on IRC doesn't mean you are a dev. If you scary about new

I wrote 900 line openblas switch script 5 month ago for gentoo
reference-blas-lapack set .This PR waited 5 months and nobody cared it
and an other dev merged his own openblas PR with new switch framework
without informing me. If a dev not checking active PRs before opening a

A simple example to explain a situation what is happening on gentoo

Anybody checked BIND package version in tree ? It is 9.12.3_P4 [1]  EOL

I updated bind ebuild then upgraded my DNS server but i didn't opened

2019-08-03 03:26, Aaron Bauman yazmış:

not clear for me. mail. packages or big PRs then again give up. new one there is no word to say. currently. as of May 2019. This is the one of the core package any linux distro. any PR because i know you guys so-busy. Anyway thank you for your great support. Best. ~Hasan

On Sat, Aug 03, 2019 at 01:20:34AM +0200, Jonas Stein wrote: On 02/08/2019 
22.55, Michał Górny wrote: Add two new maintainer types: 'proxied' for proxied 
maintainers,
and 'watcher' for people who wish to be CC-ed on bugs but are not

user does not belong into the tree.

maintainers (e.g. upstream developers). Can't we solve this simply in the bug tracker? The monitor setting of a

I would disagree with this. The benefits of it being the metadata is
just
that... it is metadata. Hence, QA checks can logically determine the
state of
maintainership on a given package.

This is one of the reasons metadata.xml was standardized years ago.

The upstream maintainer and all other "watchers" have no write access to
the tree so they will consume manpower in adding and removing their
contacts to packages.

This should become a repetitive task unless the package is continuously
being
turned over to other maintainers. Once and done is the general rule.

The perfect solution would be that any user can add a watch filter to
my-cat/mypkg in the bugtracker.

This assumes that those reporting bugs are inputing proper information.
See my
first comment regarding the metadata.xml standards.

Between 2018-01-01 and 2018-12-31 we received and assigned 31280 bugs.
I am no fan of the descriptions in the form "please CC: If the bug is
about x but not y and the moon is in the third house of the lion"

This is a good point. I am not sure how many packages have this type of
information in the metadata, but it is not a good place for it.

This consumes extra time for every assignment and prevents automagic
assignment in future. We should rather keep it simple instead of
extending the options.

I would think this *would* help us do automagic assignements in the
future, but

Links:
------
[1]
https://gitweb.gentoo.org/repo/gentoo.git/tree/net-dns/bind/bind-9.12.3_p4.ebuild

more accurately.

signature.asc
Description: OpenPGP digital signature