Recent searches
Search options
@carlton@fosstodon.orgThis month's Stack Report is going out now. An open access issue on "Managing Django's Queue" 
https://buttondown.com/carlton/archive/managing-djangos-queue/ #django #TheStackReport
@carlton oh shizzle it’s happening!!!
@wsvincent What's happening? It's the official "End of the month or the weekend following if I was busy with work" — on schedule as ever 
@carlton just happy to snipe first comment
@carlton
> … and therefore average wait time – approaches infinity.
This. 
Some PRs wait for months for a review. There are people who message on Discord, notify on the PR, even email asking for a review and telling them "we're doing the best we can" doesn't change the wait time
@sarahboyce and even that “best we can” carries some idea that it’s not (literally!) just how queues work when they’re overrun!
“It’s mathematically improbable that we’ll get to you any time soon” would be closer to the mark 
@sarahboyce it’s also why as Fellow you have to not let it psyche you out. 
@carlton finally had time to read this.
So many good thoughts in there. Nothing that hasn't been talked about before but the arguments are compelling. I need to reread it to make notes and consolidate some ideas, namely:
1. Can we limit the drive by interactions (e.g. feature requests) until a level of community status has been achieved? I think the data is present, just not used.
2. This leads me how we quantify these interactions into levels, what makes a contributor vs maintainer?
@carlton some this I hope the Online Community Working Group could help with.
@nanorepublica @carlton yes, I’m hoping that too. You’re very much on my mind as someone who could help in this space.
@nanorepublica @carlton the more I chat to folks about this, the more I see it as a lack of context (only) from the drive by people. That’s the challenge IMO.