Call for Nominations: Ecosystem Team

[tingerrr]

👋 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-11) through 2025-09-08.
• 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 [email protected], 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 below!

---

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.

[tingerrr]

The current team would like to nominate @Enter-tainer for their outstanding work maintaining tools such as mitex, typstyle, typst.ts and tinymist.

---

This was part of the pre-nomination.

[tingerrr]

The current team would like to nominate @Mc-Zen for their outstanding work maintaining tools such as lilaq, tidy and zero.

---

This was part of the pre-nomination.

[Mc-Zen]

To take a bit of the anonymity away, I would also like to add some introduction about me and my work in the Typst community.

I'm not much involved with the Typst compiler itself, but the more with packages − being the author and maintainer of five of the around 40 featured packages on the Typst Universe: Lilaq, Quill, Zero, Tidy, and Tiptoe (and a few extra ones).

Thus, I have great deal of experience with writing Typst packages; I am known for meticulous package documentation and care for interfaces that adhere to the design and principles of the Typst language and its standard library. I have a strong vision for Typst packages that interoperate well, are compatible with each other, and have a consistent interface.

Moreover, I'm quite active in the community: I regularly post issues to the Typst repository, answer questions in the forum and read a great deal of what is happening.

My background is in physics (more precisely quantum information theory) where I draw a lot of inspiration from when working on new ways to design useful packages.

[tingerrr]

The current team would like to nominate @Myriad-Dreamin for their outstanding work maintaining tools such as mitex, shiroa, tinymist and typst.ts.

---

This was part of the pre-nomination.

[tingerrr]

The current team would like to nominate @OrangeX4 for their outstanding work maintaining tools such as mitex, pinit, and touying, as well as their work on the unofficial Chinese translation of the Typst documentation.

---

This was part of the pre-nomination.

[tingerrr]

The current team would like to nominate @OverflowCat for their outstanding work maintaining tools such as astro-typst.

---

This was part of the pre-nomination.

[tingerrr]

The current team would like to nominate @PgBiel for their outstanding work maintaining tools such as elembic, oxifmt, tablex and typst itself.

---

This was part of the pre-nomination.

[tingerrr]

The current team would like to nominate @SillyFreak for their outstanding work maintaining tools such as prequery and typst-package-template.

---

This was part of the pre-nomination.

[SillyFreak]

I would like to add a few words here so that others know who they would be voting for :)

I've been using Typst for a bit over two years, must have started in the first half of 2023. I was intrigued by the same reasons that we see mentioned a lot on Discord, and since Typst started supporting packages I've authored quite a few: 11 public ones and a few extra private or unpublished ones. The most notable one is probably Alexandria, although Prequery may be a bit more relevant here, since it basically shows a blueprint for how tools can/could interact with document metadata in a structured way.

Since I have quite a few packages, I care about the ergonomics of writing them, and have become a maintainer of the community's package template.

I consider myself fairly knowledgeable about how Typst works (at least the language; not so much the internals of the compiler), and like to think I can convey that information well. I do that on the forum and Discord, and think this would also be valuable for RFC discussions (I would of course make use of that whether I'm elected or not).

I'm also fairly active in the community in general, so I think that's also a plus :)

[tingerrr]

The current team would like to nominate @Thumuss for their outstanding work maintaining tools such as utpm and truthfy.

---

This was part of the pre-nomination.

[tingerrr]

The current team would like to nominate @tingerrr for their outstanding work maintaining tools such as hydra, subpar and tytanic.

---

This was part of the pre-nomination.

[tingerrr]

The current team would like to nominate @fenjalien for their outstanding work maintaining tools such as cetz.

---

This was part of the pre-nomination.

[tingerrr]

The current team would like to nominate @johannes-wolf for their outstanding work maintaining tools such as cetz.

---

This was part of the pre-nomination.

[tingerrr]

The current team would like to nominate @sjfhsjfh for their outstanding work maintaining tools such as typship.

---

This was part of the pre-nomination.

[tingerrr]

I would like to personally nominate @YDX-2147483647 for their outstanding work on both the official English and unofficial Chinese translation of the Typst documentation, as well as their community work on typst-jp.

[YDX-2147483647]

If someone is nominated by someone else, then they must explicitly accept the nomination on this post for it to be counted

Thank you! I accept the nomination, but it should be noted that I am NOT the one who has contributed the most, the earliest or the longest in the en/zh/ja docs. I'm just active because I'm on a tiny vacation recently, and might not response quickly in the future.

• The main work of the Chinese translation was done by Myriad-Dreamin and OrangeX4 (both are nominated above), and later contributors can be found in https://github.com/typst-doc-cn/guide/graphs/contributors. I actually joined very late.

• Japanese people have been working constantly in https://github.com/typst-jp/typst-jp.github.io for months. They have a rigorous review process: Nearly every PR has been approved by at least two people. My contribution was to fix several bugs of the website generator.

[baptiste]

I would like to nominate @SabrinaJewson for creating cmarker, hayagen (and probably other tools I don't know about), and also because her contributions to the forum always enrich the discussion, from what I've seen.

[tingerrr]

Thank you for everyone who participated, the vote is now finished, and we'll announce the standings and decision soon.