You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 14
Next »
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
- CI infrastructure is documented
- 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
This operation will clear all the macro's data.
This cannot be undone.
Question |
Total Votes |
Average Score |
Communication regarding the development of TF features and bugs is done in TF JIRA
|
0
|
0.00
|
Test documentation is stored in the TF repository and can be freely accessed
|
0
|
0.00
|
Build procedure is written down and it’s stored in docs.tungsten.io
|
0
|
0.00
|
Script for building TF are stored in tf
|
0
|
0.00
|
CI is managed by clearly nominated LF administrators with all needed privileges
|
0
|
0.00
|
CI infrastructure is documented
|
0
|
0.00
|
Documentation of where release artifacts are stored (docker hub etc.) is in docs.tungsten.io and what naming convention they follow
|
0
|
0.00
|
LF administrators have access to all places where release artifacts are stored (docker hub etc.)
|
0
|
0.00
|
Release artifacts are published by LF administrators, or people designated by TSC, after TSC approval
|
0
|
0.00
|
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
|
0
|
0.00
|
PTL responsible for the development of new features delivers Release Notes for those features at the moment of adding the code to the repo
|
0
|
0.00
|
PTL responsible for the development of new features delivers documentation for those features at the moment of adding the code to the repo
|
0
|
0.00
|
PTL complies with TF release procedure (keeping EPIC up
|
0
|
0.00
|
There is a person responsible for de
|
0
|
0.00
|
There is a roadmap of code de
|
0
|
0.00
|
Code added to TF repo doesn’t use naming other than Tungsten Fabric / TF
|
0
|
0.00
|
All documents/blueprints/tests added to TF repo doesn’t use naming other than Tungsten Fabric / TF
|
0
|
0.00
|
All code migrated or added to TF has at least unit tests coverage and tests cannot be omitted from the development process
|
0
|
0.00
|
Marketing channels (twitter, linkedin etc.) are managed by a person selected by the TSC or LFN representative
|
0
|
0.00
|
Transparent project roadmap for the next release
|
0
|
0.00
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
jenkins repository
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
to
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
contralization of the source code
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
contralization
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|
Choices |
Your Vote |
Current Result: (0 Total Votes) |
4-Critical |
|
0
Votes
, 0%
|
3-Highly needed |
|
0
Votes
, 0%
|
2-Needed |
|
0
Votes
, 0%
|
1-less needed |
|
0
Votes
, 0%
|