Draft list of 

• communication regarding development TF features and bugs is done in TF JIRA
• test documentation is stored in TF repository and can be freely accessed
• build procedure is written down and it’s stored in docs.tungsten.io
• script for building TF are stored in tf-jenkins repository
• CI is managed by clearly nominated LF administrators with all needed privileges
• documentation of where release artifacts are stored (docker hub etc.) is in docs.tungsten.io
• LF administrators have access to all places where release artifacts are stored (docker hub etc.)
• release artifacts are published by LF administrators, or people designated by TSC, after TSC approval
• all code added to TF is exposed in TF either through WebUI, API, or CLI. This means there is no code that is consumed only by proprietary additions
• third party responsible for development of new features delivers Release Notes for those features at the moment of adding the code to repo
• third party responsible for development of new features delivers documentation for those features at the moment of adding the code to repo
• third party complies with TF release procedure (keeping EPIC up-to-date, TSC approvals, planning, delivery of the code, documentation etc.)
• there is a person responsible for de-contralization of the source code
• There is a roadmap of code de-contralization
• Code added to TF repo doesn’t use naming other than Tungsten Fabric / TF
• all documents / blueprints / tests added to TF repo doesn’t use naming other than Tungsten Fabric / TF
• all code migrated or added to TF has at least unit tests coverage and tests cannot be omit on development process