Avi Alkalay kirjoitti 25.9.2022 klo 12.20:
Wow, that’s too much of a process to grasp.
Sorry if I was unclear, I did not mean that you should start the Non-responsive package maintainer process right now. The purpose of the process is to release the package in case its current maintainers are really gone and not taking care of it, so that somebody else can step in. Your pull request is now two days old, we do give more time than that for maintainers to respond. Starting the process is only appropriate if you do not get any response in a long time, like some weeks. People may be on vacation, or just happen to be really busy with other things.
The original bug that is being fixed is https://bugzilla.redhat.com/show_bug.cgi?id=1933529 But my PR also improves and fixes other packaging problems that I’ve found along the way of using the software. Also brings an upstream update. I wrote it all in the PR. I had to learn how to use Copr and at the end I have the package built for many future Fedora and CentOS versions too. It’s all there in the link provided in my first email.
Thank you for your effort. I do not know much about NextCloud, but superficially, it looks like a valuable contribution.
I’ll check your links but I’m not sure it is clear for me what else should I do beyond the PR, bug report and Copr builds. After your message, it is still unclear for me if maintainers will take over and accept my PR.
You have done all the correct things, you should not need to do anything more at this point. The NextCloud maintainers should review you pull request and merge it, unless they have some concerns, which you would then resolve together.
I suggest you wait for some time to see if the maintainers are still around. I am a bit surprised if they are not, because a new maintainer was added just recently.
Unfortunately, if your pull request really is and remains ignored, the Non-responsive package maintainer process is the only way to move the package to somebody who is willing to handle it and other work items for the package.
(Well, actually there is yet another way. People with provenpackager access can access any package, so one of them *could* merge your pull request and start the builds. But this system is not really intended as a back-up for normal package maintenance, but rather for critical issues like security fixes, and for performing large changes that affect many packages.)
_______________________________________________ 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
