1. Submodule development process

Doing your submodule PR

Clone the repo you want to work on and create your own branch on it.
Do & publish your PR's early.
Commit often. No 3000 edits in single commit.
Use conventional-commits: "fix: fixed language bug at loginview."
Commit often - one understandable group of edits at a time. So that somebody reviewing your work can follow your progress.

Discuss your goals first so, that what you're going to do, will align to our goals. Link an issue to your PR (or if there's no issue for the thing you ought to do, write an issue of it).
Create a new branch & open a new PR soon of it.
Use PR template and fill it to describe what is this about & what is the state of this PR.
Make sure to follow our Best Practices: write code according to best practices, use pre-commit, make sure unit & integration tests pass, use conventional commits, DRY, KISS.

Discuss the issue so, that Developer knows what to take note of, while doing their work.

Support the team & developer eg. by connecting them to target users, to make sure whatever is developed will be wanted.