[swift-evolution] [Discussion] mailing list alternative

[David Waite]

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. 

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.

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?)

-DW

> On Jan 27, 2017, at 12:16 AM, Goffredo Marocchi via swift-evolution <swift-evolution at swift.org> wrote:
> 
> That is a so so reason though ;).
> 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.
> 
> 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.
> 
> 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.
> 
> Sent from my iPhone
> 
> On 27 Jan 2017, at 01:15, Jacob Bandes-Storch via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> 
>> UX:
>> 
>> *---Email------------JIRA------------Discourse---->
>> 
>> 😉
>> 
>> On Thu, Jan 26, 2017 at 5:10 PM, Derrick Ho via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> I'm surprised there is so little support for JIRA. Anyone think it's a bad tool for the job?
>> On Thu, Jan 26, 2017 at 6:38 PM Nevin Brackett-Rozinsky via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> On Thu, Jan 26, 2017 at 1:54 PM, Austin Zheng via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 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.
>> 
>> 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.
>> 
>> Nevin
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
>> 
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
>> 
>> 
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170127/610c0bf4/attachment.html>