On Tue, May 10, 2016 at 4:54 AM, Andrew Godwin <and...@aeracode.org> wrote: > My concern around using the Mozilla money to refine it was that it was > applied for under the pretense this would be core Django, though if that's > still our intention and we keep it external for now I don't see too much of > a problem arising there.
I don't see a problem here - the main opposition seems to be about having the code in Django 1.10. This puts a lot of pressure on Tim, and there isn't enough time to field-test the design. It also feels wrong that we approach many feature additions with saying that the design should be proven in a 3rd party app, but there hasn't yet been enough time to prove the channels design. Tim's feeling about this is very important to me. He is doing an awesome job reviewing and committing patches and ensuring releases happen on time. In my opinion he should have control of what happens near feature freeze. If he doesn't have that control, it will make it impossible for him to ensure we stay on release schedule. I'm going to try to avoid writing more about this. My opinion is hopefully clear enough already. If the decision is to ship this in 1.10, then the available time should be used to make this feature as good as possible, not on this discussion. - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALMtK1GRgBGwhuEqhBf%3D%3DYyJr%2BF51dVo4CqerGPBNLfwu02hZA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
