Allow a team to own a form

未关闭
#3,841 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript

调研方向

Start by reading the linked Nextcloud Circles issue and the referenced Deck pull request, then compare how Deck and Collectives implement team ownership. Trace how Forms currently assigns ownership and grants access; the issue does not name specific files or tests. Done means a team can own a form and team roles govern its access and lifecycle.

由索引模型根据 Issue 内容生成。

描述

1. to develop enhancement

In the effort of enabling teams to own resources:

In Nextcloud, "Shared with the team" almost always means "owned by a person, lent to the team." With the exception of Team-folders, Collectives, and Talk, resources are bound to a single user; a team is only granted access on top. That makes the team a guest in its own workspace, with important consequences:

  • Off-boarding silently destroys team assets. A team is meant to outlive any member, but delete the account of the person who created a resource and it can vanish.
  • Team roles don't govern resources. A team owner has no authority over a deck board owned by a member, and removing someone from the team doesn't touch what they own.
Task for forms
  • Please enable forms to be owned by a team
Reference

It might help to look at the implementations in the deck and collectives apps:

主要语言
JavaScript
星标
385
派生
133
平均合并
7 小时 54 分钟
30 天内合并 PR
157

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nextcloud/forms 的其他 Issue

查看 nextcloud/forms 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。