On 8 mai 2014, at 16:26, Michael Manfre <[email protected]> wrote: > 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.
If you consider core devs who made a non-trivial commit in the last three months, the baseline isn't 30+ people, it's just a handful. If you further reduce this set to the people who were at PyCon when the idea of DEPs was discussed, you probably arrive at zero. Core devs who aren't active anymore often get excited at conferences but that doesn't give them free time to execute afterwards. Besides the 10-15 minutes could easily turn into becoming the contact person for these PEPs :-) > 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? I think we're mostly missing someone to bootstrap the process. Since no one in the core team appears to be interested, if someone else wants to take the matter into his/her own hands, I'm happy to advocate for partial committer status (https://docs.djangoproject.com/en/dev/internals/contributing/committing-code/#commit-access). Contact me privately if you wish to discuss this. > 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? Undoubtedly. > 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"? Classifying core devs wouldn't achieve much. Removing core devs has no practical benefit, on the contrary. Our availability comes and goes. That's life! However, we all know that there's no such thing as too many core devs and that we would benefit from a larger core team. -- Aymeric. -- 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 [email protected]. To post to this group, send email to [email protected]. 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/3F8DCDA4-8187-48E5-8A7B-AAF68F6E9719%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
