This repository houses the documents and discussions of the Typelevel Technical Steering Committee. The committee is responsible for:
- Advising the Typlevel board on overall technical priorities for the Foundation, especially the designation and stewardship of Organization Projects; and
- Curating the portfolio of Typelevel Affiliate Projects, including soliciting and reviewing applications.
Typelevel is a collaborative organization of volunteers. If you are working with Typelevel projects and want to share your thoughts on the foundation's technical priorities, feel free to open a ticket!
We are currently reviewing the affiliate process, but if you are interested in your project becoming part of Typelevel, feel free to open a Project Submission ticket and we will get back to you once the process is updated.
The Typelevel ecosystem covers a wide range of domains including functional programming, high performance microservices, generic programming, tooling, and more. Projects that work well with or align with the goals of existing projects are invited to consider joining Typelevel.
There are two ways a project can join Typelevel, as an organization project or as an affiliate project. Both of these membership types are described in the projects page.
The main difference is that organization projects are hosted by Typelevel (at github.com/typelevel) and agree to follow the guidance and direction of the Typelevel board.
Organization Projects:
- listed on Typelevel website
- hosted by Typelevel
- are typically published under the org.typelevel group id
- receive build and maintenance help from the Typelevel team
- get updated by typelevel steward
- tend to use sbt-typelevel
Affiliate Projects:
- listed on Typelevel website
- demonstrate alignment with other Typelevel projects
- use original release coordinates
- can be withdrawn at any time by the author(s)
The Typelevel Technical Steering Committee should bias towards action and embody the idea of the advice process: any person can make any decision after seeking advice from those who will be meaningfully affected and people with expertise in the matter. More can be read about the advice process at reinventingorganizationswiki: decision-making.
In short:
- Someone notices a problem or opportunity and takes the initiative, or alerts someone better placed to do so.
- Prior to a proposal, the decision-maker may seek input to sound out perspectives before proposing action.
- The initiator makes a proposal and seeks advice from those affected or those with expertise.
- Taking this advice into account, the decision-maker decides on an action and informs those who have given advice.
The Technical Steering Committee can view the board as a safety net in its decision making: the TSC is empowered to take action on their own and the board provides oversight.
- We are pleased to offer Typelevel contributors access to a license for Tuple, pair programming software. Please read our guide for how to set it up.
All governance docs are licensed under Creative Commons Attribution 4.0 International (CC-BY-4.0).