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