On 04/17/2018 07:00 PM, Adam Williamson wrote:
On Tue, 2018-04-17 at 16:16 -0500, Jason L Tibbitts III wrote:
Is there some reason that you couldn't mention who the package
maintainer is?
Both Richard Marko (rmarko) and Jan Kaluža (jkaluza) are listed as
maintainers that package.
Also, I don't think you (Itamar) have fully followed the 'non-
responsive maintainer' process so far:
1. Check if the non-responsive maintainer is on vacation. To see if the
maintainer has been recently active on Fedora, fedora-active-user can
be employed.
2. File a bug against the package in Bugzilla asking for the maintainer
to respond. This bug should list the outstanding issues they need to
address. This is a must.
3. After every 7 days, the reporter adds a comment to the bug report
asking again for a response. Others can add to the bug that they also
were not successful in contacting the maintainer, or providing
additional contact information for the maintainer (i.e., alternative
email, IRC, etc).
4. After 2 failed attempts (2 weeks of no response from the
maintainer), the reporter posts to the Fedora devel list with a link to
the bug report and asks if anyone knows how to contact the maintainer.
I don't think you followed 2 or 3 before doing 4. The policy means to
file a bug *specifically about non-responsiveness*. The bug you're
referring to:
https://bugzilla.redhat.com/show_bug.cgi?id=1550697
just requests a version bump (so the maintainer may have treated it as
non-urgent), and doesn't say anything about non-responsiveness. Nor
have you asked for a response every 7 days, as required by 3.
FWIW, I know Jan Kaluza is active, however he doesn't appear to be CCed
on either bug. Perhaps he isn't configured to get bug mail for the
package. It may be a good idea to CC him on the bugs.
adding python-flask-login-owner@xxxxxxxxxxxxxxxxx in this mail.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
