On 05-01-2024 01:50, Priscila Gutierres wrote:
I would like to apologize if it seems that I’m being rude asking for a review in this thread.
It's perfectly fine asking for a review. But that should go into its own mail to the list or, preferably, to <${package}-maintainers@fp.o>.
Currently, this thread aims to solve the maintainer situation with regards to pebble. Once that's done, the package will be handed over to an active maintainer.
Since you appear to be interested in maintaining pebble, you might even get to be added as a maintainer once the current situation has been solved.
My point of view is that if the package is a dependency and no one is looking on it, it would be a priority to keep it up to date.
That depends...
I don’t know if merging it would be possible, since the maintainer is not responding, if not, I can close it.
Leave it open. A proven packager can still merge it or you may get to merge it yourself once the package has been handed over.
Also, I noticed any maintainer can merge it.
Yes. Anyone with commit rights can merge. But currently there's only one person enlisted and only that person can add co-maintainers.
I am a new maintainer and I don’t want to create polemics, I am here to hear and learn, but if I don’t participate in the discussion is more hard to learn. In any case, I apologize again if I was impolite.
It's all good. This thread is regarding the non-responsive maintainer check [1]. It shouldn't become a discussion thread. That's all I was/am concerned about.
[1] https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
