From: Ed W <lists@wildgooses.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Summary] tentative x86 arch team glep
Date: Mon, 12 Sep 2005 00:53:03 +0100 [thread overview]
Message-ID: <4324C35F.5090008@wildgooses.com> (raw)
In-Reply-To: <20050906182129.5725cf67@snowdrop.home>
Ciaran McCreesh wrote:
>On Tue, 06 Sep 2005 18:03:37 +0100 Ed W <lists@wildgooses.com> wrote:
>| As an "outsider" reading that summary the message *I* read is that
>| there is some strain over fitting the development model into
>| "stable", "~", and "package.mask". I think I see people basically
>| saying that they have differing views over what qualifies for each
>| level?
>
>The system basically works. The problems are:
>
>* It's not always used correctly.
>* It's not entirely understood by some users.
>* Some users think it should be easier to unmask a group of related
>packages.
>
>
Might there be an option 4 which is that a slightly different system
might stop everyone bitching over the current one and hence avoid
wasting some time? Nope, no idea what that would be, but the thought
does occur when you see some time being wasted on trivial issues...
>| Also, as someone who has submitted a few patches and some ebuilds and
>| then seen nothing happen to them and my offers to act as maintainer
>| have gone unresponded I also wonder if there is some way to make
>| better use of casual contributors like me? (I'm not bitter, it's just
>| that I feel I could contribute more, but don't know how to?)
>
>The problem is... Getting someone ready to be able to commit to the
>main tree is expensive in terms of existing developer time. The
>solution isn't lowering the standards for commit access, because that
>just leads to even more wasted developer time. There's the two tier
>system that gets proposed every now and again, but that would a)
>require svn rather than cvs and b) require that certain people who
>currently have main tree access be moved to branch access only.
>
>A bigger tree is all well and good, but the tree we have right now is
>only half maintained...
>
>
Is there any possibility that easier low quality contribution makes the
high quality contributions easier?
Look at wikipedia - it's amazing that such high quality work (in
general) can come from lightly peer review material with low barriers to
entry.
Clearly not an appropriate model here, but I can't help wondering if
there is not another way...
I did read the FAQ here and I take your point though:
http://dev.gentoo.org/~ciaranm/docs/mw-faq/maintainer.txt
Thanks for listening
Ed W
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-11 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 10:03 [gentoo-dev] [Summary] tentative x86 arch team glep Chris White
2005-09-06 12:35 ` Mike Doty
2005-09-06 17:03 ` Ed W
2005-09-06 17:21 ` Ciaran McCreesh
2005-09-06 20:07 ` Alec Joseph Warner
2005-09-11 23:53 ` Ed W [this message]
2005-09-12 0:03 ` Ciaran McCreesh
2005-09-12 17:04 ` Ed W
2005-09-12 17:19 ` Michael Kohl
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=4324C35F.5090008@wildgooses.com \
--to=lists@wildgooses.com \
--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