Re: [gentoo-dev] creating ebuilds

[Paul de Vrieze <pauldv@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 06 January 2004 09:17, Robert Cole wrote:
> But I want to know if the brick wall that others have hit is still
> there or not. There's been a bit o conflict in teh past where gentoo
> will call for maintainers for certain projects yet previously slapped
> down up and coming devs that want to maintain a different project. Why
> would they volunteer for the requested project after being hammered
> previously even if they have the skill to do the requested one? Would
> you? Who would? From my understanding the devs are overwhelmed right
> now with maintaining the current tree and need more people to take on
> maintaining packages. The egos need to go by by and just do a quick
> check to see if the ebuild and the dev have followed policy and mark
> the thing ~x86 or whatever arch it is and toss it out. If it floats
> then great they've proven themselves. If it sinks then a bit more
> education is in order, pull the package and politely ask the new dev
> to find and fix the problem and describe clearly what the problem was
> and what they did to fix it and if it apears they understand the
> problem and had a good solution toss it back in the tree to go again.
> It would likely float the second time.

There is unfortunately a limit on the amount of devs that we can handle. 
We are still busy putting more structure in the gentoo organization, but 
we would certainly have a problem if the amount of developers increased 
drastically.

> I'm not suggesting giving someone new with no established background
> any sort of access. What I'm suggesting is basically what Allen spoke
> of in just encouraging more contributions but accepting ebuilds faster
> and the person with the proper access toss it in the tree.

Like said before, the issue is not the initial ebuild. It is the 
maintenance, including fixing bug reports and new versions. At the 
moment there are allready too many packages in the tree that are not 
actually maintained. This is partly due to the fact that  those packages 
are not easy to identify, and partly because it are just low-profile 
packages. But that does not mean that we want more of those packages. 
However when an ebuild gets committed without someone maintaining it 
that is exactly what happens. If there are too many of those orphan 
ebuilds it will reflect on the distribution (most orphan ebuilds have 
issues because of not being maintained)

Paul

- -- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQE/+rDEbKx5DBjWFdsRAoeNAJ4x9wMNJoi7CCMRqBCPJPrGOHrDUwCdGLGp
oA6tDMX7fglK22bUZ2zsy54=
=sYex
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list