From: Ralph Seichter <abbot@monksofcool.net>
To: gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] Proxy-maint situation and future
Date: Sun, 07 Apr 2019 17:17:13 +0200 [thread overview]
Message-ID: <87lg0lc0au.fsf@ra.horus-it.com> (raw)
In-Reply-To: <5b67413efd86e022cc533dba0b71d7146a32bc66.camel@gentoo.org>
* Michał Górny:
> Do you have any specific ideas on how we could improve the situation?
I know too little about all the steps required on the developer side
when adding a new package, even though I have authored some new packages
However, to free up developer capacity, it seems to me that giving the
volunteer contributors more responsibility for simple changes like
version bumps should help. It should be possible to automatically
determine if the previous ebuild was simply copied, which is what I do
when version bumping, and remains otherwise unchanged.
You already mentioned your GURU idea. Having a gitolite-backed
repository where volunteers can commit simple changes if they are listed
as maintainers in metadata.xml, and having these changes integrated by
some automatism, might help, even if it does not address brand new
packages.
-Ralph
next prev parent reply other threads:[~2019-04-07 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 14:43 [gentoo-proxy-maint] Proxy-maint situation and future Michał Górny
2019-04-07 15:17 ` Ralph Seichter [this message]
2019-04-07 15:34 ` Corentin “Nado” Pazdera
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=87lg0lc0au.fsf@ra.horus-it.com \
--to=abbot@monksofcool.net \
--cc=gentoo-proxy-maint@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