Maintenance

[wrenix]

Hello together, this project is current not well maintained. There is a lack of maintainer, so that we are not able to review and develop like new major releases (see #673 ) or even other setups e.g. S3.

Therefore the question how is willing to review / maintain and could support this project.

Just to be fair, Next cloud itself do not like to maintain it anymore in favour of https://github.com/nextcloud/all-in-one/blob/main/nextcloud-aio-helm-chart/readme.md
So we are all volutiners here.

[ojsef39]

Nextcloud AIO just doesn't work for me / my use case, i hope this repo sees some more love in the future.
I sincerely appreciate any efforts from contributors to this repo and i want to see that continue :)

[varet80]

As I prefer how the current nextcloud chart works. I am interested in helping out.

Also running two private instances for my personal data.

[echo-devnull]

Between the two helm charts, this one allows for much more advanced stuff like pointing to kubernetes secrets for passwords, tokens, etc. Which works great with external-secrets.

The quality is also much higher, templates, helpers, structure, etc. I'm left seriously wondering why the AIO version is preferred?

[DreamingRaven]

I can help out if needs be. I both use this chart (https://gitlab.com/deepcypher/dc-kc/-/tree/master/charts/nextcloud?ref_type=heads) and develop my own charts https://gitlab.com/GeorgeRaven/raven-helm-charts and my own library chart to stop repeating logic everywhere https://gitlab.com/GeorgeRaven/raven-helm-charts/-/tree/main/charts/corvid?ref_type=heads

This nextcloud helm chart works out a bit differently to my usual, but im up to help where is reasonable, and I can't say I am a PHP aficionado.

[varet80]

Between the two helm charts, this one allows for much more advanced stuff like pointing to kubernetes secrets for passwords, tokens, etc. Which works great with external-secrets.

The quality is also much higher, templates, helpers, structure, etc. I'm left seriously wondering why the AIO version is preferred?

I agree,
also found the naming of the files in the AIO a bit odd.

Generally speaking this chart is awesome.

[echo-devnull]

Also see: nextcloud/all-in-one#6570

Basically: Do not use kubernetes for Nextcloud?!? That seems .. odd to say the extreme least. Seeing as all of Europe is looking for EU alternatives for US options in this space.

And most will want to use Kubernetes to create a homogeneous environment for themselves.

[szaimen]

Also see: nextcloud/all-in-one#6570

Basically: Do not use kubernetes for Nextcloud?!? That seems .. odd to say the extreme least. Seeing as all of Europe is looking for EU alternatives for US options in this space.

And most will want to use Kubernetes to create a homogeneous environment for themselves.

Hi, just to make this clear:

You are misunderstandind my comment.

Also, this is my personal view on the topic.

Additionally, you are of course free to use whatever project you want!

Thanks!

[ojsef39]

@szaimen Could you maybe explain the reasoning behind that comment a little bit more?
I cant think of something that makes docker better suited than kubernetes, since you can do basically the same stuff in k8s that you could do with the container or am i missing something really obvious here?

[szaimen]

@szaimen Could you maybe explain the reasoning behind that comment a little bit more?
I cant think of something that makes docker better suited than kubernetes, since you can do basically the same stuff in k8s that you could do with the container or am i missing something really obvious here?

Lets continue the discussion here: nextcloud/all-in-one#6570

[echo-devnull]

Also see: nextcloud/all-in-one#6570
Basically: Do not use kubernetes for Nextcloud?!? That seems .. odd to say the extreme least. Seeing as all of Europe is looking for EU alternatives for US options in this space.
And most will want to use Kubernetes to create a homogeneous environment for themselves.

Hi, just to make this clear:

You are misunderstandind my comment.

Ah that is quite possible. I was reacting to: The chart was created for users that rely on k8s and cannot switch platforms
Thinking you meant: you should switch to docker if you are able to.

Also, this is my personal view on the topic.

Also: check. I was under the impression you are part of Nextcloud as a whole ;-)

[varet80]

The main subject was: how can somebody from Community, become maintaner and/or able to create PR's and approve PRs in order to keep this project moving?

[thibaultamartin]

I've been impressed by the quality and flexibility offered by these charts, and I would love to be able to keep using them. I also understand that Nextcloud has commercial incentives to keep a proprietary chart for their paying customers.

Right now the situation strikes me as odd:

• On one hand, this repo and the charts on artifacthub.io are registered under the official nextcloud namespace.
• On another, Nextcloud is not involved in these charts' maintenance and it is unclear how someone can become a co-maintainer. Because nextcloud is several versions behind, it puts these charts' users at risk, and it puts Nextcloud's reputation at risk.

I can think of several ways forward:

• Nextcloud could ask the community to fork this repository and archive it, so it doesn't look like an official, Nextcloud-maintained chart. Potentially upsetting for some, but at least sets expectations for users.
• Nextcloud could try to make this chart and the helm AIO chart converge (in the sense that this chart would remain free, and the helm AIO one would be for paid customers, potentially with extra features, and with paid support). This would make the charts and Nextcloud easy to adopt, and make it easier for Nextcloud to sell paid support for customers who need it (similarly to what Element does with ESS Community / ESS Pro). I believe this approach has the potential to make everyone happier.
• The community and Nextcloud could agree on a governance process, with commitments from Nextcloud to actually promote maintainers who have been nominated.

@szaimen is there someone at Nextcloud in charge of relationships with the community who'd be open to talk about it?

[wrenix]

@varet80 thank you to bring us back to the topic.
The idea of this Issue is evaluate if we want still maintain this and how like to help.
Like @thibaultamartin described the options, I believe we are at the point of the last Options, that it still is maintained here (what I prefer to be as close as possibility to the original project, so that it is easy to find hopefully a well maintained chart) and the Nextcloud seems to be fine to promote persons here to maintainer (like me and @provokateurin was).

It looks like @varac, @DreamingRaven and @thibaultamartin offer helps.

I do not know how to handle a good Community and onboarding.
So at first, please speed some time to write me if i am to complex or unfair to new maintainer.

My first thoughts is that you two start to review and maybe test the existing PRs, i am not sure if you have even make a review here.
PS: Beside the Problem of have less time to spend here, I have no S3 setup where some PRs need to be tested.

If we like the way we are working, I will make suggestion to the Talk-Channel like @provokateurin . (personal I do not use Talk, so i had to use a guest account therefore - or we switch to something like Matrix).

PS: This are my thought just because I am already a person how make some things here and got merge-permission for PRs created by others. If somebody else like to organise the Maintained I am even more happy.