Hi Tom - This is a great question, and thanks for asking it. The short version is "we're not quite sure yet, and we need to work this bit out."
To go into more details, first I need to explain a bit about how the MOSS committee (of which I'm a part) works, and what it is and isn't doing. Specifically, I want to note that we're *not* making technical decisions. So when it comes to Channels work, Andrew is the "technical lead" (for want of a better term), so delegating decisions about what to do to him. Our job is to ensure that we're spending the MOSS money effectively, so what we do is: - review proposals to make sure we believe the person is capable of completing the work they've proposed, and that the budget they're proposing is reasonable (this is very similar to how we might review a GSoC proposal, with the added wrinkle of reviewing financial quotes) - review the completed work to double-check that the task is complete - coordinate between people doing the work and the DSF to get invoices paid You'll note that nowhere are we deciding things like "should this thing be built?" -- we're judging "can this person build the thing, and are they charging appropriately for their work?". This is a fairly deliberate choice, which mimics the way the DSF doesn't tell the core developer team what to build, but instead tries to spend its money in a way that helps the core team build what they want to build. So here's where things get sticky: what do we do about non-Channels work? As you note, the MOSS money was earmarked for more than just Channels. But, we don't have a mechanism to delegate the "what should we build" part of the question for work other than channels. We need to work this part out, and I'll take ownership of finding an answer here. If you have any suggestions, I would really love to hear 'em. Jacob On Tue, Jun 14, 2016 at 6:58 AM, Tom Christie <christie....@gmail.com> wrote: > Do the Django MOSS committee have any plans for the request > parsing/response rendering portion of the Django MOSS proposal? > > I'm assuming that any of the following could be reasonable choices: > > * Expecting to issue a call for work in due course, but treating channels > as the priority for now. > * Defer any decisions on it until the channels portion is deemed > sufficiently complete. > * Decide that it's no longer regarded as a priority and use the resource > elsewhere. > * Decide that it would conflict with the REST framework MOSS grant and use > the resource elsewhere. > > Asking more from a stand-point of transparency, than trying to push for a > 'call for work' to be issued. > Personally, the second option on that list probably sounds like the best > overall choice at the moment, but I think any could be valid. > > Cheers, > > 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/f1b3bf18-b8dd-49c9-8b34-9125a2ff9d6e%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/f1b3bf18-b8dd-49c9-8b34-9125a2ff9d6e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAK8PqJEFW0DC8_qbwCz827grP9bDqqhbgY_yxsM67ZYWdKSSFw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
