From section 1.2
> Multi-Tenancy: Support multiple tenants ("organizations") with isolated environments. (Multiple users/organizations must be able to use the platform simultaneously without interfering with each other.)
The #gitserver will be organisation-based.
Leak from nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 .
👀
Discussion
So, one npub can rent the git server, put his repos on it, and invite other npubs to collaborate with him in his organisation's space? 🤔
That would be the goal yes. So one npub owns the "account" which can delegate authorized npubs to projects. Ideally even allow them at an origanizational level. To me that makes the most sense of hierarchy. The only thing that differenciates a user from an organization is the authorization. Which is also required if individuals want collaboration, which is where this idea originated from.
I think the git server is a little useless if other users have to manually fork and send patches on their servers if they are part of a development team, which would then mean that the nsec would have to be shared across all developers which is bad.
Sooooo. Since its essentially identical to adding collaborators, I just defined it as an organization hierarchy.