nextcloud / nextcloud/groupfolders

Improving development process and quality of the app

Open
#1,215 29 comments 44 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion question
Dominant language
PHP
Stars
343
Forks
106
Avg merge
2d 3h
Merged PRs (30d)
34

Description

I'm just a regular NC user/admin and don't know much about NC development and internals, but I made a few observations, especially with the groupfolders app that kind of make me feel like there should be some improvements.

  1. There are a lot of open and unhandled issues (no replies, no labels, etc.).
  2. There are a lot of duplicate issues.
  3. There are quite a few severe bugs that exist for years and haven't been fixed.
  4. Some features (e.g. ACL) are quite complex and there's not enough docs.

I guess that this app is used by many people and should get the same level of attention and maintenance as the NC server repository.

Please note, that I don't mean to blame anyone. I really appreciate the huge amount of work all of you put into this.
Still I would like to ask if anyone sees some way to improve things? Is there even an officially assigned maintainer or team of maintainers for this app?

I would be even willing to add some small bounties on long-standing issues that affect me if there is any reliable platform to do this.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points and asks broadly about maintainership, issue triage, documentation, and bounties. Start by reviewing the groupfolders repository’s open issues and maintainer process; the work is only done when a concrete, agreed improvement with defined ownership and scope is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.