Something I note here is that it's presenting a solution, but not clearly (at least, from my reading) presenting the problem to be solved.
Is it a lack of people proposing features? If so, I'm not sure this helps -- it would, to me, suggest that only members of the Technical Board/Steering Council/whatever-it's called are supposed to do that, since it's in their job description. Would people then expect to, or be expected to, run for a seat in order to contribute something? Is it a more general lack of engagement? If so, I'm still not sure how this helps -- the idea of DEP 10 was to make it *easier* for people to step up and get involved, since it got rid of the idea of the "core team" with their special privileges, but I don't think any form of technical governance actually solves engagement issues. At best it can make engagement-specific efforts easier, but I don't see how re-centralizing authority (or creating the impression of it) would achieve that. Is it to make fundraising easier? That sounds again like something that technical governance really can't do on its own -- it needs to involve the DSF Board, and there are reasons why the DSF was historically wary about doing targeted fundraising for specific features in Django. Loosening eligibility is fine, though I agree it's going to be very difficult to write down in an enforceable way -- the DEP 10 language and process was intended primarily to prevent trolls and other bad-faith actors from being able to run effectively for the Technical Board, and there's a balance where the more you loosen it up, the more you also open the door for those kinds of people. Also, regarding the multiple roles restriction: it currently is allowed for a single person to simultaneously be on both the Technical Board and the DSF Board, and there are even procedures in DEP 10 for things like mandatory recusal for DSF Board votes and actions that affect the Technical Board. What's not allowed is simultaneously being a Merger and on the Technical Board. -- 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-mWWK0%2Bzkvi%3DCWu0e%3DbX-rOsLq4gHHdBuKQ8UL_8pRSg%40mail.gmail.com.
