Please follow the unresponsive maintainer policy:

https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers

CC xpra maintainer @jgu

Well, that's weird, there's been no actual attempt to contact me. Anyway, I've just approved a co-maitainer for that package, and would welcome more.

Thanks. Closing the ticket then as there's nothing left for FESCo to discuss.

Well, that's weird, there's been no actual attempt to contact me. Anyway, I've just approved a
co-maitainer for that package, and would welcome more.

It's not true: there is a bug ticket opened since 2017-01-07 and a thread on 'devel' mailing list (2017-04-22) with a reply dated 2017-05-04.

According to the guidelines:

• File a bug against the package in Bugzilla
• After every 7 days, the reporter adds a comment to the bug report asking again for a response
• After 2 failed attempts (2 weeks of no response from the maintainer), the reporter posts to the Fedora devel list
• After other 7 days (now 3 weeks total), the reporter posts a formal request to the FESCo trac

Anyway, I've just approved a co-maitainer for that package, and would welcome more.

Hope that @sergiomb is available for updating 'xpra'.

The bug you refer to was generated by the upstream monitoring process. For the unresponsive maintainer process you're required to open a new bug requesting a response. In any case, sending an email would have caught my eye. I filter out "newhotness" emails when I am busy.

The bug you refer to was generated by the upstream monitoring process.

And assigned to you. ;)

@sagitter , Now I see that I'm Package Administrator , please ask for admin access or commit access, please I prefer that you update the package, I don't have much time . thanks .
Though that you already have commit access (at least ) .

Cheers