From: Sam Jorna <wraeth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fixing elasticsearch maintainer
Date: Mon, 22 May 2017 15:50:03 +1000 [thread overview]
Message-ID: <20170522055002.GA21602@cerberus.civica.com.au> (raw)
In-Reply-To: <1495432039.1899.3.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Mon, May 22, 2017 at 07:47:19AM +0200, Michał Górny wrote:
> On pon, 2017-05-22 at 11:52 +1000, Sam Jorna wrote:
> > On 18/05/17 02:38, Patrick Lauer wrote:
> > > Since proxy-maint refuses to be removed from packages (especially since they
> > > were unconditionally added to all packages with a non-gentoo-dev maintainer in
> > > metadata) they are the de facto maintainers, and overrule everything else.
> >
> > Just to clarify, the Proxy Maintainers project is not required to be
> > added to all packages maintained by non-Gentoo maintainers. If a Gentoo
> > developer is willing to work with and proxy commits for maintainer(s)
> > without commit access, Proxy Maintainers are happy to be removed. There
> > are several metadata.xml's in the tree with examples, including a few
> > for which you are one of the maintainers.
> >
>
> Just to clarify, this works only if the developer and proxied maintainer
> agree on the terms. It's not 'I remove proxy-maint, and now force you to
> work on my terms that do not fit you because reasons'.
That's why I used the phrase "work with".
--
Sam Jorna (wraeth)
GnuPG Key: D6180C26
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 1006 bytes --]
prev parent reply other threads:[~2017-05-22 5:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 16:38 [gentoo-dev] Fixing elasticsearch maintainer Patrick Lauer
2017-05-18 15:49 ` Mart Raudsepp
2017-05-18 16:50 ` Andrew Savchenko
2017-05-18 17:17 ` Alec Warner
2017-05-19 16:38 ` Patrick Lauer
2017-05-20 19:43 ` Tomas Mozes
2017-05-19 13:10 ` Michał Górny
2017-05-19 16:50 ` Patrick Lauer
2017-05-19 17:27 ` Kristian Fiskerstrand
2017-05-19 22:43 ` Kent Fredric
2017-05-19 22:58 ` Kristian Fiskerstrand
2017-05-20 19:57 ` Tomas Mozes
2017-05-20 20:46 ` Michał Górny
2017-05-20 20:51 ` Kristian Fiskerstrand
2017-05-20 21:06 ` Michał Górny
2017-05-20 21:16 ` Kristian Fiskerstrand
2017-05-22 4:10 ` Patrick Lauer
2017-05-22 19:27 ` Kent Fredric
2017-05-22 20:05 ` Matthias Maier
2017-05-22 21:05 ` M. J. Everitt
2017-05-20 21:24 ` Andreas K. Huettel
2017-05-20 19:35 ` Tomas Mozes
2017-05-22 1:52 ` Sam Jorna
2017-05-22 4:12 ` Patrick Lauer
2017-05-22 4:16 ` M. J. Everitt
2017-05-22 4:24 ` Sam Jorna
2017-05-22 19:31 ` Kent Fredric
2017-05-22 5:47 ` Michał Górny
2017-05-22 5:50 ` Sam Jorna [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170522055002.GA21602@cerberus.civica.com.au \
--to=wraeth@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox