<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div></div><div><br></div><div><br>On Jan 27, 2017, at 4:21 PM, Karl Wagner via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><br class=""><div><blockquote type="cite" class=""><div class="">On 27 Jan 2017, at 02:10, Derrick Ho via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">I'm surprised there is so little support for JIRA. Anyone think it's a bad tool for the job?<br class=""><div class="gmail_quote"><div dir="ltr" class="">On Thu, Jan 26, 2017 at 6:38 PM Nevin Brackett-Rozinsky via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg">On Thu, Jan 26, 2017 at 1:54 PM, Austin Zheng via swift-evolution <span dir="ltr" class="gmail_msg"><<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg">I haven't yet seen a good answer to the question: who is going to put in the long-term commitment to host and maintain a replacement solution, moderate forums, make technical upgrades and backups, and perform all the other maintenance and administrative work it takes to properly run a system like Discourse, a web forum, or even a bug tracker.</div></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg">I will volunteer to be a moderator of the Swift forums. I have time available, and the core team surely has better things to do.</div></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Nevin</div></div></div></div>
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""><div class="">Personally, I’d prefer if we used GitHub Issues. I like keeping the current state of the project together with the known issues in it. It also has better formatting and actually supports some kind of syntax highlighting for Swift code.</div></div></blockquote><div><br></div><div>We did not go with GitHub Issues for our bug tracking for a few reasons (in no particular order):</div><div><br></div><div>(1) At the time Swift became open source, GitHub did not support arbitrary attachments to issues, which seemed a non-starter since it is important to allow users to be able to file meaningful bug reports with reproducible test cases. This has since been resolved.</div><div><br></div><div>(2) The locus of everything on GitHub is the repository. The Swift project spans a bunch of repositories, and we felt it was not desirable to have GitHub Issues, at least for the purposes of bug-tracking, on a per repository level. Instead, we wanted a central place to file issues that had its own affordances for organizing them. This is important for many reasons. First, not all the logical "sub-components" have their own repositories, and it is important to distinguish in the bug-tracker the differences between (say) compiler and standard library bugs. We also found that users frequently do not know what component — even if they are separate repositories in GitHub — to file a bug report against, and often get it wrong. Having a central bug database allows us to move things around. JIRA also provides a lot more tools out of the box for managing issues at scale.</div><div><br></div><div>Note that syncing with other bug tracking systems is not an issue with either JIRA or GitHub Issues, since both provide nice web services APIs for querying them.</div><div><br></div><div>I completely agree that GitHub provides a nicer interface than JIRA, and would be one less tool for us to use. Unfortunately, it doesn't match with some important workflows we have in mind for bug tracking. It forces an organization of issues that doesn't match with what the project needs. If those problems did not exist, we'd almost certainly be using GitHub Issues for issue tracking as that would more tightly match with the development workflows of the rest of the project (e.g., pull requests).</div><div><br></div><div>It's an interesting idea to use GitHub Issues or JIRA essentially as a forum — but it feels a bit <i>too</i> structured. I pretty much share Goffredo's opinion here on the value of a forum like Discourse versus using a tool like JIRA for discussions. The discussions on swift-dev or swift-evolution often are just discussion or even chatter — important chatter, but unstructured and ad hoc. I can see something like GitHub Issues being a useful way for tracking more official discussions, such as when a proposal is getting official discussed, but I'm not certain if doing something different for those kinds of discussions than what are done for the informal shop-and-idea-around discussions on the mailing list would be worth it.</div><div><br></div><blockquote type="cite"><div><div class=""><br class=""></div><div class="">I just assumed that some of our requirements (e.g. syncing with Apple’s internal “radar” system) disqualified it.</div><div class=""><br class=""></div><div class="">The reason why we don’t have topics every month about migrating our bug-tracking system is that JIRA (while perhaps not optimal) is at least passable. That’s more than you can say for the mailing lists, most of the time.</div><div class=""><br class=""></div><div class="">- Karl</div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></div></body></html>