<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 26, 2016 at 3:36 PM, Leonard Dimaggio <span dir="ltr"><<a href="mailto:ldimaggi@redhat.com" target="_blank">ldimaggi@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 dir="ltr"><div><div><div><div><div>Hey Andrew,<br><br></div>Great idea! One question on the hierarchy - we have to make it very clear when a parent element is limited to one child or may have many children. For example, a build or deployment may have to be run in many environments.<br></div></div></div></div></div></blockquote><div><br></div><div>Yes, please call the cardinality out in the relationship model.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Actually - in re-thinking this - are ANY of these elements limited to only one child?<br></div></div></div></div></blockquote><div><br></div><div>TBD. Perhaps a user account only has one isolated build/test environment they must use for all of their projects.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><br></div>Thanks!,<br></div>Len<br><br><br></div>P.S. I noticed your reference to bug tracking - will this be an external system (bugzilla, JIRA, git, etc.) or something that we will build in?<br></div></blockquote><div><br></div><div>Yes. :P</div><div><br></div><div>It's our own view of the issue-tracking world, so it's internal. Additionally we will be using other systems as extensible backends and data providers.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><br><br></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Sep 26, 2016 at 3:07 PM, Andrew Lee Rubinger <span dir="ltr"><<a href="mailto:alr@redhat.com" target="_blank">alr@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>Something I'd like to iron out sooner than later are common terms and definitions, because getting to a mutual understanding about what we're referring to starting to be pretty relevant. :)</div><div><br></div><div>Alongside the discussions we had on this list last week, could I ask the UXD team to take the lead on moderating the definitions and relationships among the following constructs? A graphical representation of relationships where appropriate would be wonderful.</div><div><br></div><div><div>* "Almighty System" - An instance of Almighty. Contains all "Almighty User" accounts and "Almighty Projects".</div></div><div>* "Almighty Project" - A top-level container for an application shared among users/teams. May hold N "Codebases", has issue tracking, build and deployment environments. Eventually will have realtime communications.<br></div><div>* "Codebase" - Basically a repository. Can be N in a "Project"</div><div>* "Environment" - Target for running builds or deployments</div><div>* "Almighty User" - My account</div><div>* "Workspace" - The WebIDE view of an "Almighty Project". Contains the "Codebases", each of which may require its own Stack to be built/tested.</div><div>* "Stack" - Runtime to build a codebase or deploy its resultant artifacts. In practice, equates to an image which may be run as a container. NOTE: currently Che, as I understand it, has one Stack per Workspace. We'll need to address that in order to support opening, for instance, a Java codebase and a Node codebase in the same workspace.</div><div>* Other important concepts I've missed here</div><div><br></div><div><div>The terms definitions I'm using here are placeholders and could likely do with something else that's descriptive and not so overloaded. The definitions are also up for debate -- everything is open to review now, but let's try to get things at this level to gel quickly. </div></div><div><br></div><div>S,</div><div>ALR</div><span><font color="#888888"><div><div><br></div>-- <br><div><div dir="ltr">Red Hat Developer Programs Architecture<div>@ALRubinger</div></div></div>
</div></font></span></div>
<br></div></div>______________________________<wbr>_________________<br>
almighty-public mailing list<br>
<a href="mailto:almighty-public@redhat.com" target="_blank">almighty-public@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/almighty-public</a><br>
<br></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Len DiMaggio (<a href="mailto:ldimaggi@redhat.com" target="_blank">ldimaggi@redhat.com</a>)<br>JBoss by Red Hat<br>314 Littleton Road<br>Westford, MA 01886 USA<br>tel: <a href="tel:978.392.3179" value="+19783923179" target="_blank">978.392.3179</a><br>cell: <a href="tel:781.472.9912" value="+17814729912" target="_blank">781.472.9912</a><br><a href="http://www.redhat.com" target="_blank">http://www.redhat.com</a><br><a href="http://community.jboss.org/people/ldimaggio" target="_blank">http://community.jboss.org/<wbr>people/ldimaggio</a><br><br><img src="http://www.redhat.com/g/logos/RedHat_JBoss_logo.png"><br></div></div></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Red Hat Developer Programs Architecture<div>@ALRubinger</div></div></div>
</div></div>