I noticed tenshi [1] hasn't been updated for quite a while and I'd like to maintain it (and perl-io-bufferedselect which is a dependency in newer versions and not yet in AUR/repos) in community if 1) the current maintainer is okay with that and 2) three TUs agree because it sadly doesn't satisfy the 10 votes or 1% usage rule. I've got a working PKGBUILD for 0.12 and I'm already using it on my systems. In case I can't move it to community I'll publish that later. CC'ing the current maintainer (Ryan). [1] https://aur.archlinux.org/packages.php?ID=14088 -- Florian Pritz -- {flo,bluewind}@server-speed.net
On Sat, Jan 1, 2011 at 9:37 PM, Florian Pritz <bluewind@server-speed.net> wrote:
I noticed tenshi [1] hasn't been updated for quite a while and I'd like to maintain it (and perl-io-bufferedselect which is a dependency in newer versions and not yet in AUR/repos) in community if 1) the current maintainer is okay with that and 2) three TUs agree because it sadly doesn't satisfy the 10 votes or 1% usage rule.
I'd advise waiting a week for a reply from the current maintainer, like we do in these cases. After that, you can take it. The fact that it has gathered only 5 votes in three years troubles me. Therefore, I'm against moving it to [community] at the moment.
Florian Pritz wrote:
I noticed tenshi [1] hasn't been updated for quite a while and I'd like to maintain it (and perl-io-bufferedselect which is a dependency in newer versions and not yet in AUR/repos) in community if 1) the current maintainer is okay with that and 2) three TUs agree because it sadly doesn't satisfy the 10 votes or 1% usage rule.
I've got a working PKGBUILD for 0.12 and I'm already using it on my systems. In case I can't move it to community I'll publish that later.
CC'ing the current maintainer (Ryan).
[1] https://aur.archlinux.org/packages.php?ID=14088
-- Florian Pritz -- {flo,bluewind}@server-speed.net
There are two unrelated issues here. The first is that you want to actively maintain a package that you use and which appears to be neglected by its current maintainer. If the maintainer does not update the package in response to your email or says that you can take it, then it's obviously fine for you to take it. The maintainer may respond by updating it though, as he's been active as recently as October. The second issue is one of moving this to [community]. The package has been in the AUR for 3 years yet only has 6 votes. I doubt that it takes long to compile either, so why do you want to move it to [community]? I see no benefit in doing, and it will only complicate maintenance for you. I think you should just maintain it in the AUR, at least until it reaches the vote threshold. Regards, Xyne
On 2 January 2011 04:15, Xyne <xyne@archlinux.ca> wrote:
Florian Pritz wrote:
I noticed tenshi [1] hasn't been updated for quite a while and I'd like to maintain it (and perl-io-bufferedselect which is a dependency in newer versions and not yet in AUR/repos) in community if 1) the current maintainer is okay with that and 2) three TUs agree because it sadly doesn't satisfy the 10 votes or 1% usage rule.
I've got a working PKGBUILD for 0.12 and I'm already using it on my systems. In case I can't move it to community I'll publish that later.
CC'ing the current maintainer (Ryan).
[1] https://aur.archlinux.org/packages.php?ID=14088
-- Florian Pritz -- {flo,bluewind}@server-speed.net
There are two unrelated issues here. The first is that you want to actively maintain a package that you use and which appears to be neglected by its current maintainer. If the maintainer does not update the package in response to your email or says that you can take it, then it's obviously fine for you to take it. The maintainer may respond by updating it though, as he's been active as recently as October.
The second issue is one of moving this to [community]. The package has been in the AUR for 3 years yet only has 6 votes. I doubt that it takes long to compile either, so why do you want to move it to [community]? I see no benefit in doing, and it will only complicate maintenance for you. I think you should just maintain it in the AUR, at least until it reaches the vote threshold.
+1 leave it in the AUR.
On Sun, Jan 02, 2011 at 11:23:31AM +0800, Ray Rashif wrote:
+1 leave it in the AUR.
I also vote for leaving it in [unsupported] unless there is a good reason for moving it.
Am 01.01.2011 21:15, schrieb Xyne:
Florian Pritz wrote:
I noticed tenshi [1] hasn't been updated for quite a while and I'd like to maintain it (and perl-io-bufferedselect which is a dependency in newer versions and not yet in AUR/repos) in community if 1) the current maintainer is okay with that and 2) three TUs agree because it sadly doesn't satisfy the 10 votes or 1% usage rule.
I've got a working PKGBUILD for 0.12 and I'm already using it on my systems. In case I can't move it to community I'll publish that later.
CC'ing the current maintainer (Ryan).
[1] https://aur.archlinux.org/packages.php?ID=14088
-- Florian Pritz -- {flo,bluewind}@server-speed.net
There are two unrelated issues here. The first is that you want to actively maintain a package that you use and which appears to be neglected by its current maintainer. If the maintainer does not update the package in response to your email or says that you can take it, then it's obviously fine for you to take it. The maintainer may respond by updating it though, as he's been active as recently as October.
The second issue is one of moving this to [community]. The package has been in the AUR for 3 years yet only has 6 votes. I doubt that it takes long to compile either, so why do you want to move it to [community]? I see no benefit in doing, and it will only complicate maintenance for you. I think you should just maintain it in the AUR, at least until it reaches the vote threshold.
Regards, Xyne
My 2 cents: - The maintainer has 8 packages, 3 of which are flagged out of date. - The tenshi PKGBUILD is in very bad shape (arch is wrong, many startdirs and "|| return 1"'s). So IMHO you should not wait till the author responded, but adopt the PKGBUILD and maintain it in AUR. If it is still just a perl script as it was in 2007, then, as Xyne already said, it won't take long to "build", and so there is another point against its move to [community]. BTW, it now has 9 votes. Seems we have some audition here. :) Regards Stefan
Am 02.01.2011 18:23, schrieb Stefan Husmann:
Am 01.01.2011 21:15, schrieb Xyne:
Florian Pritz wrote:
I noticed tenshi [1] hasn't been updated for quite a while and I'd like to maintain it (and perl-io-bufferedselect which is a dependency in newer versions and not yet in AUR/repos) in community if 1) the current maintainer is okay with that and 2) three TUs agree because it sadly doesn't satisfy the 10 votes or 1% usage rule.
I've got a working PKGBUILD for 0.12 and I'm already using it on my systems. In case I can't move it to community I'll publish that later.
CC'ing the current maintainer (Ryan).
[1] https://aur.archlinux.org/packages.php?ID=14088
-- Florian Pritz -- {flo,bluewind}@server-speed.net
There are two unrelated issues here. The first is that you want to actively maintain a package that you use and which appears to be neglected by its current maintainer. If the maintainer does not update the package in response to your email or says that you can take it, then it's obviously fine for you to take it. The maintainer may respond by updating it though, as he's been active as recently as October.
The second issue is one of moving this to [community]. The package has been in the AUR for 3 years yet only has 6 votes. I doubt that it takes long to compile either, so why do you want to move it to [community]? I see no benefit in doing, and it will only complicate maintenance for you. I think you should just maintain it in the AUR, at least until it reaches the vote threshold.
Regards, Xyne
My 2 cents:
- The maintainer has 8 packages, 3 of which are flagged out of date. - The tenshi PKGBUILD is in very bad shape (arch is wrong, many startdirs and "|| return 1"'s).
So IMHO you should not wait till the author responded, but adopt the PKGBUILD and maintain it in AUR. If it is still just a perl script as it was in 2007, then, as Xyne already said, it won't take long to "build", and so there is another point against its move to [community].
BTW, it now has 9 votes. Seems we have some audition here. :)
Regards Stefan
BTW, somewhere on the homepage of tenshi I found that it has a predecessor named "oak". Since this was not in AUR yet, i made a PKGBUILD for it. http://aur.archlinux.org/packages.php?ID=45011 Regards Stefan
participants (6)
-
Evangelos Foutras
-
Florian Pritz
-
Lukas Fleischer
-
Ray Rashif
-
Stefan Husmann
-
Xyne