public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC]: Proxy-maintainer project
Date: Thu, 18 Mar 2010 20:09:43 +0100	[thread overview]
Message-ID: <4BA27A77.2050803@gentoo.org> (raw)
In-Reply-To: <201003181830.01103.hwoarang@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]

On 03/18/2010 05:29 PM, Markos Chandras wrote:
> Dear fellow developers,
> 
> A new project is about to start so I am requesting your feedback
> 
> The primary goal of the Proxy Maintainers[1] project is to create and maintain 
> relationships between developers and users in order to ensure packages in the 
> Gentoo tree stay up to date. This involves a few main tasks:

Also it is a nice idea, i dont think, it will help Gentoo in the longer term. As i can see with the
Sunrise project, most users only want to get their ebuild initially into portage/sunrise. They also
listen to suggestions, improve their code and read a document to get access. But in most cases, they
only do the initial commit or initial commit+some version bumps before they leave again and the
ebuild is unmaintained.
I dont think, we want to proxy for those users, since this would result in either the proxy
maintaining the ebuilds or many more maintainer-needed ebuild in main tree.
The next group of users are those, who actively maintain their ebuild, also help other users and do
this for a longer time. Usually those users get a mentor offer sooner or later and then become a
Gentoo Developer. So for those users, who are willing to help and can do this for longer time
(requirements for Gentoo devs), sunrise is already a good starting point and base to get in.
The only case, where there might be a (minimal) profit are those rare users, who initially commit
their ebuild and maintain exactly and only this ebuild for a longer time. There might be 2 or 3
users doing it this way, so creating just another project for this idea is imho a bit too much work
for minimal profit.

I think, it might be better to send the interested users so Sunrise, where they can learn the basics
and afterwards you could still offer them to proxy the ebuild (sunrise has an extra branch for proxy
maintainers).
A much better idea is imho to make the idea and way of Sunrise more public and easier to see without
searching (Homepage, FAQ, Forums), so interested users can find it easier. In addition, every dev,
who is interested in proxy maintaining something can do this via Sunrise.



-- 
Thomas Sachau

Gentoo Linux Developer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  parent reply	other threads:[~2010-03-18 19:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 16:29 [gentoo-dev] [RFC]: Proxy-maintainer project Markos Chandras
2010-03-18 17:13 ` Alexis Ballier
2010-03-18 17:24 ` Sébastien Fabbro
2010-03-18 17:50   ` Patrick Lauer
2010-03-18 18:32   ` justin
2010-03-18 21:03   ` Angelo Arrifano
2010-03-18 21:22     ` Markos Chandras
2010-03-18 19:09 ` Thomas Sachau [this message]
2010-03-18 20:29   ` Markos Chandras
2010-03-18 20:34   ` Ben de Groot
2010-03-19 14:00     ` Richard Freeman
2010-03-19  8:05 ` Alex Alexander

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=4BA27A77.2050803@gentoo.org \
    --to=tommy@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