<div dir="ltr">FYI, there is a glossary at the end of the PDD, so this discussion will hopefully lead to good content for there. (I think we've got Mitch to thank for the initial glossary work.)</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 26, 2016 at 3:51 PM, Max Rydahl Andersen <span dir="ltr"><<a href="mailto:manderse@redhat.com" target="_blank">manderse@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u> <div> <div style="font-family:sans-serif"><span><div style="white-space:normal"> <p dir="auto"></p></div> <div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777;color:#777;margin:0 0 5px;padding-left:5px"><blockquote style="border-left:2px solid #777;color:#999;margin:0 0 5px;padding-left:5px;border-left-color:#999"><div dir="auto">P.S. I noticed your reference to bug tracking - will this be an external </div><div dir="auto">system (bugzilla, JIRA, git, etc.) or something that we will build in? </div><div dir="auto"> </div></blockquote><div dir="auto"> </div><div dir="auto">Yes. :P </div><div dir="auto"> </div><div dir="auto">It's our own view of the issue-tracking world, so it's internal. </div><div dir="auto">Additionally we will be using other systems as extensible backends and data </div><div dir="auto">providers. </div></blockquote></div> </span><div style="white-space:normal"> <p dir="auto">to be clear - almighty notion of remote issues is explicitly kept simple so we do <em>not</em> need to treat them as backends, but mainly data providers.</p> <p dir="auto">Could we in future use GitHub and jira as our backend for issues ? I doubt it. Could we make it so we could sync more data between the systems ? Sure - but I think we can get more done and be more useful to users if we do not try and treat the remote issue trackers as backends.</p> <p dir="auto">By definition - if they are remote issues they are <em>not</em> in a backend, if they are in our backend they are not remote issues.</p> <p dir="auto">/max</p> <p dir="auto"></p></div><div><div class="h5"> <div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777;color:#777;margin:0 0 5px;padding-left:5px"><div dir="auto"> </div><blockquote style="border-left:2px solid #777;color:#999;margin:0 0 5px;padding-left:5px;border-left-color:#999"><div dir="auto"> </div><div dir="auto"> </div><div dir="auto"> </div><div dir="auto">On Mon, Sep 26, 2016 at 3:07 PM, Andrew Lee Rubinger <<a href="mailto:alr@redhat.com" target="_blank">alr@redhat.com</a>> </div><div dir="auto">wrote: </div><div dir="auto"> </div><blockquote style="border-left:2px solid #777;color:#bbb;margin:0 0 5px;padding-left:5px;border-left-color:#bbb"><div dir="auto">Something I'd like to iron out sooner than later are common terms and </div><div dir="auto">definitions, because getting to a mutual understanding about what we're </div><div dir="auto">referring to starting to be pretty relevant. :) </div><div dir="auto"> </div><div dir="auto">Alongside the discussions we had on this list last week, could I ask the </div><div dir="auto">UXD team to take the lead on moderating the definitions and relationships </div><div dir="auto">among the following constructs? A graphical representation of </div><div dir="auto">relationships where appropriate would be wonderful. </div><div dir="auto"> </div><div dir="auto">* "Almighty System" - An instance of Almighty. Contains all "Almighty </div><div dir="auto">User" accounts and "Almighty Projects". </div><div dir="auto">* "Almighty Project" - A top-level container for an application shared </div><div dir="auto">among users/teams. May hold N "Codebases", has issue tracking, build and </div><div dir="auto">deployment environments. Eventually will have realtime communications. </div><div dir="auto">* "Codebase" - Basically a repository. Can be N in a "Project" </div><div dir="auto">* "Environment" - Target for running builds or deployments </div><div dir="auto">* "Almighty User" - My account </div><div dir="auto">* "Workspace" - The WebIDE view of an "Almighty Project". Contains the </div><div dir="auto">"Codebases", each of which may require its own Stack to be built/tested. </div><div dir="auto">* "Stack" - Runtime to build a codebase or deploy its resultant </div><div dir="auto">artifacts. In practice, equates to an image which may be run as a </div><div dir="auto">container. NOTE: currently Che, as I understand it, has one Stack per </div><div dir="auto">Workspace. We'll need to address that in order to support opening, for </div><div dir="auto">instance, a Java codebase and a Node codebase in the same workspace. </div><div dir="auto">* Other important concepts I've missed here </div><div dir="auto"> </div><div dir="auto">The terms definitions I'm using here are placeholders and could likely do </div><div dir="auto">with something else that's descriptive and not so overloaded. The </div><div dir="auto">definitions are also up for debate -- everything is open to review now, but </div><div dir="auto">let's try to get things at this level to gel quickly. </div><div dir="auto"> </div><div dir="auto">S, </div><div dir="auto">ALR </div><div dir="auto"> </div><div dir="auto">-- </div><div dir="auto">Red Hat Developer Programs Architecture </div><div dir="auto">@ALRubinger </div><div dir="auto"> </div><div dir="auto">______________________________<wbr>_________________ </div><div dir="auto">almighty-public mailing list </div><div dir="auto"><a href="mailto:almighty-public@redhat.com" target="_blank">almighty-public@redhat.com</a> </div><div dir="auto"><a style="color:#bbb" href="https://www.redhat.com/mailman/listinfo/almighty-public" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/almighty-<wbr>public</a> </div><div dir="auto"> </div><div dir="auto"> </div></blockquote><div dir="auto"> </div><div dir="auto"> </div><div dir="auto">-- </div><div dir="auto">Len DiMaggio (<a href="mailto:ldimaggi@redhat.com" target="_blank">ldimaggi@redhat.com</a>) </div><div dir="auto">JBoss by Red Hat </div><div dir="auto">314 Littleton Road </div><div dir="auto">Westford, MA 01886 USA </div><div dir="auto">tel: <a href="tel:978.392.3179" target="_blank" value="+19783923179">978.392.3179</a> </div><div dir="auto">cell: <a href="tel:781.472.9912" target="_blank" value="+17814729912">781.472.9912</a> </div><div dir="auto"><a style="color:#999" href="http://www.redhat.com" target="_blank">http://www.redhat.com</a> </div><div dir="auto"><a style="color:#999" href="http://community.jboss.org/people/ldimaggio" target="_blank">http://community.jboss.org/<wbr>people/ldimaggio</a> </div><div dir="auto"> </div><div dir="auto"> </div><div dir="auto"> </div></blockquote><div dir="auto"> </div><div dir="auto">-- </div><div dir="auto">Red Hat Developer Programs Architecture </div><div dir="auto">@ALRubinger </div></blockquote><div dir="auto"> </div><div dir="auto"> </div><blockquote style="border-left:2px solid #777;color:#777;margin:0 0 5px;padding-left:5px"><div dir="auto">______________________________<wbr>_________________ </div><div dir="auto">almighty-public mailing list </div><div dir="auto"><a href="mailto:almighty-public@redhat.com" target="_blank">almighty-public@redhat.com</a> </div><div dir="auto"><a style="color:#777" href="https://www.redhat.com/mailman/listinfo/almighty-public" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/almighty-<wbr>public</a> </div></blockquote></div> </div></div><div style="white-space:normal"> <p dir="auto">/max<br> <a style="color:#3983c4" href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a></p> </div> </div> </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" target="_blank" rel="noreferrer">https://www.redhat.com/<wbr>mailman/listinfo/almighty-<wbr>public</a><br> <br></blockquote></div><br></div>