Outline process to create/adopt TF modules
As we develop We can think about what the "bar" should be for adoption, such as how broadly it might be used, if the inputs/outputs provide a good UX, etc.
I feel that process should follow something like this, but am certainly open to feedback:
- Work to create/prove out the module is done in a personal/team repo.
- Open a request to adopt the module within the community. But... where? This repo? Somewhere else?
- If accepted (need to clarify how acceptance/rejection is determined), the project's README is updated to include the new source paths for where the project will reside.
- The project is transferred to its new location.
- The original owner is added as a maintainer to the project.
Thoughts?