Wow, that’s too much of a process to grasp.

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.

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.

Thank you in advance

On Sat, Sep 24, 2022 at 18:01 Otto Liljalaakso <otto.liljalaakso@iki.fi> wrote:
Avi Alkalay kirjoitti 24.9.2022 klo 14.31:
> NextCloud is an amazing project that lets you run your own DropBox with
> steroids.
>
> Current F36 package is not performing well because it was not well
> integrated with PHP-FPM.
>
> I fixed it in my branch (
> https://src.fedoraproject.org/fork/aviram/rpms/nextcloud/commits/rawhide)
> along with upstream update to 24.0.5 and other required fixes. PR is here:
> https://src.fedoraproject.org/rpms/nextcloud/pull-request/7
>
> I'm looking for someone to approve it and make it into official Fedora.

The correct way to do this is by filing issues in Bugzilla and creating
PRs (which you have already done). In case they are ignored, you should
invoke the Non-responsive maintainer policy [1].

Note that the Non-responsive maintainer process was recently started for
NextCloud [2]. In that case, the current maintainer eventually responded
and thus is still the main admin. A new co-maintainer was also added. It
seems that there are multiple people interested in this package and
ready to contribute, I hope that an arrangement can be found so that
updates and other fixes can be handled efficiently.

As an aside, if the intent is to only package NextCloud official
releases, and not betas and release candidates, it would make sense to
configure release-monitoring.org so that it would stop suggesting those [3].

[1]:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
[2]: https://pagure.io/fesco/issue/2838
[3]: https://bugzilla.redhat.com/show_bug.cgi?id=2115524
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--

AVI ALKALAY    @avibrazil    +55(11)99659-9059    digital business card