> Has that not been occurring? Because if it hasn't, then we have a major > problem, and I don't see how the current proposal would resolve it.
It has not. While I cannot speak for the other members of the Board, I got burnt out in 2019, and then the pandemic began, and so it has not really been something I've pushed for in the past three years (and I believe I was one of the drivers of getting that in DEP 10 in the first place). We never really got into the rhythm of doing it, and I think a lot of us got busy or burnt out. My personal belief is that if something is not working, it is time for a re-analysis of the situation and a change, even if what's written down in the rules is fine on its face. This proposal is part of a larger set of community changes I would like to consider - I am, for obvious reasons, not blasting the community with them all at once, but I do believe that a strong, visible set of leaders, with a clearly outlined set of principles and shepherding a community-guided vision, is the most important thing to establish - both in terms of the Technical Board and the DSF Board. I have a much longer blog post in me about my evolving belief in the need for visible, servant leaders in OSS communities rather than trying to embrace a flat hierarchy with mechanical checks and balances - but that is for another day. Andrew On Mon, Oct 24, 2022, at 4:26 PM, James Bennett wrote: > On Mon, Oct 24, 2022 at 2:24 PM Andrew Godwin <and...@aeracode.org> wrote: >> __ >> Proposing features - this is already in DEP 10, so I more just want to get >> that aspect of the Board actually going (and, as a side-effect, have >> something to aid fundraising). I am talking with the current Board >> separately on an internal thread, where the current stance (not everyone has >> responded) is that I am personally happy to take on all the work here for >> now - but I want to make sure it's not just me in the long run, be that >> merely proving that the idea works or attracting board members who want to >> specifically mediate such discussions and interaction with the wider >> community. > > I admit I haven't been following Django development all that closely since I > mic-dropped after DEP 10 passed, but this is worrying, because canvassing for > feature proposals is not an optional thing -- DEP 10 *requires* the Technical > Board to do this at least once per feature release of Django. Has that not > been occurring? Because if it hasn't, then we have a major problem, and I > don't see how the current proposal would resolve it. > >> Overall, if all we do is change the name and start actually doing calls for >> features as outlined in DEP 10, I'll honestly be happy - but I think, given >> the most recent TB election was uncontested and several long-time Django >> contributors have told me they'd be more willing to join a TB that was less >> strictly technical-all-the-time, that it makes sense for us to also look at >> those requirements. >>> > I have concerns about this because what it really feels like is a first step > toward merging the Technical Board and the DSF Board into a single unified > governance board of everything to do with Django, and I think the split > between governance of Django-the-codebase and > Django-the-everything-the-DSF-does is a useful and important one (not least > for legal reasons). > > > -- > 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/CAL13Cg93CvLgVU567MsvqKZAiWVBxxm1-L_YuEUhjr_JRySBwg%40mail.gmail.com > > <https://groups.google.com/d/msgid/django-developers/CAL13Cg93CvLgVU567MsvqKZAiWVBxxm1-L_YuEUhjr_JRySBwg%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- 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/6196974e-a1a5-4585-87ab-02f792222509%40app.fastmail.com.
