[almighty] Subdomains and Model

[Leonard Dimaggio]

Don't we want users to always/only exist in the context of a project?

-- Len

On Thu, Nov 24, 2016 at 6:47 AM, Sudipta Sen <sudsen at redhat.com> wrote:

> Adding with that,
> *How will organizations be associated with the project?*
>
> >> By the URL (organisation first approach) ?
>
> In this case someone opens org_1.almighty.io and sign-up as an user.
>
> Now if the same user wants to sign-up for another organisation, org _2,
> then user goes to org_2.almighty.io
>
> This way organisation comes first in the model.
>
> In this case user can't have it's own workitem or projects.
>
> User always have to login under an organisation and create workitem or
> project.
>
> So, every workitem or project comes under an organisation.
>
> *>> Choose organisation are login (User first approach)?*
>
> User comes into almighty.io
>
> Login there and see their dashboard.
>
> They can add workitems, projects for themselves.
>
> They can search for an organisation and join it or get an invitation from
> organisation admin.
>
> They can choose associated organizations from a list and get into the
> organization's dashboard.
>
> Create workitem, projects under the organisation.
>
> On 24-Nov-2016 4:59 PM, "Michael Kleinhenz" <kleinhenz at redhat.com> wrote:
>
> Hi Todd, Team,
>
> Sudipta raised a question on the data model in connection with the url
> adressing. There was a discussion that the adressing should include
> subdomains based on the organization, like "companyXY.alm.io" going
> directly to the context of the referred company.
>
> As a user has not a 1:n connection to an org (a user can be "member"
> of many orgs over the team/teamRole connection), the user can use many
> subdomains. Also, the model supports "personal work items" that are
> directly connected ("owned") by a user. These must be avalaible under
> a generic domain for deep linking. Is that an expected behaviour?
>
> My 0.02€ on that: the subdomain is merely a "redirect" or a "masking"
> of a generic url. So "companyXY.alm.io" could also be
> "alm.io/companyXY".
>
> Also, the data model should not restrict any reasonable requirement on
> the UI or user level. So the url addressing should not have any impact
> on the underlying data model. It's just an addressing after all. And a
> synchronous one..
>
> @Sudipta, maybe you can elaborate on your concerns a bit more..
>
> -- Michael
>
> --
> Michael Kleinhenz
> Principal Software Engineer
>
> Red Hat Deutschland GmbH
> Werner-von-Siemens-Ring 14
> 85630 Grasbrunn
> Germany
>
> RED HAT | TRIED. TESTED. TRUSTED.
> Red Hat GmbH, www.de.redhat.com,
> Registered seat: Grasbrunn, Commercial register: Amtsgericht München,
> HRB 153243,
> Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
> Michael O'Neill
>
>
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>
>


-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20161125/547311ba/attachment.htm>