On Thu, 2006-10-05 at 09:52 +0300, Alin Nastac wrote: > Natanael Copa wrote: > > Nobody has ever showed interest and I'm not pushing my services on > > anyone. > > > Why exactly you don't want to become a Gentoo dev?
Because of the byrocracy? Is it worth it to only maintain one single package? Because of gentoo devs always seems to fight? > The whole "proxy maintainer" thing is a bunch of crap. Thanks. Seems to work just fine in freebsd ports. > The Gentoo developer will still be > expected to be responsible of his/her commits, which means 2 maintainers > will spend (approximately) same amount of time testing it. The Gentoo developer would have the final reposability, so yes, he/she might need to test it. But if it doesn't work the Gentoo developer sends an email to the (proxy) maintainer: "It doesn't work. Please fix or I won't commit" or: "The code is too ugly. Please improve or I won't commit". The Gentoo dev can establish a relationship with the maintainer so after a while he/she knows the (proxy) maintainer is trustable and can commit after just a look. This in contrast to dealing with thousands unknown bug reporters. If the (proxy) maintainer doesn't answer, the gentoo dev can either fix it himself/herself or find an new maintainer - which I believe is easier than requiting a new dev, since it does not *feel* like as much responsability, even if it is. Its funny, I use gentoo much more that FreeBSD, I'm a freebsd port maintainer, but nothing for Gentoo (well, im an active bugreporter...) When I submit a fix/version bumb (I submit as "maintainer update") to freebsd ports, its normally committed within hours, even if its not a popular port. When I submit fixes for packages in Gentoo bugzilla it get stuck for months. They must have done something right. -- Natanael Copa -- gentoo-dev@gentoo.org mailing list
