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 12:42:11 -0400	[thread overview]
Message-ID: <1126456931.10563.22.camel@localhost> (raw)
In-Reply-To: <20050911155045.GA13507@kfk4ever.com>

On Sun, 2005-09-11 at 17:50 +0200, Maurice van der Pot wrote:

> If bugs are not handled in a timely manner, it is because we're
> shorthanded. This is also the reason new ebuilds are often assigned to
> maintainer-wanted. We'd rather not add packages to portage if there is
> no developer to pick up maintenance for them. Remember that we are all
> investing our spare time to work on Gentoo, we're not getting paid.
> We'd rather focus on removing bugs from packages already in portage than
> on adding new packages.
> 
> Also for some packages it is hard to find a maintainer because it is
> best if the maintainer is also an active user of the package. If a
> relatively small group of people uses a package, it's much harder to
> find a suitable maintainer.
> 
> If you see an area that could use an extra developer working on it and
> you think you could be that developer, by all means apply for the
> position.
> 
> Here are some links of interest:
> http://www.gentoo.org/proj/en/devrel/staffing-needs/index.xml
> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2
> 
> Regards,
> Maurice.
> 

I am well aware of all this:

2.b. Helping out

Firstly; to be asked to become a developer you should either apply to an
opening, or just help out whether in the form of user support or filing
bug reports - we notice frequent contributors making contributions to
Gentoo and we attempt to reward them by giving them the chance to become
a Gentoo developer. Gentoo has many paths, and the Gentoo Developer
Relations Recruitment Team is always looking out not just for developers
- documentation writers and infrastructure maintainers are just as
important too for our distribution to run smoothly.

You should look out for openings for developers in the GWN, as well as
the /topic of #gentoo-bugs on irc.freenode.net - if you feel you could
fill in one of those positions, try to find a mentor who is willing to
sponsor you, or contact the Gentoo Recruiters who may be able to find a
mentor for you. Please do not file "New Developer" bugs on yourself
since this task is designated for the mentor and any such bugs will be
closed.
---------------------

Certainly, I am others have fulfilled this. I have emailed the two
maintainers offering to assist. No response.

For some reason, rox does not show up as a staffing need. That should be
corrected.

I'm not going to bloat this thread. I am here to help, and I know at
least one other fellow who probably would be willing to help too. It's
easy, quick, and will make what users there are for rox happy.

As I noted, the intent here was not to add any additional work for
developers. On the contrary, the work is done already. We're already
"helping out" we're filing bug reports, we're creating ebuilds that
work. All that needs to be done is get them into portage.

If you are unable to find a suitable developer to maintain rox, then
please let me know and I will see about assembling a herd for it.
-- 
Peter

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-09-11 16:45 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 [this message]
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

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=1126456931.10563.22.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