[swift-evolution] Swift phases and mis-timed proposals

[Gor Gyolchanyan]

I have to constantly suppress all ideas (big or small) because I don't want to flood the mailing list with spam.
In the case of factory initializers, it seemed like something a lot of people yearn for (myself included), so pushing for it in the wake of Swift 4 seemed like an appropriate time.
But otherwise, It would be nice to get a more volatile mailing list specifically for out-of-place (and potentially huge, game-changing) ideas.
We would then collectively compose a monthly or quarterly (or whatever) summary of what has been going on in the volatile mailing list for the people with more timely priorities to be able to keep track of (including the core team).

> On Jun 12, 2017, at 2:47 AM, Erica Sadun via swift-evolution <swift-evolution at swift.org> wrote:
> 
> 
>> On Jun 11, 2017, at 3:41 PM, Haravikk via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 
>> 
>>> On 11 Jun 2017, at 22:13, Gor Gyolchanyan via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>> 
>>> I agree, this makes focusing on the right types of changes much easier and helps us avoid turning Swift into an incoherent conglomeration of random use-cases (*cough*, C#, *cough*).
>>> Now, the question is: when will be the time to officially push the factory initializers proposal and which stage should it be targeting?
>> 
>> I think there's definitely a need for greater clarity; we could really do with better announcements on the list itself as to when the new phase begins and exactly what is in-scope, it also needs to be put more clearly on the swift-evolution repository.
>> 
>> Thing is; people are going to have ideas when they have them, and want to discuss them right away. I've been caught out numerous times with proposals that are almost immediately rejected as out of scope, and still have no idea when I'm supposed to resubmit them.
>> 
>> To be honest it's demoralising, as I find myself apathetic towards my own ideas as I have no idea when to revisit them, and by the time I do I've largely lost interest and moved on to other things.
>> _______________________________________________
> 
> This.
> 
> I am sitting on a number of ideas that I think have merit (in a non-random use-case non-C# way) and I have no idea when the right time will be to bring them up. Several were marked as "bring forward to Swift 4" and obvious that was never going to happen for them.
> 
> I think having a queue to submit "proposals for eventually", written when the inspiration is there, and having a core team review (say once a month or even once a quarter) of their viability for future Swift directions would be amazingly valuable.
> 
> An example: https://github.com/apple/swift-evolution/pull/369 <https://github.com/apple/swift-evolution/pull/369>
> 
> -- E
> 
> _______________________________________________
> 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/20170612/52922921/attachment.html>