How to manage extensions

[aeronautes]

I'm curious about your thoughts on adding extensions to your dcs-scratchpad repo. Generally I'd like to provide more extensions to the user without further bifurcating the sourcing of scratchpad from the users perspective.

• Are you taking submissions for upstream pushes from forks? If so, how would you want maintainenance and development of those extensions handled in your repo?
• In particular I wonder when extensions have commits available often, how to deconflict that from your availability for review/merge. I'm aware of repo permissions or submodules as ways github addresses this type of issue.
• Would a more sophisticated system to allow on demand download of extensions be suitable to help decouple the development of extensions from their distribution from within the main repo?