We are closing all the old issues to have more clarity in our backlog for Zanata project. Feel free to re-open or leave a comment if you require our attention on your Jira.

Carlos Munoz commented:

Ding, as I understand it an Organization is a group of projects, while a team is a group of people. An organization will eventually (*not part of this initial feature*) have multiple teams all with potentially different permissions over the projects of the organization.

I share your concern over permissions for projects in an organization, but there is still some discussion to be had on that front and I think we haven't arrived at a final implementation decision.

Ding-Yi Chen commented:

(In reply to Luke Brooker from comment #3)
> Hi Noriko,
>
> For your situation, the way to handle that would be with teams inside of an
> organisation. Users can be assigned to teams and each team can be assigned
> to multiple projects.
>
> This doesn't mean this is our final solution though, as to get this right
> (especially in Fedoras case) it will need further thought and discussion.

What's difference between team and organization?
It looks like we need to implement team before organization.

Otherwise according to what I perceive, FESCo is not going to like the idea of thousands of maintainers can push and pull one another projects.

Luke Brooker commented:

Hi Noriko,

For your situation, the way to handle that would be with teams inside of an organisation. Users can be assigned to teams and each team can be assigned to multiple projects.

This doesn't mean this is our final solution though, as to get this right (especially in Fedoras case) it will need further thought and discussion.

Noriko Mizumoto commented:

This sounds great base. Let me allow to picture an example.

(In reply to Luke Brooker from comment #1)
> Update from meeting:
>
> Initial Plan:
>
> - Users create an Organisation as maintainer/owner

A user who can create an Org should be able know current size of Org and possible growth which can impact the server resource/performance and the people translators. Naturally it should not allow every user to create Org easily. This user is kinda org admin? Who is eligible? What is the condition?

For example, Fedora, I may prefer to have ORG per development cycle. One ORG follows one development cycle. Any projects follows this particular development cycle join this ORG, but basically not allowed to create separate ORG without clear reason. Otherwise some projects just want to create own ORG, and over time the number of ORGs will become uncontrollable.