On Fri, 14 Dec 2007 21:07:53 -0500, Randy Barlow wrote: > 7v5w7go9ub0o wrote: >> My concerns with this, other than my abilities, are: > >> 1. Showing proper respect to the guy who pioneered the effort to date, >> and who may simply be out of town. (This disrespect would be alleviated >> if there was an official policy encouraging "volunteer ebuilds".) > > It's not disrespectful, IMO, to do something that you don't see getting > done. Especially since it's less work for another guy. I wouldn't > worry about that point.
As a developer I agree with that point. It's always better to get bug reports for version bumps or problems that have patches attached to them, or even a simple note saying that you copied the ebuild to the new version and things work fine. > This can happen. I've submitted ebuilds for backuppc-3.0.0, and so have > many other people. In fact, the bug for it has several ebuilds that > have been submitted but haven't made it into the official tree. I think > that particular bug report might not be getting attention from the right > people or something. That doesn't mean it isn't worth doing though, > because people can still use the ebuild from the bug report. Ideally, a > dev would see that, check it out for correctness, and add it to ~arch. I guess you are talking about https://bugs.gentoo.org/show_bug.cgi? id=141018 ? It's assigned to maintainer-needed (ie, it is in the tree, but currently no developer is maintaining it). The original maintainer recently retired, so it is now in some sort of limbo. In this case the fallback would be the backup herd (who are listed on the bug), but I know that these folks are understaffed. As you can tell from this we are always looking for more developers. > Does anybody know how to call attention to a bug report that doesn't > seem to have any devs paying attention to it? I think BackupPC is a > fine product, and would like to see it in the tree for others to use. > I'm using my own ebuild successfully, as are many of the fine folks who > have contributed on that bug report. I'd just like my and others' > efforts to be something that benefits more of the Gentoo community :) A possible solution would be for you (or someone) to become a proxy maintainer, meaning that you'd get the bug reports and provide new ebuilds, and a developer (most likely someone from the backup herd) would review it and put it in the tree. Kind regards, Hans -- [EMAIL PROTECTED] mailing list
