[swift-evolution] [Discussion] mailing list alternative

Rudolf Adamkovič salutis at me.com
Mon Jan 30 09:52:43 CST 2017


+1 for either e-mail or GitHub issues. No need for yet another tool...

R+

> On 28 Jan 2017, at 01:21, Karl Wagner via swift-evolution <swift-evolution at swift.org> wrote:
> 
> 
>> On 27 Jan 2017, at 02:10, 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
> 
> 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.
> 
> I just assumed that some of our requirements (e.g. syncing with Apple’s internal “radar” system) disqualified it.
> 
> 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.
> 
> - Karl
> _______________________________________________
> 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/20170130/cc19581e/attachment.html>


More information about the swift-evolution mailing list