david at alkaline-solutions.com
Tue Dec 15 17:53:12 CST 2015
> On Dec 15, 2015, at 10:28 AM, David Owens II via swift-evolution <swift-evolution at swift.org> wrote:
> Why couple two systems together that don’t need to be? Also, using issues as a discussion list is really abusing it’s purpose. Is someone really going to go through and mark certain ones closed and others not?
There are several projects (Mozilla jumps out at me immediately) that use their bug system for most of these kinds of discussions.
(leaking into related projects I suppose: https://bugs.webkit.org/show_bug.cgi?id=19371 )
That said, we are even more on track here for Issues usage, since every evolution item is a feature request against the language. It would be really nice to be able to point new issues against pre-existing request topics, and to clearly mark them as deferred or won’t fix so they stop triggering fresh discussion.
> By coupling the two systems together, you make it significantly more challenging change how the source code is stored and where. You’ve arbitrarily said that GitHub is the way we are going to manage this project for all of time. How do you export all of the issues into another system now?
> It might be more convenient for some, but it creates long-term problems for no measurable short-term gain.
> Also, your list of steps conveniently leaves out the setup process for a GitHub account.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution