<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8"> </head> <body> <div style="font-family:sans-serif"><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> <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">On Mon, Sep 26, 2016 at 3:51 PM, Max Rydahl Andersen <manderse@redhat.com> </div><div dir="auto">wrote: </div><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">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><div dir="auto">so we do *not* need to treat them as backends, but mainly data providers. </div><div dir="auto"> </div></blockquote><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></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> <p dir="auto">creating and editing full blown issues as complete as jira or bugzilla has it ? No.</p> <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> <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> <p dir="auto">/max<br> <a href="http://about.me/maxandersen" style="color:#3983C4">http://about.me/maxandersen</a></p> </div> </div> </body> </html>