Listen, I'd like to chime in on this thread. Our policy (where "our" reflects Gentoo DevRel -- DevRel == Developer Relations) is that if you want to be a dev, don't ask to be a dev, just be a dev. You don't NEED CVS access to develop, just to commit something to the tree. In that regard, Avenj's point (about proving thyself) was simply: do the work, create a relationship with the gentoo dev team via bug day or through bugzilla and cvs access follows as a natural course. It's not specifically a wall, as much as it is establishing a relationship of mutual trust. That does NOT mean that fraternising with the devs grants you developerhood, what it does mean is that if your work is going by seemingly unnoticed, point it out to someone. More often than not, however, one of the developers at least will notice your work.
As for ebuilds sitting in the tree for a year, that means a couple of things: 1. Nobody on the dev team has the hardware to test it (like the opensmartcard bug [1]). 2. There is simply a low demand for that -- if more people tested and chimed in on a bug with their results it would likely see more action. You see, I've taken on maintainership for some packages, with the express understanding that any bugs get assigned to the initial submitter. Basically, things can be worked out, you just have to talk to someone about it. Hope that helps. Thanks, -- Seemant Kulleen Developer and Project Co-ordinator, Gentoo Linux http://dev.gentoo.org/~seemant Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E
signature.asc
Description: This is a digitally signed message part
