-
Notifications
You must be signed in to change notification settings - Fork 181
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
Process for porting pattern improvements into Japanese book #448
Comments
@yuhattor would be great to get your thoughts on how to go about this. |
Thank you for summarizing the idea of continuous improvement of the book translation. Well, actually, we do not yet have many community members for InnerSource patterns. I think we need more Japanese contributors for the pattern book. If each change could be divided into small issues, it would be easier for Japanese members to start making contributions. I think this is an opportunity to increase the number of people willing to become TC:) I think I know more about GitHub Actions than most people. And since there are many GitHub employees in the community, they might be able to tell me how to do it better... A quick thought came to my mind: If everyone, including TC, develops using Pull Request and does not push to main, then basically the unit of major changes/updates would be a one Pull Request, and it must be clean. GH Actions look like this
If you have any ideas or information, please le us know @yuichielectric |
@yuhattor this sounds nice. I understand where you are going with that GHA. That way we would automatically create an issue backlog of to-be-translated content. |
That's great! Thank you:) I may need a little verification at my end.I'm thinking of translating innersourcecommons.org in the community right now. Maybe the implementation here can be applied to that as well. But I think innersourcecommons.org has a lot of commits, so we need to make sure it doesn't become noise. |
Yeah, I also think that innersourcecommons.org will require a different approach. Let's solve one challenge at a time ;) |
This has been implemented for a while already. Closing this issue. |
Our fantastic Japanese InnerSource community has translated all current Level 2+ patterns to Japanese. 🇯🇵 🥳
Now what if the original English patterns are improved further?
Common changes are:
Identify to-be-translated content
First we have to identify the changes to the English patterns and book files that have not been translated to Japanese yet. We can do this with a bit more elaborate git log query. Here I am assuming that all changes up to date
2022-07-28
have been translated already:Note: This query does not quite do what I would expect yet but you get the idea I guess :)
Trigger process for translations
We could create a GHA that creates an issue automatically, if new to-be-translated content is identified.
Then the Japanese InnerSource community could review those issues periodically and determine how they want to go about creating the translations for those.
The text was updated successfully, but these errors were encountered: