On Sun, 2005-09-11 at 17:50 +0200, Maurice van der Pot wrote: > If bugs are not handled in a timely manner, it is because we're > shorthanded. This is also the reason new ebuilds are often assigned to > maintainer-wanted. We'd rather not add packages to portage if there is > no developer to pick up maintenance for them. Remember that we are all > investing our spare time to work on Gentoo, we're not getting paid. > We'd rather focus on removing bugs from packages already in portage than > on adding new packages. > > Also for some packages it is hard to find a maintainer because it is > best if the maintainer is also an active user of the package. If a > relatively small group of people uses a package, it's much harder to > find a suitable maintainer. > > If you see an area that could use an extra developer working on it and > you think you could be that developer, by all means apply for the > position. > > Here are some links of interest: > http://www.gentoo.org/proj/en/devrel/staffing-needs/index.xml > http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2 > > Regards, > Maurice. >
I am well aware of all this: 2.b. Helping out Firstly; to be asked to become a developer you should either apply to an opening, or just help out whether in the form of user support or filing bug reports - we notice frequent contributors making contributions to Gentoo and we attempt to reward them by giving them the chance to become a Gentoo developer. Gentoo has many paths, and the Gentoo Developer Relations Recruitment Team is always looking out not just for developers - documentation writers and infrastructure maintainers are just as important too for our distribution to run smoothly. You should look out for openings for developers in the GWN, as well as the /topic of #gentoo-bugs on irc.freenode.net - if you feel you could fill in one of those positions, try to find a mentor who is willing to sponsor you, or contact the Gentoo Recruiters who may be able to find a mentor for you. Please do not file "New Developer" bugs on yourself since this task is designated for the mentor and any such bugs will be closed. --------------------- Certainly, I am others have fulfilled this. I have emailed the two maintainers offering to assist. No response. For some reason, rox does not show up as a staffing need. That should be corrected. I'm not going to bloat this thread. I am here to help, and I know at least one other fellow who probably would be willing to help too. It's easy, quick, and will make what users there are for rox happy. As I noted, the intent here was not to add any additional work for developers. On the contrary, the work is done already. We're already "helping out" we're filing bug reports, we're creating ebuilds that work. All that needs to be done is get them into portage. If you are unable to find a suitable developer to maintain rox, then please let me know and I will see about assembling a herd for it. -- Peter -- gentoo-dev@gentoo.org mailing list
