Maintenance
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with issue #673 and the linked Nextcloud AIO Helm chart README; compare those references with the current chart's maintenance needs. Done would require a concrete, agreed scope and an active maintainer or review path, which this issue does not currently define.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100