Re: [swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-10-09 Thread Adrian Zubarev via swift-evolution
Was there any progress made on this? It almost feels like were not going to move to a forum until Swift 6-7. Would be interesting to see a sign of progress here. :) Am 3. August 2017 um 23:14:16, Erica Sadun via swift-evolution (swift-evolution@swift.org) schrieb: When moving to a forum, the

Re: [swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-08-03 Thread Erica Sadun via swift-evolution
When moving to a forum, the problem becomes a thread splintering to an overwhelming tree. I'd prefer to see a single primary thread (as in the mailing lists) with breakout threads for working groups. These could be built either around already identified areas (see manifestos) or future

[swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-08-03 Thread Félix Fischer via swift-evolution
Hi! I hope I sent this email correctly and it entered the RFC thread started by Ted. My pitch: what about timeline of thread as a category? Like this: - Short term: for current release of Swift, aka 4.1 after 4.0 is released. - Mid term: for next release of Swift, aka 4.0 now, because 3.x is the

Re: [swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-08-02 Thread Tino Heth via swift-evolution
> For Swift 4, the core team identified a set of priorities. Provided the same > will be done for Swift 5, these are natural categories for the evolution part > of the forum, to my mind. We fully agree on this point. > It should have the positive effect of encouraging discussion to be focused,

Re: [swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-08-02 Thread Xiaodi Wu via swift-evolution
For Swift 4, the core team identified a set of priorities. Provided the same will be done for Swift 5, these are natural categories for the evolution part of the forum, to my mind. It should have the positive effect of encouraging discussion to be focused, and would allow even new participants to

Re: [swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-08-02 Thread David Hart via swift-evolution
> On 2 Aug 2017, at 09:44, Tino Heth via swift-evolution > wrote: > > Thanks for the update! > >> - We currently have swift-evolution and swift-evolution-announce. Should >> we use a specific “category” in the forum for "proposals that are in active >> review" —

Re: [swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-08-02 Thread Tino Heth via swift-evolution
Thanks for the update! > - We currently have swift-evolution and swift-evolution-announce. Should we > use a specific “category” in the forum for "proposals that are in active > review" — and possibly remove the need to have something like > swift-evolution-announce? Guess

Re: [swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-08-02 Thread Ted Kremenek via swift-evolution
> On Aug 1, 2017, at 10:30 PM, Rick Mann wrote: > > My inclination is to start with two broad-level categories: Evolution and > User (this presumes both the evolution and user lists are moving to > Discourse). Just to help frame the rest of the discussion on this

Re: [swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-08-01 Thread Rick Mann via swift-evolution
My inclination is to start with two broad-level categories: Evolution and User (this presumes both the evolution and user lists are moving to Discourse). To the degree that there are separate parts of evolution or user that never cross over, it would make sense to have more categories, but I

[swift-evolution] RFC: structuring forums for best use for swift-evolution

2017-08-01 Thread Ted Kremenek via swift-evolution
A while back a decision was reached to move from using mailing lists for swift-evolution to using a forum, specifically Discourse. At the time that decision was made, efforts had been already well committed for supporting the development of Swift 4 — including efforts supporting important