Use a monorepo style for extensions?

[perrygoy]

Having just made ~a half dozen almost-identical PRs to update copyright years and dependencies across all the ScreenPy ecosystem, i kinda don't want to have to do that again. I also noticed that all of our repos are a little tiny bit different—not on purpose, but because it's hard to set up 8 different repos exactly the same way. Some are missing Poetry; some were missing the ScreenPy-Maintainers group; some don't have Github checks...

It would be nice to have all that meta stuff handled in one spot. Maybe with Poetry we can support a monorepo environment with multiple packages deployed out of this repo?

Investigate!

[perrygoy]

looks like Poetry currently doesn't support a monorepo structure out of the box, but there is some interest in it and it's possible to bend its will to do it:
python-poetry/poetry#936
python-poetry/poetry#2270

here's a blog post and an example repo from someone who got it to work
https://gerben-oostra.medium.com/python-poetry-mono-repo-without-limitations-dd63b47dc6b8
https://gitlab.com/gerbenoostra/poetry-monorepo/

[perrygoy]

After thinking about it some more, part of the benefit to splitting the repos out like this is to "live by our own example"—part of the joy of ScreenPy and composition in general is how you can extend it additively, and all of the supported extensions living in their own repos is meant to show how to do that.

So, despite the extra work, i still think this is the right way to do it. Closing!