Skip to content

Latest commit

 

History

History
107 lines (77 loc) · 4.18 KB

GOVERNANCE.md

File metadata and controls

107 lines (77 loc) · 4.18 KB
Raw

Governance of the Spack project

All information in this file is pursuant to the Spack Technical Charter. In case of any conflict or difference in language, the Spack Technical Charter takes priority over this document.

Technical Steering Committee

Role

The role of the Technical Steering Committee (TSC) is to provide technical direction to the project. The TSC will vote on any matters on which the community is unable to reach consensus.

Membership

Members can be added to the TSC by a majority vote of the TSC. Members may be removed from the TSC by a 2/3 vote of the TSC. If a TSC member has been inactive for over 6 months, the TSC must hold a vote on whether to remove that member from the TSC.

Current Membership:

  1. Todd Gamblin (@tgamblin), LLNL
  2. Greg Becker (@becker33), LLNL
  3. Peter Scheibel (@scheibelp), LLNL
  4. Tamara Dahlgren (@tldahlgren), LLNL
  5. Massimiliano Culpo (@alalazo), np-complete, S.r.l
  6. Harmen Stoppels (@haampie), Stoppels Consulting
  7. Phil Sakievich (@psakievich), SNL
  8. Adam Stewart (@adamjstewart), TU Munich
  9. Wouter Deconinck (@wdconinc), U. Manitoba
  10. John Parent (@johnwparent), Kitware
  11. Ryan Krattiger (@kwryankrattiger), Kitware
  12. Luke Peyralans (@eugeneswalker), U. Oregon
  13. Marc Paterno (@marcpaterno), Fermilab
  14. Mark Krentel (@mwkrentel), Rice University

TSC Chair

The TSC will elect a chair. The TSC chair runs TSC meetings and may make interim decisions on urgent matters on behalf of the TSC, which may be reviewed by the TSC at its next meeting.

Current chair:

Meetings and Notes

The TSC meets at 9am Pacific Time on the first Wednesday of every month. These meetings are open to the public, and are held virtually.

Meeting notes can be found in tsc-meeting-notes in this repository.

Other Public Spack fora

Weekly Meetings

Public Spack community meetings are held every Wednesday that is not a TSC meeting, at 9am Pacific Time. These meetings are held virtually over webex.

Spack slack

The Spack project uses slack for day-to-day communication. Invitations to the Spack slack instance are publically available from slack.spack.io.

Spack Github

Spack issues, pull requests, and long term discussions are tracked on the Spack GitHub page. Upcoming high-impact changes have their own pinned discussion.

Announcements

The Spack mailing list is an announcements-only list. Spack also has a twitter account [@spackpm](https://github.com/spackpm).

Teams in the Spack organization

Administrative Access to the Github Repository

Only members of the TSC may have administrative access to the Spack repository. TSC members will be given access as needed. This list is not generally published for operational security reasons.

Other teams within the Spack organization

There are other teams within the Spack github organization which control access to various permissions on the repository. These teams are:

  • tsc: see above
  • spack-releasers: can create a new release of Spack
  • merge-to-develop: can merge an approved pull request to Spack
  • triage: can triage pull requests and issues in the Spack repository
  • maintainers: any user registered to be the maintainer for a package in Spack

See the relevant teams in the Spack github repository for membership of these teams. Membership in these teams is controlled by the TSC.