What is the state of the "known issues" for groupfolders?

[Ra72xx]

When visiting the Github site for "groupfolders", the documentation prominently links to an extensive list of known bugs and limitations (https://github.com/nextcloud/groupfolders/issues/1414).

This issue, however, has last been updated in 2021 and has moreover been classified as "spam". At least some of the bug reports collected in this issue have already been closed or are also years old.

So, what is the current state of "groupfolders"? Is it still buggy and unusable (I currently use it - again after bad experiences years ago - and until now it seems quite usable), or should this intimidating link on the front page be removed / updated?

[Zeugma440]

Gotta +1 on that one.

Groupfolders looks like something we'd need, but I'm very intimidated by the know issues list, especially "Sharing of directories inside a group folder can lead to all kinds of problems.", where there are stagnating issues opened since 2019.

Is that module on the verge of being replaced by something else from vanilla? Or have the main contributors been called in priority on other parts of the NC ecosystem?

[solracsf]

Is that module on the verge of being replaced by something else from vanilla? Or have the main contributors been called in priority on other parts of the NC ecosystem?

I simply believe main priorities goes to actual Nextcloud Enterprise customers bug reports and features requests. Otherwise, this app relies on community contributions (as the whole Nextcloud ecosystem).

[fschrempf]

So, what is the current state of "groupfolders"? Is it still buggy and unusable (I currently use it - again after bad experiences years ago - and until now it seems quite usable), or should this intimidating link on the front page be removed / updated?

The "Known Issues" issue probably needs updating. Some things might have been resolved and new problems have occurred. As long as there is no serious effort from anyone to properly maintain this app it will remain in a state of "might work (or break) for your use-case but can cause you serious headaches at any time". Just my two cents.

[Ra72xx]

So, what is the current state of "groupfolders"? Is it still buggy and unusable (I currently use it - again after bad experiences years ago - and until now it seems quite usable), or should this intimidating link on the front page be removed / updated?

The "Known Issues" issue probably needs updating. Some things might have been resolved and new problems have occurred. As long as there is no serious effort from anyone to properly maintain this app it will remain in a state of "might work (or break) for your use-case but can cause you serious headaches at any time". Just my two cents.

You're probably right, but "groupfolders" is, on the surface, an officially supported Nextcloud app suggested by I think several "app packages" in the app store. There were AFAIK also some very optimistic press releases concerning group folders, the possibiity to use ACLs, and so on.

This does not really fit in with the seemingly missing official maintainance state of the app. I'm completely aware that most of the development is done by volunteers and I appreciate that, however then the PR department is not really synchronized with the ground reality of the code base, I'm afraid ;-).

As of now, I'm using "groupfolders" and have not encountered any bugs (this was different some years ago), but I'm a bit unsure as the way this bug report is evolving suggests that this might only be per chance. Other open source projects I use, e.g. Home Assistant, draw a very clear distinction what an "official" add on is and there is some kind of commitment (though no guarantee) of the core team to support the software, and other stuff is inofficial and then you know that it might break any time. Nextcloud seems to have another approach concerning the status "official".

[fschrempf]

This does not really fit in with the seemingly missing official maintainance state of the app. I'm completely aware that most of the development is done by volunteers and I appreciate that, however then the PR department is not really synchronized with the ground reality of the code base, I'm afraid ;-).

That's point on and something that's already been the topic of the other issue that is currently pinned here: #1215.

[provokateurin]

We are working on this, so please refer to #1414 and #1215