DevHeads.net

Unresponsive maintainer: mflobo

Hello,

I've been trying to contact mflobo in order to get some packages updated
but didn't get any response:

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1711394" title="https://bugzilla.redhat.com/show_bug.cgi?id=1711394">https://bugzilla.redhat.com/show_bug.cgi?id=1711394</a>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1711395" title="https://bugzilla.redhat.com/show_bug.cgi?id=1711395">https://bugzilla.redhat.com/show_bug.cgi?id=1711395</a>

Output of fedora_active_user.py:

Last login in FAS:
mflobo 2017-02-23
Last action on koji:
Tue, 15 Jan 2019 package list entry revoked: python-muranoclient in
trashcan by oscar
Last package update on bodhi:
2016-04-15 15:26:46 on package python-muranoclient-0.8.4-1.fc24
Last actions performed according to fedmsg:
- <a href="mailto: ... at redhat dot com"> ... at redhat dot com</a> updated nothing on RHBZ#1711395 'Update to latest
release upstream 1.12.0' on 2019-05-17 18:58:33 ()
- <a href="mailto: ... at redhat dot com"> ... at redhat dot com</a> updated nothing on RHBZ#1711394 'Update to latest
released upstream 3.8.0' on 2019-05-17 18:55:32 ()
- upstream-release-monitoring updated 'short_desc' on RHBZ#1445107
'python-mistralclient-3.9.0 is available' on 2019-05-16 11:14:55 ()
- upstream-release-monitoring updated 'short_desc' on RHBZ#1445107
'python-mistralclient-3.8.1 is available' on 2019-05-14 17:11:52 ()
- upstream-release-monitoring updated 'short_desc' on RHBZ#1445107
'python-mistralclient-3.8.0 is available' on 2019-03-08 22:12:32 ()
- <a href="mailto: ... at in dot waw.pl"> ... at in dot waw.pl</a> updated 'bug_status', 'cf_fixed_in', and 'resolution'
on RHBZ#1579356 'python-mistralclient has no dist tag' on 2019-02-15
18:02:32 ()
- <a href="mailto: ... at redhat dot com"> ... at redhat dot com</a> updated 'bug_status', 'flag.needinfo', and
'resolution' on RHBZ#1560485 'python-muranoclient: Switch to Python 3 ...'
on 2019-01-09 15:27:54 ()
- <a href="mailto: ... at redhat dot com"> ... at redhat dot com</a> updated 'flag.needinfo' on RHBZ#1560485
'python-muranoclient: Switch to Python 3 ...' on 2019-01-09 15:27:53 ()
- <a href="mailto: ... at redhat dot com"> ... at redhat dot com</a> updated 'status', 'cf_fixed_in', 'resolution', and
'cf_last_closed' on RHBZ#1649010 'python-vitrageclient: Remove
(sub)packag...' on 2018-11-19 14:36:19 ()
- <a href="mailto: ... at redhat dot com"> ... at redhat dot com</a> updated 'status' and 'assigned_to' on RHBZ#1649010
'python-vitrageclient: Remove (sub)packag...' on 2018-11-19 14:29:14 ()

According to <a href="https://src.fedoraproject.org/user/mflobo" title="https://src.fedoraproject.org/user/mflobo">https://src.fedoraproject.org/user/mflobo</a> he's the only
maintainer for python-mistralclient, python-congressclient and python-yaql.
As these three are somehow related to OpenStack packages, i'd be happy to
take them as maintainer.

Best regards,

Alfredo

Comments

Re: Unresponsive maintainer: mflobo

By Didier Fabert at 05/22/2019 - 02:36

Hi,

It's a little off topic, but where your fedora_active_user.py script
come from ?

I have the same problem and according to the
Policy_for_nonresponsive_package_maintainers[1], the "official" repo is
on github[2].

I cannot run successfully this script with python2 or python3,and with
the latest fedora_cert[3] lib.

Le 21/05/2019 à 15:13, Alfredo Moralejo Alonso a écrit :

Re: Unresponsive maintainer: mflobo

By Alfredo Moralej... at 05/23/2019 - 11:40

On Wed, May 22, 2019 at 9:37 AM Didier Fabert <didier. ... at gmail dot com>
wrote:

Re: Unresponsive maintainer: mflobo

By Matthias Runge at 05/27/2019 - 02:55

On Thu, May 23, 2019 at 06:40:34PM +0200, Alfredo Moralejo Alonso wrote:
I believe, I am Marcos sponsor; thus I went ahead and merged the PRs.

IIRC, he moved on to something unrelated to OpenStack, thus I'd make
sense to at least grant commit access to the OpenStack related packages.

Matthias

Re: Unresponsive maintainer: mflobo

By Alfredo Moralej... at 05/27/2019 - 08:42

On Mon, May 27, 2019 at 9:56 AM Matthias Runge <mrunge@matthias-runge.de>
wrote: