Replies: 3 comments 1 reply
-
There's been some discussion on Discord about what to do:
A good compromise I think would be to use https://github.com/jcbhmr/setup-typst which currently works and release it as "typst-community/setup-typst@v3". Then, if/when @yusancky is active (last commit 6mo) we can merge the fork back into https://github.com/yusancky/setup-typst and then transfer that repository to @typst-community ? Does that seem like a good idea? |
Beta Was this translation helpful? Give feedback.
-
Nobody represents the organization, but the community involved. You are completely free to conduct the outreach in the name of However, since the organization itself is still in its preliminary stages, i'd refrain till its setup to eliminate confusion that will arise otherwise. |
Beta Was this translation helpful? Give feedback.
-
Completed with @yusancky joining the Typst Community and a new @typst-community/setup-typst team being created. |
Beta Was this translation helpful? Give feedback.
-
I recently opened a Pull Request to revamp the setup-typst action typst-community/setup-typst#12 by @yusancky. That got me thinking: I think that https://github.com/yusancky/setup-typst would be a good project to have under the @typst-community umbrella.
Why this would be a good idea:
typst-community/setup-typst
which looks "official-ish" more than a person's username does lol 😅. That's branding for you haha.Beta Was this translation helpful? Give feedback.
All reactions