On Tue January 06 2004 4:09 am, Chris Gianelloni wrote: > On Tue, 2004-01-06 at 03:39, Robert Cole wrote: > > On Mon January 05 2004 11:55 pm, Jon Portnoy wrote: > > > Okay, let me explain a little bit about how the recruitment process > > > works. > > > > I like it. That's a very good process. I'm talking about ebuilds here. > > I'll be honest and say I don't know how the backend of the portage tree > > works with security and all but maybe another tier would be in order if > > possible. Like a low access new ebuild access that gets queued and not > > actually put in the tree and someone with access could simply flag it to > > move into the tree or reject it sending an email back to the creator of > > the ebuild why. > > That is exactly what is done with Bugzilla. If ti isn't being done on > certain ebuild submissions, it should be.
I couldn't agree more with Allen on this. Bugzilla should be for software bugs not ebuilds. It obviously sucks for that. > Bugs will stay in Bugzilla if no developer wants to maintain the > package. At the end of the day, if I submit an ebuild that you created, > *I* am responsible for it, not you. Many developers do not want to take > on the responsibility of maintaining ebuilds that they know little to > nothing about. I know I surely don't. Now this is just wrong. A cvs dev shouldn't have to shoulder someone elses ebuild when the submitter is willing to maintain it. <snip> > than try to add new "testing" packages. As for ACCEPT_KEYWORDS, Gentoo > does not use ~ARCH as an unstable area. It is an area for testing > EBUILDS, not for testing packages. If a package is unstable, it doesn't > belong in our tree. Period. Whoa then I guess you better clear out half the gentoo tree then! Just because a new release of a software is put out doesn't mean its stable. Heck look at gcc, gnupg, cvs, etc yet because those packages have active maintainers they get rev bumped within hours of a new release and some get downgraded quickly. I run KDE 3.2 beta 2 but it's not 100% stable so you better hurry up and take it out of the tree. See how bogus " If a package is unstable, it doesn't belong in our tree. Period." is? Simply not true. Gentoo is a bleeding edge distro and gets all the latest releases of anything that has a maintainer beta, pre, or release. > No. It is a bug that should be fixed by the developer/maintainer. It > very well COULD be a developer's fault that someone's system went > haywire. Usually, though, it is simply a combination of items which was > not explicitly tested for and ends up being a bug in either the ebuild > or the package itself. And I say so what? Again as a gentoo user I accept that risk when I use the gentoo distro. If I want "stable" I could run debian stable and be a few years back on everything all the time. > Yes. You can always add ebuilds to bugzilla. If you think people will > be interested in them, stir up some support for them in the forums and > have people test your ebuilds. Look at lots of ebuilds and see how the > "official" developers do things and try to improve the general quality > of your ebuilds. Try to help out on Bug Day. Prove yourself as a > valuable asset to Gentoo and the development team will scoop you up > quickly. It's that simple. I'll do my best. I feel I owe gentoo, kde, openoffice.org, etc allot and right now the only way I can pay back is testing and submitting ebuilds. When I have the financial means I'll do that too. Robert -- [EMAIL PROTECTED] mailing list
