-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Translate the Platform White Paper into Japanese #694
Conversation
Signed-off-by: Nao Nishijima <[email protected]>
✅ Deploy Preview for tag-app-delivery ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@hhiroshell @Okabe-Junya @kaitoii11 |
Please wait a bit longer; I'll continue the review starting tomorrow. |
Signed-off-by: Nao Nishijima <[email protected]>
I don't have enough time to review this PR right away. I'm sorry, but could you please ask hhiroshell and kaitoii11 ? (I think two approvals should be enough for the localization review.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed until プラットフォームチームの特性。
|
||
デリバリーチームを本来のコア業務に集中させ、組織全体の重複作業を減らしたいという要望から、企業をクラウドネイティブコンピューティング向けのプラットフォームを導入するようになりました。プラットフォームに投資することで、企業は次のことが可能になります: | ||
|
||
1. プロダクトチームの認知負荷を軽減し、製品開発とデリバリーを加速します。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. プロダクトチームの認知負荷を軽減し、製品開発とデリバリーを加速します。 | |
1. プロダクトチームの認知負荷を軽減し、プロダクト開発とデリバリーを加速します。 |
Since the product team is "プロダクトチーム", it would make sense to translate product develop as "プロダクト開発"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed. I thought it would be better to unify one or the other, so "product team/developers/teams/owner" became "プロダクトXX". But the word "product" occurs in many places. Should we "puroduct" to be "プロダクト" rather than "製品"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Understood. If there is consistency throughout the text we should leave it as is.
|
||
クラウドネイティブコンピューティングのためのプラットフォームとは、プラットフォームの利用者のニーズに合わせて定義、提供された能力の集合体です。これは、幅広いアプリケーションやユースケースに対して、一般的な能力やサービスの取得と統合を一貫したエクスペリエンスで保証する横断的なレイヤーです。優れたプラットフォームは、ウェブポータル、プロジェクトテンプレート、セルフサービスAPIなど、その能力やサービスの利用と管理において、一貫したユーザーエクスペリエンスを提供します。 | ||
|
||
Atlassianによると[[1]]、「プラットフォームチームは、少しのオーバーヘッドで多数のストリームに沿った[プロダクト]チームが利用できる能力を作成します... プラットフォームチームは、ストリームアラインプロダクトチームのリソースと認知負荷を最小化します... プラットフォームチームは、異なるユーザーエクスペリエンスや製品にまたがる一貫した体験を構築できます。」 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The term "stream-aligned team" should be aligned with the translation of the original book Team Topolgy. So ideal we should leave it as "stream-aligned team" or ストリームアラインドチーム。
For reference, here is a slide from the Japanese translator. https://speakerdeck.com/miholovesq/team-topologies-with-platform-engineering?slide=21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for information! I translated the term of "stream-aligned [product] teams" to "ストリームアラインド[プロダクト]チーム". Just add "ド" after "アライン".
Signed-off-by: Nao Nishijima <[email protected]>
Thank you for review! I deal with it and left comments. |
@naonishijima (This issue will be fixed by #687) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyway, the translation is quite fine to me. Thanks for your work!
Does this PR have enough approvals to move forward? If not, I think @kaitoii11 needs to check it again, thank you :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM from the technical side
I think good to go with one native speaking reviewer and one tech reviewer. Just need a tag rep to verify and merge! Cc/@lianmakesthings @thschue @angellk @roberthstrand |
This PR translates the Platform White Paper into Japanese.