On Wed, Oct 26, 2022 at 4:34 PM Andrew Godwin <and...@aeracode.org> wrote:
> I have copied in the DSF Members mailing list as it is a > governance-related DEP, but if we could keep all discussion on the thread > in the Django Developers mailing list, as per DEP 0001, that would be great. > My main concern remains the thing I've been saying repeatedly in the other thread: how does this actually solve a problem that Django is facing right now? We've established that the Technical Board was not carrying out its duties. There's also been a claim advanced that probably there is not a replacement slate of board members who would step up and have the capacity to do what DEP 10 asks. So, either this new DEP is intended to be a slight clarification of the Technical Board's role, in which case I don't see how saying "same as before, but this time we actually expect you to do the thing" solves the issue. Or it's intended to be a first step toward a more active group, in which case I don't see how it can succeed given that a lower required level of activity has already failed. I also have concerns with the "Steering Council" name. In Python's case it's something resembling Django's old technical board, which was made up of core devs elected by core devs (technically Python does it as "must be nominated by a core dev", not "must be a core dev", but in practice it makes little difference). I don't want to create the impression that Django's governance looks even a little bit like that, because it doesn't look like that. > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAL13Cg-gULvacpiR6y8ZM89FKHeatoaaLZcj0Vrx9gPqGXG-XA%40mail.gmail.com.
