Please note that we are unaffiliated with the official Typst team, this is a separate organization.
Hey everyone,
With the ecosystem around community maintained tools, packages, plugins, and templates continuously growing, we’re looking to consolidate efforts and shape the ecosystem at an early age. We want to ensure a coherent experience for people using community maintained tools and packages. For this reason, we’ve created the rfcs repository, a place at which we want to propose standards that community tools should uphold/support. We want RFCs to go through an open process where everyone can review them and voice their opinion and concerns. To ensure that RFCs are reviewed by stakeholders, we want to have a community-elected team (currently called @typst-community/ecosystem) that has the expertise to decide whether an RFC should be accepted, postponed, or rejected.
This is where this post comes in, we’re looking for nominations for this team.
We’re asking you to nominate either yourself or somebody else who you think would be a good fit.
RFCs
- What are RFCs?
An RFC (request for comments), in the context of typst-community, is a public discussion of a proposed standard which can be brought forth by anyone. The discussion is open to everyone to review and propose changes to the standard itself. A prime example for this is the standardization of the doc comment syntax used by packages and the language servers, which has previously arisen naturally. - What kind of RFCs are we expecting?
A few have been gathered on rfcs#4, while these are mostly scripting related at the moment, they need not be. Though we mostly expect RFCs to propose standards for community tools, and as such, we expect them to mostly be about package development. - What will the process for an RFC be like?
The exact RFC process is not yet fixed in place, it will be the first decision of the new ecosystem team to do that. But we want it to be a process that is open to anyone. You can see the current RFC process draft on rfcs#3. Feel free to review it and add your thoughts, regardless if you’re nominating or not!
Nomination Requirements
- Nominees should be regularly active and genuinely involved somewhere in the Typst community, ideally in the package development ecosystem. This could mean being active on the forums, Discord, or anywhere else Typst folks gather. Stuff like answering questions, maintaining projects, translating, or helping out in other ways all counts.
- Nominees should be able to communicate their thoughts. This may sound trivial, but when a team member blocks an RFC, they should be able to explain why they think the RFC is unfit for inclusion in the repository. This is where familiarity with package development really counts!
- Nominees must follow the Code of Conduct for both our community and the Typst Discord.
Election Process
- Nominations need not be self-nominations, if you think someone meets the requirements and would be a good fit for the team, feel free to nominate them. If someone is nominated by someone else, then they must explicitly accept the nomination on this post for it to be counted
- This thread will be open for 4 weeks from today (2025-08-10T22:00:00Z) through 2025-09-07T22:00:00Z.
- After 4 weeks, the top 9 nominees with the most total reactions (upvotes - downvotes) on their nomination are elected.
- If the latter places are tied, we’ll hold a runoff vote for those tied candidates.
- Feel free to ask nominees questions under their post if you want to know more about them or what they do around the community.
Responsibilities
- Members adhere to the RFC process once it was voted on by the team.
- Members regularly vote on whether an RFC should be merged, postponed or rejected.
- Members review RFCs before their FCP (final comment period).
- Members present readiness to implement RFCs if they maintain projects affected by them.
If you have any other questions or want to chat privately, you can reach out by email at admin@typst.community, post on the Discussion Board, or find us on the official Typst Discord in CONTRIBUTORS > 
forge > Community.
If you’re interested, go ahead and nominate yourself or someone else on the GitHub discussion thread.
Note that the current team has previously held a smaller pre-nomination Q&A where we gathered potential candidates for the team based on their community efforts. These candidates are marked below with a small pre-nominated disclaimer, but are treated no different from other nominees. The vote was done to see how large the ecosystem team may become and if it should have subteams.
To all pre-nominees, you can add additional information in an extra comment under your post if you wish.