<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 3:46 AM, 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 class=""><div style="white-space:normal"> <p dir="auto">On 26 Sep 2016, at 21:54, Andrew Lee Rubinger wrote:</p> <p dir="auto"></p></div> </span><div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777;color:#777;margin:0 0 5px;padding-left:5px"><span class=""><div dir="auto">On Mon, Sep 26, 2016 at 3:51 PM, Max Rydahl Andersen <<a href="mailto:manderse@redhat.com" target="_blank">manderse@redhat.com</a>> </div><div dir="auto">wrote: </div><div dir="auto"> </div></span><blockquote style="border-left:2px solid #777;color:#999;margin:0 0 5px;padding-left:5px;border-left-color:#999"><span class=""><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><div dir="auto">Yes. :P </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 </div><div dir="auto">data </div><div dir="auto">providers. </div><div dir="auto"> </div><div dir="auto">to be clear - almighty notion of remote issues is explicitly kept simple </div></span><div dir="auto">so we do *not* need to treat them as backends, but mainly data providers. </div><div dir="auto"> </div></blockquote><span class=""><div dir="auto">Let's wait for Aslak on that. I'm not sold. :) </div><div dir="auto"> </div><div dir="auto">Example use case: writing/editing an issue. Done internally and would need </div><div dir="auto">to be propagated back. I view this as "under review" not a conclusion yet. </div></span></blockquote></div> <div style="white-space:normal"> <p dir="auto">creating a basic issue in the remote system - sure.<br> updating basic status and description - sure.</p></div></div></div></blockquote><div>That's a write operation. Write operations infer some contract. That's enough for me to believe it's possible we need an SPI model to fulfill it. </div><div><br></div><div>But again I think this discussion is one we'll need to continue from several angles to come at a conclusion. We haven't reached it yet. :)</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:sans-serif"><div style="white-space:normal"> <p dir="auto">creating and editing full blown issues as complete as jira or bugzilla has it ? No.</p></div></div></div></blockquote><div>Hey, Strawman, nobody said that. :P</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:sans-serif"><div style="white-space:normal"> <p dir="auto">Again, if you want full two-way sync then you are <em>not</em> talking about what we have<br> called remote issues since day one.</p></div></div></div></blockquote><div>"I never said that." - Donald Trump (he did, but I didn't)</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:sans-serif"><div style="white-space:normal"><p dir="auto"> </p> <p dir="auto">The "remote" part is first class concept - it is an issue that is not "owned" or managed by almighty directly and we want to include in overall plan - it will/can have different comment thread, different assignee etc. than the actual issue remotely.</p> <p dir="auto">Having a different backend for storing actual issues != having support for remote work items. </p> <p dir="auto">Lets at least make sure we keep those concepts/concerns separate so we are clear on what usecases we are trying to solve.</p></div></div></div></blockquote><div>+1, the concepts we need to support with regards to remote systems are what draws up the contract. And even a small contract means some SPI in my view.</div><div><br></div><div>Let's break this discussion off this thread; it's its own topic. :)</div><div><br></div><div>S,</div><div>ALR</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:sans-serif"><div style="white-space:normal"> <p dir="auto">/max<br> <a href="http://about.me/maxandersen" style="color:#3983c4" target="_blank">http://about.me/maxandersen</a></p> </div> </div> </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>