8:28 p.m.
Over a month ago, a bug was filed
(https://bugzilla.redhat.com/show_bug.cgi?id=476119) requesting that Falcon
be updated to 0.8.14 (it is currently 0.8.10). The maintainer has not
responded at all (multiple requests from upstream to update and one from
me). At least version 0.8.12 is needed in order to enable the Kross module
for Falcon in kdebindings (currently disabled).
There have been builds by salimma for his other packages (recently in fact:
http://koji.fedoraproject.org:80/koji/buildinfo?buildID=80649), so he's not
AWOL. What should the next course of action be? Not sure if this qualifies
for the Non-responsive policy since he is active. If it does, I'll go that
route.
--Ben
9:12 p.m.
Ben Boeckel wrote:
Over a month ago, a bug was filed
(https://bugzilla.redhat.com/show_bug.cgi?id=476119) requesting that Falcon
be updated to 0.8.14 (it is currently 0.8.10). The maintainer has not
responded at all (multiple requests from upstream to update and one from
me). At least version 0.8.12 is needed in order to enable the Kross module
for Falcon in kdebindings (currently disabled).
There have been builds by salimma for his other packages (recently in fact:
http://koji.fedoraproject.org:80/koji/buildinfo?buildID=80649), so he's not
AWOL. What should the next course of action be? Not sure if this qualifies
for the Non-responsive policy since he is active. If it does, I'll go that
route.
Email directly; offer to comaintain.
You can document those steps in the bug report if you want to start the
Non-responsive policy.
salimma is around. But if he doesn't have time for the package, having
someone as a comaintainer will help. Or perhaps prompt him to tell you
there's a reason he doesn't want to update.
-Toshio
10:02 p.m.
On Thu, Jan 29, 2009 at 9:28 PM, Ben Boeckel wrote:
Over a month ago, a bug was filed
(https://bugzilla.redhat.com/show_bug.cgi?id=476119) requesting that Falcon
be updated to 0.8.14 (it is currently 0.8.10). The maintainer has not
responded at all (multiple requests from upstream to update and one from
me). At least version 0.8.12 is needed in order to enable the Kross module
for Falcon in kdebindings (currently disabled).
There have been builds by salimma for his other packages (recently in fact:
http://koji.fedoraproject.org:80/koji/buildinfo?buildID=80649), so he's not
AWOL. What should the next course of action be? Not sure if this qualifies
for the Non-responsive policy since he is active. If it does, I'll go that
route.
Why shouldn't it? Please complete steps 1-3 before quick-jumping to step 4:
http://fedoraproject.org/wiki/PackageMaintainers/Policy/NonResponsiveMain...
Also, I'd suggest sending a direct email and/or pkgdb request. They
help sometimes.
Orcan
7:53 a.m.
On Fri, Jan 30, 2009 at 02:27:36PM +0100, Kevin Kofler wrote:
Patrice Dumas wrote:
> No, it doesn't qualify, since the maintainer is known to be active.
It does. A maintainer can be active and still neglecting some packages.
Of course, this happens. But this is not covered by that policy.
Still, there ought to be a better solution. Comaintainership?
There is no formal procedure in that case, with Rahul we proposed
forced co-maintainership, but the policy was rejected by FESCo.
FESCo said that this would be revised when provenpackager is done.
I don't think anything changed with provenpackager, but, in any case,
since it has been implemented, FESCo could revisit it.
Still this is a controversial and touchy subject, the balance between
bureaucracy and no handling of bugs is not an easy one. Actually the
focus was only on bugs with a fix provided or discussed, not for
every bugs, in our proposal:
https://fedoraproject.org/wiki/RahulSundaram/CollectiveMaintenance
--
Pat
8:30 a.m.
On Fri, Jan 30, 2009 at 03:19:11PM +0100, Kevin Kofler wrote:
Patrice Dumas wrote:
> Of course, this happens. But this is not covered by that policy.
It is. Non-responsive status is per package.
No, it is per maintainer. If a maintainer is active, it means that he
can be contacted, and the non maintainer procedure should not be
continued.
--
Pat
5566
days inactive
5566
days old
7 comments
5 participants
participants (5)
-
Ben Boeckel -
Kevin Kofler -
Orcan Ogetbil -
Patrice Dumas -
Toshio Kuratomi