Back

@carlton excellent thoughts and articulated well as always!

Especially as I know I have been poking and prodding this topic a fair amount recently

To me it's the confusion when choosing a package to achieve a goal. There are numerous questions in my head which don't exist with core.

To be clear I agree that I don't think anymore should be added to core, but it is the social problem to solve.

@nanorepublica Thanks Andy, yes. I've been following your posts, and they've stimulated a lot of thoughts.

There's room in core for the right things, but (I agree) if we can solve the social problem the plugin approach gives more flexibility and power.

@carlton @nanorepublica I wonder if more features could have the kind of "VIP" status that Django-Tasks has: something that is created in a context where it will _likely_ make its way in core at some point, and is created with that in mind.
A feature that is first managed as an external package only while its implementation is fine-tuned and feedback is gathered from the community... But is designed to be (hopefully) merged into Django.

Could there be a specific named process for such things?

@carlton @nanorepublica Ah, true! I forgot that Django-Tasks was built with a DEP attached.
Thanks for your reply