nextcloud / nextcloud/server

Unify the concept of human being throughout Nextcloud

Open
#49,490 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

This is a bit abstract, I know. Bear with me 🙏

The problem

We currently have different categories of "humans" in Nextcloud:

  • User (a human behind a Nextcloud account, created by an admin)
  • Guest (a human behind a Nextcloud guest account, created by a user)
  • Contact (a human that lives in my contact server, not necessarily tied to a Nextcloud account)
  • Email user (a human that has been added via email to conversations and files shares)
  • Anonymus guest (a human that has joined a conversation via link)
  • Federated user (a human behind a Nextcloud account on a different instance)

It would be great if we had:

  • a unified concept of human (placeholder term) and work with features and permission of this human to determine its type
  • A unified place from where to create and edit humans
  • Automatic creation of a new human on the instance if I add an email address to a conversation or to a file
  • One click upgradeability of a human: non-user(contact) → guest user → instance user → instance admin

Thoughts @jancborchardt ?

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

No files, tests, or entry points are named. Start by reviewing how users, guests, contacts, email users, anonymous guests, and federated users are currently represented across Nextcloud. Done requires an agreed unified human concept, creation and editing path, automatic email-based creation, and upgradeability between the listed roles.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
authorization, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.