On Tue, 06 Aug 2019 18:53:33 +0200
Ulrich Mueller wrote:
> Yes, I know how elementary set theory works. :) I had asked for a
> concrete _example_ in the outer set but not in the inner.
Easy:
- You maintain a package that depends on this, and you want to be kept
"in the loop" on changes/bugs
> On Tue, 06 Aug 2019, Kent Fredric wrote:
>> Can you give an example of a maintainer in the watcher \ upstream set?
> all maintainers who aren't upstream are just maintainers
> all maintainers who are upstream are just maintainers
> all maintainers are watchers
> So:
> { watcher {
On Fri, 2019-08-02 at 22:55 +0200, 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
> maintainers (e.g. upstream developers).
>
> While at it, clarify that subproject member inheritance does
On Tue, 06 Aug 2019 09:45:18 +0200
Ulrich Mueller wrote:
> > All fit within
> > , but not all
> > fits within
>
> Can you give an example of a maintainer in the watcher \ upstream set?
>
> Ulrich
all maintainers who aren't upstream are just maintainers
all maintainers who are upstream
> On Tue, 06 Aug 2019, Kent Fredric wrote:
> All fit within
> , but not all
> fits within
Can you give an example of a maintainer in the watcher \ upstream set?
Ulrich
signature.asc
Description: PGP signature
On Sun, 04 Aug 2019 18:49:30 +0200
Ulrich Mueller wrote:
> > And yes, I'm talking about real life situation when the only
> > in the package left was this 'upstream watcher'.
> > I suppose an alternative solution there would be to return to explicit
> > logical marking as .
>
> Many metadata
On Sun, 04 Aug 2019 18:49:30 +0200
Ulrich Mueller wrote:
> Alternatively, how about calling that type "upstream" instead of
> "watcher"?
Mostly, because the term "upstream" doesn't communicate any useful
information about what it is expected to mean, and, it reduces the
usefulness of this field
> On Sat, 03 Aug 2019, Michał Górny wrote:
>> Upstream developers can be listed already now in the
>> description (per GLEP 68). Should they be listed twice now, only to
>> indicate that they are to be CCed on bugs?
> This is happening already. I'm not saying it's perfect but I don't see
>
Hi
On 2019/08/03 01:19, 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
maintainers (e.g. upstream developers).
Can't we solve this simply in the bug
On Sat, 3 Aug 2019 01:20:34 +0200
Jonas Stein wrote:
> 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"
You could stipulate that in order to be added as a "watcher" in
metadata.xml, you must agree to accept
On Sat, 2019-08-03 at 01:20 +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
> > maintainers (e.g. upstream developers).
>
> Can't we
On Sat, 2019-08-03 at 06:40 +0200, Ulrich Mueller wrote:
> > > > > > On Fri, 02 Aug 2019, 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
> > maintainers (e.g. upstream developers).
>
>
> On Fri, 02 Aug 2019, 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
> maintainers (e.g. upstream developers).
Upstream developers can be listed already now in the
description (per
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
not clear for me.
As a very active proxy-maintainer in gentoo for a year i think it is not
important
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
> > maintainers (e.g. upstream developers).
>
> Can't
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
> maintainers (e.g. upstream developers).
Can't we solve this simply in the bug tracker? The monitor setting of a
user
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
> maintainers (e.g. upstream developers).
Can't we solve this simply in the bug tracker? The monitor setting of a
user
17 matches
Mail list logo
