Project contribution mechanism

[AlexisTercero55]

          FYI: @xavierVG 

Although PR flow is not defined yet as part of Agile MLDevOps follow up milestone, we muts to follow the next PR flow.

14-byte-pair-encoding-on-mwt-14-en2de => Development => QA-TEST => main

As you can see direct PR to main branch is blocked and protected by signed commits.

• In Development we clear the code and it serves to quickly share work.
• In QA-Test we apply tests and we must get a consensus on what is going to be published in the main branch.

Thanks for creating this DevOps scenario that need to be addressed from my side. I'm going to work in this standard ASAP

• [ ] Project contribution mechanism design.
• [ ] Edit README in order to show this contribution requirements.

Originally posted by @AlexisTercero55 in https://github.com/AlexisTercero55/AI-Research/issues/20#issuecomment-2134255951