6:31 a.m.
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.
Meanwhile I set up a Copr with updated packages:
https://copr.fedorainfracloud.org/coprs/aviram/nextcloud/
This is what I'm running in my production server.
Thank you in advance
*AVI* ALKALAY @*avibrazil* +55(11)99659-9059 <+5511996599059> *digital
business card* <https://avi.alkalay.net/card/>
4 p.m.
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_packa...
[2]: https://pagure.io/fesco/issue/2838
[3]: https://bugzilla.redhat.com/show_bug.cgi?id=2115524
4:20 a.m.
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(a)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_packa...
[2]: https://pagure.io/fesco/issue/2838
[3]: https://bugzilla.redhat.com/show_bug.cgi?id=2115524
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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 <+5511996599059> *digital
business card* <https://avi.alkalay.net/card/>
5:03 a.m.
On 25-09-2022 11:20, Avi Alkalay wrote:
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.
Avi, I think you've already done more than what most people would do in
this situation.
The current package maintainers will have been notified of your pull
request. Seeing that a non-responsive maintainer process was already
started once, they may have little time to spent on package maintenance.
Maybe, as one last effort, you could try to reach out to the package
maintainers directly and ask them if they'd be willing to add you as a
co-maintainer. Christopher (lcts) is the maintainer, the rest are
co-maintainers. You can look them up in FAS.
I hope that helps and thank you for your contribution.
-- Sandro
2:38 p.m.
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.)
2:42 p.m.
Sep 25, 2022 4:22:14 AM Avi Alkalay <avibrazil(a)gmail.com>:
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.
Hi Avi,
It looks like the pull request has only been open for two days. You've
done all that's is needed. Allow the maintainers some time to review your
pull request.
If you are interested in co-maintaing the package, you can ask the
maintainers by emailing nextcloud-maintainers(a)fedoraproject.org.
--
Best,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
4:41 p.m.
On 25-09-2022 21:42, Maxwell G via devel wrote:
If you are interested in co-maintaing the package, you can ask the
maintainers by emailing nextcloud-maintainers(a)fedoraproject.org.
Thanks for correcting me. That's indeed the normal and documented
procedure of contacting package maintainers. It had slipped my mind.
-- Sandro
588
days inactive
589
days old
6 comments
4 participants
participants (4)
-
Avi Alkalay -
Maxwell G -
Otto Liljalaakso -
Sandro