<div dir="ltr">If I use URLs to explain my expectations, it goes like this:<div><br></div><div><a href="http://almighty.io">almighty.io</a> -- home page of the system</div><div><a href="http://almighty.io/userid">almighty.io/userid</a> -- profile page of user</div><div><a href="http://almighty.io/userid/projname">almighty.io/userid/projname</a> -- Project 'projname' created by User 'userid'</div><div><a href="http://almighty.io/orgid">almighty.io/orgid</a> -- home page of Org 'orgid'</div><div><a href="http://almighty.io/orgid/projname">almighty.io/orgid/projname</a> -- Project 'projname' created within Organization 'orgid'</div><div><br></div><div>I'd stay away from subdomains for now -- I think we want to promote URLs like above. (Sure, we could have subdomains do a redirect, but let's not even bother with that for now.)</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 28, 2016 at 4:15 AM, Thomas Mäder <span dir="ltr"><<a href="mailto:tmader@redhat.com" target="_blank">tmader@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p> Hi Len,</p><span class="">
<div class="m_3996735339490993731moz-cite-prefix">On 26.11.2016 04:20, Leonard Dimaggio
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Don't we want users to always/only exist in the context of
a project?<br>
<br>
</div>
-- Len<br>
</div>
<div class="gmail_extra"><br>
</div>
</blockquote>
</span><p>I think we definitely don't want that. If ,like me for example,
you are a member of 4 organizations, you would have to have 4
different Identities (and probably logins). Not cool!<br>
</p>
<p>I think github gets this totally right: you have roots (accounts
which have their own subdomains or root url's), that can belong to
an organisation or an individual. You can create project inside
every root where you have sufficient privileges. You log into the
system, not a particular subdomain. You always log in as a person,
not an organization. The rest is metadata and permissions.</p>
<p>I think the whole idea gets easier to think about when we
separate containment of assets (projects, issues, etc.) from
control over assets. Think about it this way: if a user was a
container for projects, any project belonging to an organization
I'm a member of would contain the projects that the user contains
(containment being transitive). This makes no sense.</p>
<p><b>The simplest way to model the problem that fulfills the
requirements for me is to introduce the concept of an account.
Think of it like a bank account. You can open a personal account
or one for your company. For a personal account, you are
naturally the "super user", you can put money in your account,
you can close the account, etc. With a company account, you need
a designated person (or multiple persons) that have the "super
user" privilege for that account. If we want to work with
subdomains, each account gets its own subdomain.</b></p>
<p>Note that subdomains can be nothing but an alternative addressing
scheme for things. For example, we have system-unique ids for work
items, so we can always address them with
<a href="http://almighty.io/workitems/" target="_blank">almighty.io/workitems/</a><id>. Hence, we can just rewrite an
url containing a subdomain by removing the subdomain. The
important question is whether the subdomains act as a namespace.
Can you have the same project name twice in different subdomains
or not?</p><span class="HOEnZb"><font color="#888888">
<p>/Thomas<br>
</p>
<p><br>
</p>
<br>
</font></span></div>
<br>______________________________<wbr>_________________<br>
almighty-public mailing list<br>
<a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/almighty-<wbr>public</a><br>
<br></blockquote></div><br></div>