<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Actually, several projects (Mozilla and WebKit spring to mind) both have historically had issue trackers as an essential organization tool, for just about everything from planning a new feature to organizing T-Shirt sizes for user meet ups. <div class=""><br class=""></div><div class="">Issue trackers work really well for proposals as they allow you to (for example) reference previous discussions directly, close a parallel discussion to divert people to the main topic, and so on.<div class=""><br class=""></div><div class="">Interestingly, Rust did not use Bugzilla but instead used Discourse. Iām curious why that choice was made (I suspect it was partly because use of bugzilla is a pretty big turn-off for participation?)</div><div class=""><br class=""></div><div class="">-DW<br class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 27, 2017, at 12:16 AM, Goffredo Marocchi 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=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">That is a so so reason though ;).</div><div class="">JIRA can be a discussion hub and it should be used for discussion centred around user stories, bugs, etc... it is a delivery planning/agile planning tool not a mailing list or a forum for general discussion.</div><div class=""><br class=""></div><div class="">Creating stories/items to discuss bugs, a proposal under refinement or review (the lifetime of proposals could and should go there), etc... but some of the other material on this list would be better left to something like Discourse or mailing lists.</div><div class=""><br class=""></div><div class="">I do think we should use JIRA more to discuss and leave a better trace for the evolution of proposals and bugs raised against the language though. Creating tickets in JIRA and then leaving all the details and the discussion outside of JIRA is a bad practice that we should not encourage.</div><div class=""><br class="">Sent from my iPhone</div><div class=""><br class="">On 27 Jan 2017, at 01:15, Jacob Bandes-Storch via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">UX:<div class=""><br class=""></div><div class="">*---Email------------JIRA------------Discourse----></div><div class=""><br class=""></div><div class="">š</div><div class="gmail_extra">
<br class=""><div class="gmail_quote">On Thu, Jan 26, 2017 at 5:10 PM, Derrick Ho via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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 class=""><div class="h5"><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" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div class="h5"><div dir="ltr" class="m_37941978311077495gmail_msg"><div class="gmail_extra m_37941978311077495gmail_msg"><div class="gmail_quote m_37941978311077495gmail_msg">On Thu, Jan 26, 2017 at 1:54 PM, Austin Zheng via swift-evolution <span dir="ltr" class="m_37941978311077495gmail_msg"><<a href="mailto:swift-evolution@swift.org" class="m_37941978311077495gmail_msg" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br class="m_37941978311077495gmail_msg"><blockquote class="gmail_quote m_37941978311077495gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="m_37941978311077495gmail_msg"><div class="m_37941978311077495gmail_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="m_37941978311077495gmail_msg"><br class="m_37941978311077495gmail_msg"></div></div></div></div><div dir="ltr" class="m_37941978311077495gmail_msg"><div class="gmail_extra m_37941978311077495gmail_msg"><div class="gmail_quote m_37941978311077495gmail_msg"><div class="m_37941978311077495gmail_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="m_37941978311077495gmail_msg"><div class="gmail_extra m_37941978311077495gmail_msg"><div class="gmail_quote m_37941978311077495gmail_msg"><div class="m_37941978311077495gmail_msg"><br class="m_37941978311077495gmail_msg"></div><div class="m_37941978311077495gmail_msg">Nevin</div></div></div></div></div></div><span class="">
______________________________<wbr class="">_________________<br class="m_37941978311077495gmail_msg">
swift-evolution mailing list<br class="m_37941978311077495gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="m_37941978311077495gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="m_37941978311077495gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="m_37941978311077495gmail_msg" target="_blank">https://lists.swift.org/<wbr class="">mailman/listinfo/swift-<wbr class="">evolution</a><br class="m_37941978311077495gmail_msg">
</span></blockquote></div>
<br class="">______________________________<wbr class="">_________________<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" rel="noreferrer" target="_blank" class="">https://lists.swift.org/<wbr class="">mailman/listinfo/swift-<wbr class="">evolution</a><br class="">
<br class=""></blockquote></div><br class=""></div></div>
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-evolution mailing list</span><br class=""><span class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br class=""></div></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="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>