docs(i18n): defer README template-driven generation, capture #195 discussion#403
Open
laihenyi wants to merge 1 commit intonexu-io:mainfrom
Open
docs(i18n): defer README template-driven generation, capture #195 discussion#403laihenyi wants to merge 1 commit intonexu-io:mainfrom
laihenyi wants to merge 1 commit intonexu-io:mainfrom
Conversation
discussion Add NRG / template-driven README generation to TRANSLATIONS.md "Deferred decisions" with explicit re-evaluation triggers (≥15 locales or monthly+ README structural edits) and a record of the shared-structure trade-off that surfaced in nexu-io#195. Captures the rationale (zh-TW's "上手體驗" section, pt-BR vs pt-PT content-level divergence precedent) so future contributors don't relitigate it from scratch.
Contributor
mrcfps
approved these changes
May 4, 2026
Contributor
mrcfps
left a comment
There was a problem hiding this comment.
@laihenyi I reviewed the TRANSLATIONS.md deferred-decision update and verified the new README template-generation guidance is scoped to the changed documentation, keeps the existing deferred-decisions structure, and records clear revisit triggers plus the locale-variation trade-off. This is a tidy follow-up that should make future i18n tooling discussions easier to pick up without forcing premature process changes. Thanks for capturing the rationale so clearly. 🙌
Generated by Looper 0.0.0-dev · runner=reviewer · agent=opencode
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
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.
Follow-up to #196 / discussion in #195. After PR #196 landed, @andriishin pointed out NRG (single
.src.mdtemplate → multi-localeREADME.<lang>.md) as a fix for the atomic-update brittleness called out in TRANSLATIONS.md step 7. @lefarcen analyzed the fit and we agreed the right move is document-and-defer rather than fold tooling into the docs RFC.This PR captures that decision in
TRANSLATIONS.mdso future contributors don't relitigate it from scratch.What changes
A single bullet under Deferred decisions — parallel in shape to the existing Translation memory tooling entry:
.src.mdscripts, All Contributors-style) so we don't lock into one tool prematurely.README.zh-TW.md's "上手體驗" section, the pt-BR / pt-PT content-level precedent).Why "Deferred" not "Open question"
The existing Open questions section is for genuinely undecided items. NRG-class tooling has been actively discussed in #195 and the team agreed to defer with explicit triggers — that's the same shape as the TM-tooling entry already living under Deferred decisions.
Out of scope
A separate tracking issue ("Evaluate template-driven README generation") will collect NRG + alternatives and link back here. That's a separate, smaller change that doesn't need to ride with this docs update.
Test plan
TRANSLATIONS.mdon GitHub; confirm the new bullet renders alongside the TM-tooling bullet under Deferred decisions.