Hi James, On Tuesday, October 25, 2022 at 12:27:03 AM UTC+2 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. > To be honest that is not how I understood and read the DEP. In my understanding the goal of the DEP was to make contributions easier and put the power into the community. The role of the technical board as I understood it was to assist or step in when our other decision making processes fail. As such I didn't read the DEP 10 as a requirement for the technical board to put out calls for proposals and ideas as long as those ideas are around anyways. With the powers the technical board has, I was always rather hesitant to use them unless it seemed necessary. > And it's not just the lack of canvassing for features that's worrying; if members of the Technical Board didn't feel they were up to the job, they should have let someone know that. Getting burned out or overcommitted is a thing that happens, and a thing that was anticipated in drafting the governance -- DEP 10 has a procedure for it! > Why did no member of the Technical Board do that? Because on one hand, even with a process for it out there there might be a mental barrier to do so and admit failure to yourself. On the other hand, and this is probably my reason, is that we apparently have a different understanding of how the technical board is supposed to work. This is probably fully my fault, but the impression I got from the previous technical boards was that the role was to be rather passive and a tie-breaker when all else fails. I also think that I am not the only one who thought so. Obviously the way I see (saw) the role of the technical board is not how you and probably others see it. As such I have no problem stepping down from the technical board if people feel I over- or understepped. Cheers, Florian -- 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/6eece557-85ae-41ee-b3cf-9c2307082b37n%40googlegroups.com.
