I think other projects use issue trackers for these sorts of topics (rather than mailing lists) primarily for the ability to capture summaries, allow searching, capture relationships (duplicates ,etc), and indicate something is deferred to a particular milestone (say swift 4 phase 2).
Not to segue the mailing list vs forum discussion again. -DW > On Sep 28, 2016, at 11:42 AM, Chris Lattner via swift-evolution > <swift-evolution@swift.org> wrote: > > >> On Sep 28, 2016, at 8:34 AM, Jay Abbott via swift-evolution >> <swift-evolution@swift.org> wrote: >> >> I don't really understand this concept of only accepting proposals for a >> specific round. I saw some ideas that were suitable for future rounds of >> proposals but not right now... Why aren't they captured in a better format >> than the mailing list archive? If you don't want to be distracted by future >> things then capture them as proposals but file them out of the way a bit so >> that people can see they exist - I would have thought this would decrease >> distractions from people bringing them up again. > > We have a list of frequently rejected proposals. I think it would be > reasonable to have an index of discussions and even written proposals in > areas of topics that are “deferred” because they are out of scope for the > current release, but not rejected. > > -Chris > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
