Sub-organizations

[jace]

This is not a fully thought-out proposal. It may not be feasible.

Sub-organizations are like organizations, but bound to a parent. They have a name that is unique within the scope of the parent and they can contain their own teams.

Sub-organizations are used for event editions. For example, the metarefresh organization has 2012 and 2013 sub-organizations, each of which can have distinct teams to indicate the Program Committee, Participant Directory, etc.

Post-profiles project, they'll get URLs like these:

• http://hasgeek.com/metarefresh/ <- metarefresh organization
• http://hasgeek.com/metarefresh/2012 <- 2012 sub-org
• http://hasgeek.com/metarefresh/2013 <- 2013 sub-org

[jace]

This sub-org model allows for endless nesting, which can be problematic. It also precludes the subsidiary model, where metarefresh is a subsidiary of hasgeek but has a unique global name.

[miteshashar]

Did we write this off in our last long meeting?

[jace]

We haven't discussed this.

[jace]

This ticket represents an archival use case. Lastuser's teams are meant for current use and are not suitable for archival as individuals may leave teams and organisations, which shouldn't be possible for archival. Teams are not lists. A separate ticket for lists may be warranted.