On Mon January 05 2004 11:36 pm, Allen Parker wrote: <snip> > Basically, I just find that the entire ebuild submission process could > definitely be streamlined as to take less dev time and be more rewarding > for the users actually doing the submissions. Including having user > response saying, "hey, so and so just bumped package-x.y.y to package-x.y.z > and it builds fine with a renamed and digested ebuild."
I couldn't agree more. After all whats the ARCH for anyway if it's not really being used. My contributions in the past have been along the lines and compiling and testing and summiting info. I've got 7 systems to crunch with and they all use distcc. So testing and submitting bug reports to bugs.gentoo.org, kde.org, openoffice.org, etc has been my way of contributing. Now I've devoted 3 of my best systems to get really serious about giving back even more. 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. 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. Robert -- [EMAIL PROTECTED] mailing list
