Skip to content
Permalink
Browse files

Updated governance details and added members to the TSC (#1578)

Signed-off-by: Travis Addair <taddair@uber.com>
  • Loading branch information
tgaddair committed Dec 9, 2019
1 parent 737830c commit 680716940b397bde59476dbc0fa808d6285ecf4a
Showing with 30 additions and 5 deletions.
  1. +30 −5 CONTRIBUTING.md
@@ -14,15 +14,40 @@ You can find Horovod Charter [here](https://wiki.lfai.foundation/download/attach

### Technical Steering Committee

Horovod development is governed by Horovod Technical Steering Committee (TSC).
Horovod development is governed by the Horovod Technical Steering Committee (TSC). The TSC consists of voting and
non-voting members, in addition to a chairman responsible for running TSC meetings, setting the meeting agenda, and
calling votes on proposals.

Current voting members of the Horovod TSC:
* Alex Sergeev (@alsrgv)
* Travis Addair (@tgaddair)
* Travis Addair (@tgaddair) - Chairman
* Can Karakus (@karakusc)

Horovod TSC publishes meeting notes via [mailing list](https://lists.lfai.foundation/g/horovod-tsc).
This mailing list can also be utilized to reach out to the TSC.
* Josh Romero (@romerojosh)
* Jaliya Ekanayake (@jaliyae)

Current non-voting members of the Horovod TSC:
* Yuxi Hu (@yuxihu)
* Lin Yuan (@apeforest)
* Todd Mytkowicz (@klipto)
* Emad Barsoum (@ebarsoum)
* Kaarthik Sivashanmugam (@skaarthik)

Non-voting members of the TSC ("maintainers") have commit access to the Horovod GitHub repository, and take part in the
standing TSC meetings and mailing lists.

The Horovod TSC meets monthly and publishes meeting notes via a [mailing list](https://lists.lfai.foundation/g/horovod-tsc).
This mailing list can also be utilized to reach out to the TSC. Major decisions regarding the technical directions of
the Horovod project will be brought before the TSC for discussion, with an accompanying proposal document termed an RFC
(Request for Comments).

Technical decisions made by the TSC should be unanimous, with each voting and non-voting member either agreeing to the
proposal or abstaining for it to pass. If consensus cannot be reached, then the proposal is to be put to a vote
among the voting members of the TSC, at which point a majority of the voting TSC must agree to the proposal for it to
pass.

Decisions to add or change members of the TSC in either a voting or non-voting capacity are handled the same as other
proposals (without an RFC): an attempt is made to reach a unanimous decision among the entire TSC, followed by a vote
among the voting members if no consensus can be reached.

### Code of Conduct

0 comments on commit 6807169

Please sign in to comment.
You can’t perform that action at this time.