Daniel Drake <dsd <at> gentoo.org> writes: > You don't need to go to all that trouble to find that it was assigned to > maintainer-needed <at> gentoo.org. Open the bug itself:
> http://bugs.gentoo.org/show_bug.cgi?id=92501 > And towards the top, you see: > Assigned To: Default Assignee for New Packages <maintainer-needed > <at> gentoo.org> Curiously the last part '<maintainer-needed <at> gentoo.org>' does not show up in my mozilla.....? So I could not gleen that information, nor what it means that a maintainer-needed email address infers..... > > OK, if my limited cerebrial functions are correct, it's dead in the water > > until a 'maintainer' picks up the effort? > Yes, maintainer being a member of the gentoo development group. Is this an actual huminoid/cyborg, or a solicitation for somebody to maintain the package? > > Is there anything I can do (like be a poezrrr and try to maintain this > > package for the gentoo community?) > Do you know how to write and understand ebuilds? If you don't, then you > wouldn't make a very suitable maintainer :) > If you did want to become the maintainer, you could read through our developer > documentation: > http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml > http://dev.gentoo.org/~plasmaroo/devmanual/ > You'd then apply to become a Gentoo developer, and after going through the > recruitment stages, you could then add the ebuild to portage and become a > maintainer of that as well as of other ebuilds. thinking....thinking....thinking...searching...freetime...freetime... invalid...deleting....deleting...sleep...thinking...deleting_sleep.... thinking...drinking...under_consideration.... > However, on your bug, you noticed that someone posted an ebuild for the > package you requested. Marcelo is actually a Gentoo developer, so it may well > be that he has an interest in the software. You may be in luck, as he may well > develop the ebuild, add it to portage, and become the maintainer. OK, I see his name at the bottom, but, if he's to be the 'substantiator' of the jffnms ebuild, wouldn't he have fulfilled the maintainer-needed email address? Or do developers do these things in silence, clandestinely and then become the maintainer when the package is stable? Or ebuild the package and then hand it off to a poezrrr such as myself? I'm just not sure what the semantics are here. Also, being over 45 puts me at a disadvantage with the lingo and thought processes employed by those youthful minds...... Anyway it's been a month since his comments. Maybe he's bored with jffnms, or it's too difficult to create an ebuild, and he has given up and the package is orphaned? How would I know, just sit around with a digit up where no sun shines? Surely it does not take a capable person a month to install Jffnms. 1/3 of my attempts (on Debian) actuallywork, until I screwed something up. It's not an easy package to install or configure. But, when it is setup correctly, it a fantastic Network Management Package..... My strengths are more hardware and device driver type of stuff. I'm definately not the web/application specialist it takes to conquer a package such as jffnms. But, if the package has been orphaned, which I'm still trying to ascertain, then I have no choice but to noodle at the jffnms ebuild, do I? Whether I poez as the maintainer is a horse of another color, methinks..... > > There's lots of information with Bugzilla, but much of it's enlightenment > > does not seem intuitive to me, nor have a found a lucid document that > > turns bugzilla into a knowledge tool. (obviously my_bad juju) > No, we lack decent bugzilla documentation but hopefully this will be resolved > soon... Now your teasing me? Can we peep at the unfinished work, if wezz promise to withhold questions and comments? James -- gentoo-user@gentoo.org mailing list
