It's been almost a month and the next step in the process for the first two DEPs is to merge the PRs and assign numbers to make them "active". The discussion for each of them can take place over the coming months. I hate to sound so cynical, but if none of the 30+ current core developers are able to find 10-15 minutes of available time over the span of a month to merge and assign a number to a DEP, I think it's safe to say that the DEP process is not going to work in its current form.
I realize that most of the core developers are not paid to work on Django, are very busy with polishing 1.7, or busy with non-Django things, but there are clearly some questions that need to be discussed (some probably just among the core devs) to figure out how to improve the current situation and avoid repeating it. The current situation is not really that bad, but I would be surprised if I was the only person that thinks any feature proposal that would require a DEP is probably not worth doing at this point in time. This discussion is more involved than activating a DEP and should probably be postponed until 1.7 is out of the way. 1) The DEP process was quickly brainstormed and put in to practice. Did this move too quickly? Should this sort of process change be more conscientious of the Django release cycle and not take place after the feature freeze? 2) The core devs know their "territory" in the code, but did enough of them agree to take on /django/deps before it was put in to practice? 3) Django lists over 30 current core developers. Does Django have enough *active* core developers for its current user base and existing processes? Is there a process in place for moving an inactive core developer from "Current Developers" to "Developers Emeritus"? Regards, Michael Manfre PS The DEP experience so far has been reminding me of a few specific examples of "government bureaucracy" that I've banged my head against many times over the years. My motivation for pressing the DEP issue is for the sake of everyone's sanity by avoiding it devolving to that level of frustration. On Thu, May 8, 2014 at 8:21 AM, Florian Apolloner <f.apollo...@gmail.com>wrote: > Hi, > > > On Thursday, May 8, 2014 2:13:52 PM UTC+2, Carl wrote: >> >> Just noticed this message, and the DEP PRs are still open a week later. > > >> Can someone shuffle this along, please? >> > > We are in the final stages of 1.7, I personally would rather focus on that > first. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" 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 http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/1d33bd04-a509-4c34-8bfe-2e4df31a3add%40googlegroups.com<https://groups.google.com/d/msgid/django-developers/1d33bd04-a509-4c34-8bfe-2e4df31a3add%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" 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAGdCwBvxj%2By_MNr8OokWWyRcwmHTFK-swSkLYTD_KiDebdRUPg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
