Draft list of objectives to increase community transparency and engagement
Release
CI
Marketing
- Communication regarding the development of TF features and bugs is done in TF JIRA → Marek Chwal, Nick Davey
- Test documentation is stored in the TF repository and can be freely accessed → Szymon Golebiewski Nick Daveyaccessed
- Build procedure is written down and it’s stored in docs.tungsten.io →
Alexandre Levine, Szymon Golebiewski, Vanessa ValderramaJira server Tungsten Fabric columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 82691efe-91a0-3cff-8e71-932ce5d4700b key TFSC-2 - Script for building TF are stored in tf-jenkins repository → Alexandre Levine, Vanessa Valderrama, Chandra Dasarirepository
- CI is managed by clearly nominated LF administrators with all needed privileges ->Alexandre Levine, Vanessa Valderrama, Chandra Dasari
- Documentation of where release artifacts are stored (docker hub etc.) is in docs.tungsten.io -> Alexandre Levine, Szymon Golebiewski and what naming convention they follow
- LF administrators have access to all places where release artifacts are stored (docker hub etc.) ->Alexandre Levine, Vanessa Valderrama, Chandra Dasari
- Release artifacts are published by LF administrators, or people designated by TSC, after TSC approval → Vanessa Valderramaapproval
- 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 → PTLsadditions
- 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 → Nick Davey, Szymon Golebiewskicode
- There is a roadmap of code de-contralization →
Nick DaveycontralizationJira server Tungsten Fabric columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 82691efe-91a0-3cff-8e71-932ce5d4700b key TFSC-1 - Code added to TF repo doesn’t use naming other than Tungsten Fabric / TF → Szymon Golebiewski, PTLsTF
- All documents/blueprints/tests added to TF repo doesn’t use naming other than Tungsten Fabric / TF → Szymon Golebiewski, PTLsTF
- All code migrated or added to TF has at least unit tests coverage and tests cannot be omitted on the development process → PTLsfrom the development process
- Marketing channels (twitter, linkedin etc.) are managed by a person selected by the TSC or LFN representative