Page tree
Skip to end of metadata
Go to start of metadata

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 Davey
  • Build procedure is written down and it’s stored in docs.tungsten.io →  TFSC-2 - Getting issue details... STATUS  Alexandre LevineSzymon GolebiewskiVanessa Valderrama
  • Script for building TF are stored in tf-jenkins repository → Alexandre LevineVanessa ValderramaChandra Dasari
  • CI is managed by clearly nominated LF administrators with all needed privileges ->Alexandre LevineVanessa ValderramaChandra Dasari
  • Documentation of where release artifacts are stored (docker hub etc.) is in docs.tungsten.io -> Alexandre LevineSzymon Golebiewski
  • LF administrators have access to all places where release artifacts are stored (docker hub etc.) ->Alexandre LevineVanessa ValderramaChandra Dasari
  • Release artifacts are published by LF administrators, or people designated by TSC, after TSC approval → Vanessa Valderrama
  • 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 → PTLs
  • 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 Golebiewski
  • There is a roadmap of code de-contralization →  TFSC-1 - Getting issue details... STATUS  Nick Davey
  • Code added to TF repo doesn’t use naming other than Tungsten Fabric / TF → Szymon Golebiewski, PTLs
  • All documents/blueprints/tests added to TF repo doesn’t use naming other than Tungsten Fabric / TF → Szymon Golebiewski, PTLs
  • All code migrated or added to TF has at least unit tests coverage and tests cannot be omitted on the development process → PTLs


  • No labels

1 Comment

  1. Nick Davey  suggests adding project wide "roadmap" proposal and a plan for the community.