Open nicosammito opened 1 month ago
We have implemented Namespaces
as a layer between projects/members/roles and organizations. This allows us to make the User
be a NamespaceParent
as well, which will then allow users to create projects and other things in a personal namespace.
We have implemented
Namespaces
as a layer between projects/members/roles and organizations. This allows us to make theUser
be aNamespaceParent
as well, which will then allow users to create projects and other things in a personal namespace.
Sounds great. It would be good to have a detailed docs for that
Currently it works as intended. Projects only exist within an organization. We might reconsider that in the future, but for now, it definitely isn't worth the added complexity to having projects within two different parent types.
One example of the added complexity would be members. Either you can't invite anyone to your personal projects or we would have to introduce members at a project level and then somehow combine it with the members on organization level when the project is in an organization. And if we would be to support members on project level, either all members are project administrators or we would also have to introduce roles on the project level which would have to be properly merged with organization roles for projects in organizations.
For now I would prefer that projects stay in organizations and if a user wants personal projects, they can create an organization just for themself.
Originally posted by @Taucher2003 in https://github.com/code0-tech/sagittarius/issues/173#issuecomment-2113090306