{"id":28544064,"url":"https://github.com/moby/tsc","last_synced_at":"2026-01-30T18:31:35.187Z","repository":{"id":65977901,"uuid":"104799657","full_name":"moby/tsc","owner":"moby","description":"Moby Technical Steering Committee","archived":false,"fork":false,"pushed_at":"2020-01-01T09:36:05.000Z","size":22,"stargazers_count":24,"open_issues_count":2,"forks_count":24,"subscribers_count":18,"default_branch":"master","last_synced_at":"2025-07-06T18:43:02.345Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/moby.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2017-09-25T20:38:16.000Z","updated_at":"2024-12-12T18:36:56.000Z","dependencies_parsed_at":"2023-02-19T18:50:33.832Z","dependency_job_id":null,"html_url":"https://github.com/moby/tsc","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/moby/tsc","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/moby%2Ftsc","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/moby%2Ftsc/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/moby%2Ftsc/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/moby%2Ftsc/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/moby","download_url":"https://codeload.github.com/moby/tsc/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/moby%2Ftsc/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28917040,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-30T16:37:38.804Z","status":"ssl_error","status_checked_at":"2026-01-30T16:37:37.878Z","response_time":66,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-06-09T22:06:40.970Z","updated_at":"2026-01-30T18:31:35.179Z","avatar_url":"https://github.com/moby.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Technical Steering Committee\n\nA Technical Steering Committee(TSC) for multiple projects serves as a replacement for the current BDFL that oversees a few of the projects that exist today.\nThese changes should have a minimal impact to the day-to-day operations and governance model in order to make a transition smooth and timely.\n\nThis proposal provides enough initial structure to elect the committee and hand off responsibilities to this group of diverse individuals.\n\n**Edits to this charter requires that the projects the TSC oversees vote with a simple majority on all changes.**\n\nSmall edits to this charter such as typos and formatting can be approved by the TSC members.\n\n## Committee Information\n\nThe Technical Steering Committee acts as an escalation point for conflicts within projects, encourage cross-project communication/coordination and help with project governance.\nThe TSC is not involved in the day-to-day development or maintenance of the projects it represents, though, individuals on the committee may be maintainers and/or contributors to the projects.\nThe committee does not make day-to-day technical decisions on architecture, code acceptance, or feature set but can resolve technical disputes in these areas when an issue has been escalated to the TSC by the community of the project.\nHowever, escalation should be considered a failure of the community process when unable to reach concensus on an issue.\n\n### Responsibilities\n\nThe committee should:\n\n1. Serve as an escalation point for members of the community to file a dispute or report concerns on technical issues.\n2. Ensure that appropriate communication exists between projects.\n3. Keep a public record of escalations, actions, and decisions.\n\n*If non-technical issues are escalated to the TSC, the TSC should route the issue to the appropriate destination for the affected project.  i.e. Code of Conduct issues to CNCF or Docker CoC boards.*\n\n### Seat Term\n\n**2 years**\n\nMembers do not have a set term limit, the seat they hold has a term limit.\nMembers are rotated organically as seats expire and members are either re-elected or replaced.\n\nEvery two years the seats expire and a new election process begins.\nMembers are able to re-run for election as long as they qualify for the **Candidate Requirements**.\n\n### Committee Size\n\n**7 seats**\n\nA single company cannot hold more than 1/3 (one-third) of the seats on the committee.\n\n### Elections\n\nMembers of the TSC will be voted in by the maintainers of the projects that it represents.\nEach project receives one vote in the election.\nThe departing BDFL, Solomon Hykes, will receive one vote in every election.\n\nThe top 7 candidates will comprise the TSC.\nElections will be handled via http://civs.cs.cornell.edu/ using ranked voting.\nEach project will receive one vote that the maintainers of the project must decide on.\nThis ensures projects with a large number of maintainers will not be able to influence the voting more than smaller projects.\nIt is up to the projects to determine how they want to rank their votes in an election.\nA suggested method for projects is to use the same ranked voting with their maintainers to cast their vote.\n\n*Why ranked voting?: “Ranked-choice voting gives more accurate results because it collects more information from voters. It also helps avoid vote splitting and spoilers.”*\n\n#### Candidate Requirements\n\n1. Anyone is eligible.\n2. Must be sponsored by a maintainer of a TSC represented project.\n3. Maintainers cannot sponsor themselves.\n\n## TSC Mailing List\n\ntsc@mobyproject.org\n\n## TSC Represented Projects\n\n* [InfraKit](https://github.com/docker/infrakit)\n* [LinuxKit](https://github.com/linuxkit/linuxkit)\n* [Moby](https://github.com/moby/moby)\n* [SwarmKit](https://github.com/docker/swarmkit)\n* [libnetwork](https://github.com/docker/libnetwork)\n* [notary](https://github.com/docker/notary)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmoby%2Ftsc","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmoby%2Ftsc","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmoby%2Ftsc/lists"}