> we don't have a mechanism to delegate the "what should we build" part of the question for work other than channels.
I guess there's two aspects to that. 1. Do Mozilla allow some flex in meeting the proposal / do we have an differing priorities now / do we want to discuss what those should be? 2. Breaking down request parsing/response rendering, as initially described in the proposal, into a call for work. (Assuming we do want to include it?) Given the release timelines I don't think we're in any great rush to make decisions here - 1.11 isn't due til April '17. Couple of options: * Plan to make a firm decision at the core team meeting in Django Under the Hood, having solicited feedback more widely first? * I could take on drafting up a call for work on the request/response portion. If there's a strong applicant for it, then we'd have plenty of time for it to start making its way in, without being remotely up against an alpha release deadline. (That way around would rather write me out of being an applicant, but might work well if we get the right person on board, and there might be scope for an a review/advisory role from Tim or myself) No firm opinions at this point, myself. Tom -- 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/c5e5e0e0-894d-4580-9a1a-2fa9267e334b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
