public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Hyman <pete4abw@comcast.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ROX: maintainer-wanted and apps out of date
Date: Sun, 11 Sep 2005 20:36:55 -0400	[thread overview]
Message-ID: <1126485415.10563.101.camel@localhost> (raw)
In-Reply-To: <4324CB6D.9060202@gentoo.org>

On Sun, 2005-09-11 at 20:27 -0400, Stephen P. Becker wrote:
> > Thank you for the opportunity. Apparently though, my submissions have
> > already been rejected Ciaran. It's important to realize that the
> > submissions were intended to AID the developers, not to necessarily be
> > PERFECT in every way.
> 
> Of course they have been criticized by Ciaran.  In case you didn't know, 
> he does this for *every* maintainer-wanted ebuild.  They are only 
> rejected as long as they have problems.  If you fix them, they will be 
> accepted if some dev takes responsibility for them, or is recruited to 
> maintain them.  It's really that simple  Sounds like a case where you 
> can't stand to have anyone review your work.
> 
> > I submitted the ebuilds in good faith in the hope they would help myself
> > and others get the portage tree wrt ROX up to date and correct
> > breakages. In that my "spacing" was not liked, or my "descriptions" were
> > too long is irrelevant.
> 
> No, it isn't irrelevant.  We strive to make the portage tree to be of 
> high quality.  Why settle for less?
> 
> -Steve

Oh, flame on! When I submitted many of the ebuilds, I had no idea the
rox maintainers were AWOL. I just assumed that they would take heed of
the version bumps, small changes made to existing ebuilds, and update
portage. It was not my intent to replace the maintainers or to re-invent
their efforts. I thought that having a new up-to-date ebuild would save
time for the maintainers.

I did not know that there were none anymore. As I wrote privately to
Ciaran, if I WAS auditioning to become a dev, then sure, I need the
comments. However, I was using:
http://www.gentoo.org/doc/en/ebuild-submit.xml as my guide -- the goal
being to alert the devs that new stuff was out and that certain
breakages needed fixing.

If the goal was to keep portage quality high, take heed of user comments
when it comes to updating packages. We all share that goal.


--
Peter

-- 
gentoo-dev@gentoo.org mailing list



      reply	other threads:[~2005-09-12  0:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11 13:58 [gentoo-dev] ROX: maintainer-wanted and apps out of date Peter Hyman
2005-09-11 15:50 ` Maurice van der Pot
2005-09-11 16:42   ` Peter Hyman
2005-09-11 19:24     ` Maurice van der Pot
2005-09-11 21:02     ` Alin Nastac
2005-09-12  0:10       ` Aron Griffis
2005-09-12  7:04         ` Alin Nastac
2005-09-12  0:14       ` Peter Hyman
2005-09-12  0:25         ` Ciaran McCreesh
2005-09-12  0:38           ` Alec Warner
2005-09-12 11:55           ` Carsten Lohrke
2005-09-12 14:03             ` Chris Gianelloni
2005-09-12 14:26               ` Re[2]: " Jakub Moc
2005-09-12 14:28               ` Maurice van der Pot
2005-09-12 15:41                 ` Peter Hyman
2005-09-12 16:12                   ` Martin Schlemmer
2005-09-12 17:00                     ` Peter Hyman
2005-09-12 17:12                       ` Jan Kundrát
2005-09-12 17:25                       ` Stephen P. Becker
2005-09-12 17:51                       ` Chris Gianelloni
2005-09-12 17:03             ` Ciaran McCreesh
2005-09-12 17:32               ` Carsten Lohrke
2005-09-12 17:40                 ` Ciaran McCreesh
2005-09-12 17:56                 ` Re[2]: " Jakub Moc
2005-09-12 18:53                   ` Carsten Lohrke
2005-09-12 19:21                     ` Ciaran McCreesh
2005-09-13  0:20                       ` Nathan L. Adams
2005-09-12 19:26                     ` [gentoo-dev] " Dan Meltzer
2005-09-12  0:27         ` [gentoo-dev] " Stephen P. Becker
2005-09-12  0:36           ` Peter Hyman [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=1126485415.10563.101.camel@localhost \
    --to=pete4abw@comcast.net \
    --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