nextcloud / nextcloud/circles

Store all team-related app-data in a team-folder

Open
#2,637 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #5011 by @Fin-c — closed without merging
0. Needs triage enhancement
Dominant language
JavaScript
Stars
177
Forks
68
Avg merge
2d 22h
Merged PRs (30d)
60

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

We should pull all team-related data together and store it in a consolidated team-folder assigned to the team.

Directory structure

For team-related resources, a hidden directory called .system should be created in the team folder by default, where sub-folders for Collectives, Deck, etc. live in.
The rest of the team-folder could be used and managed by the team-members

Example
<Team>
	.system
		Collectives
		Deck
		Talk
	Userfolder 1
	Userfolder 2
	Textfile.odt

Note: This represents the frontend path visible to the user. On disk, the path is actually

<Team-folder-ID>/files/.system/

Use case

  • At the moment, several Apps create their own directory structure inside the Nextcloud data folder. These folders get linked/mounted to the users home directory, leading to confusion and misuse of those.
  • More tidy, clear directory structure
  • Quota and permissions could more easily be controlled if data is in one place

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 specifies a team-folder layout with a hidden .system directory and the on-disk path /files/.system/, but names no implementation files or tests. Start by tracing the current team-related storage paths and reviewing closed pull request #5011. Done means the listed team data is consolidated there while user-managed files remain available in the team folder.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.