repo: Add RFC process document #3
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tingerrr
force-pushed
the
tinger/rztqymutxyps
branch
2 times, most recently
from
41833e2 to
a039f98
Compare
This process is adapted from the Rust RFC process on rust-lang/rfcs and is intentionally less formal than that of Rust as the Typst community is still much smaller and the RFCs are less official than those of Rust. The formality may change in the future and the repository may be incorporated into the typst organization itself. But until then, this process can stay simple and somewhat informal.
tingerrr
force-pushed
the
tinger/rztqymutxyps
branch
from
a039f98 to
241a125
Compare
SillyFreak
reviewed
Jul 4, 2025
tingerrr
force-pushed
the
tinger/rztqymutxyps
branch
from
004aec2 to
38da57a
Compare
tingerrr
force-pushed
the
tinger/rztqymutxyps
branch
from
ac676f1 to
d740c50
Compare
|
I've put this up for review, but I'd like to discuss the current state of the ecosystem team on the forge before this is merged to ensure we have a representative portion of the community for the final vote of the RFC (as the process stands for now at least). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See commit description.
Please make sure to read the source code directly, as some parts of the original text have not yet been altered, these usually have comments which aren't visible in the rendered version.
Two parts in particular stand out:
The Rust process requires consensus by all members of a subteam, since we may not have subteams (see community forge discussion) this would have to be revised.After the review I've changed this to be a sizable majority of the ecosystem team for now.
RFCs need some kind of advertisement when they go into FCP, Rust for example uses the "This Week in Rust" newsletter. See the comment for ideas.I went with the forum as an example here, this need not be just that, it merely serves as an example.
I've also left out the explanation about postponing and informality because they didn't seem to add much and the doc is already long enough. I think we can still simplify a lot of the wording here to make it more approachable.