starlingx/governance
Code Issues Proposed changes
Files
9ef066dbb9c8a89518606231216f2a62db91e0e9
governance/reference/tsc/index.rst
Dean Troyer 9ef066dbb9 Add projects.yaml support 
The projects.yaml lists all of the "official" StarlingX projects
(the ones actually owned by StarlingX and not upstream forks).
It is in YAML format to be machine-readable and useful for a
number of tools.

The first such use is to generate project-specific pages in the
governance documentation listing the projects, tech leads and
project leads. The current content is basically taken from
the existing wiki pages and is lacking in certain areas.
Please review it carefully.

projects.py is based on the OpenStack governance teams.py.

Introduce hacking and switch to flake8 for Python linting,
and fix the pep8 errors in members.py.

Change-Id: I514de8d574df8e60bb488974f2796e2c41010363
Signed-off-by: Dean Troyer <dtroyer@gmail.com>
2018-10-18 14:24:27 -05:00

982 B
Raw Blame History

StarlingX Technical Steering Committee

The StarlingX Technical Steering Committee has oversight over StarlingX technical matters such as project architectural decisions and managing the sub-project life-cycle. It defines the overall project architecture and sets the overall project priorities in collaboration with the community.

Reference Documents

StarlingX has chosen to adopt some of the existing policy and process from OpenStack. Where there is no change from existing OpenStack documentation the links below are directly there.

projects/index

Current Members

Indices and Tables

  • genindex
  • search