Draft list of objectives to increase community transparency and engagement
- Communication regarding the development of TF features and bugs is done in TF JIRA
- Test documentation is stored in the 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 and what naming convention they follow
- 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
- PTL responsible for the development of new features delivers Release Notes for those features at the moment of adding the code to the repo
- PTL responsible for the development of new features delivers documentation for those features at the moment of adding the code to the repo
- PTL 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 omitted from the development process
- Marketing channels (twitter, linkedin etc.) are managed by a person selected by the TSC or LFN representative
- Transparent project roadmap for the next release
TSC priorities
| Choices | Your Vote | Current Result: (0 Total Votes) |
|---|---|---|
| Communication regarding the development of TF features and bugs is done in TF JIRA | ||
| Test documentation is stored in the 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 and what naming convention they follow | ||
| 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 | ||
| PTL responsible for the development of new features delivers Release Notes for those features at the moment of adding the code to the repo | ||
| PTL responsible for the development of new features delivers documentation for those features at the moment of adding the code to the repo | ||
| PTL 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 omitted from the development process | ||
| Marketing channels (twitter, linkedin etc.) are managed by a person selected by the TSC or LFN representative | ||
| Transparent project roadmap for the next release |