[Project] Cloud Native Security White Paper Japanese translation - v2

[naonishijima]

Description: I would like to start translating the Cloud Native Security white paper v2 into Japanese.

Impact: This would help the Japanese-speaking community understand and adopt best practices for cloud native security.

Scope: Cloud Native Security White Paper v2

Project leader: @naonishijima
Project Schedule: 3w-5w

This translation will be done with the assistance of some members of the Japanese CNCF Glossary community.
If anyone else is interested, please feel free to leave your name/contact details in this thread. Thank you very much!

[yuichi-nakamura]

I can help something. My name is Yuichi Nakamura (@yuichi-nakamura).

[PushkarJ]

Happy to be a TAG sponsor for this proposal 🎉

[anvega]

Hello @naonishijima and @yuichi-nakamura -- Thanks for taking the initiative.

As stated by @PushkarJ already, we'd be thrilled to support you in translating the paper.

Please let us know if you have been able to get started. Should you require assistance coordinating additional help from other contributors or resources you may need, don't hesitate to reach out indicating so.

It would also help us with a status update of where you are in the process if you can include an expected completion timeline.

どうもありがとうございます

[naonishijima]

Hi @anvega,
I started to translate last week, just finished 30% of the translation.
I will have a colleague review it within the next week, and as soon as that is done, I will send PR and ask CNCF Glossary Japanese community to review it.

[anvega]

Amazing @naonishijima. Thanks for the update.

[anvega]

Thank you for your hard work. The translated Japanese Cloud Native Security White Paper is now merged.

If you can write one or two paragraphs to announce the blog, we can work with CNCF communications team to announce the publication in the cncf blog. Same as with generating a pdf for the translation.

[naonishijima]

@anvega Thank you for marge!

Yes. I would like to write one or two paragraphs.
When should I write it by? and Where should I write?

[anvega]

Great. The production team typically takes about one to two weeks for a turnaround with the pdf version but sometimes sooner. My recommendation is to aim for 10 days. You can paste the text in a comment on this issue here.

[naonishijima]

@anvega
This is a comment for announcement. We are happy if it is in line with your assumptions. You do not have to adopt this text, and you can modify it if you find something wrong.

"Cloud Native Security White Paper Japanese translation is now available. The language barrier still separates Japan from the world despite its large number of developers. Localization removes that barrier, and now you can learn about global best practices for cloud-native security. It is recommended that users who are considering adopting cloud-native systems use this paper to understand the security challenges and solutions involved."

[PushkarJ]

@naonishijima sorry for the delayed response. CNCF suggested to convert the markdown whitepaper to a google document if possible for publishing as CNCF designed pdf. Is that something you would be able to do for us and then share a link? Note the google document should be identical in content with markdown merged paper.

You may use markdown to docx converter to do the same. Let us know if you need help!

[naonishijima]

@PushkarJ Sure. I converted the markdown whitepaper to a google document by Pandoc.
This is the link:
https://docs.google.com/document/d/1-CTg-_tW1dnZzG8pMHTvc0MnzQkMpwMk8-2cpQLNTRU/edit?usp=sharing

I have a question. The document is not converted properly and the annotations are blank. I have also converted English documents with pandoc, but the same problem occurs. Are there any steps I should take?

[PushkarJ]

@naonishijima I honestly have no idea how to help with annotations issue. Would blank annotations severely impact the translation quality? If yes, maybe we will have to cancel the PDF conversion. I will try to see if we can publish a blog though regardless. Let me know what you think.

[naonishijima]

@PushkarJ The annotation issue is not critical and does not affect the quality of the translation. Therefore, continuing to convert to PDF format will not be a problem.

[caniszczyk]

@PushkarJ any idea what the blocker here is?

I think we should always ensure that the source of truth is the .md file

[PushkarJ]

Markdown version is already merged. We were mainly discussing how to publish a PDF version of this. CNCF design team has always asked for google docs link for designing the PDF.

Since google docs is in sync with markdown here: #1098 we can publish this. I will be requesting CNCF service desk assignee to generate a pdf for this.

[PushkarJ]

@ashutosh-narkar will be helping with the rest of the process until publication!

[ashutosh-narkar]

I've opened a CNCF Service Desk ticket to get the doc converted and published. I'll keep y'all posted about updates from the CNCF. Thanks.

[mnm678]

@ashutosh-narkar any updates on the Service Desk ticket?

[ashutosh-narkar]

Not yet. I have asked for an update. Once I hear back, I'll post here.

[eddie-knight]

I've bumped the service desk request for this.

cc/ @riaankleinhans CNCFSD-2517

[riaankleinhans]

@naonishijima Have the work been completed? It the document available to publish?

[naonishijima]

@riaankleinhans Yes. The work has been completed and can be published.

[riaankleinhans]

Is the document published through this PR?
Then I assume this issue can be closed?

[naonishijima]

@riaankleinhans
The PR has been merged, but a PDF version still needs to be created.
https://github.com/cncf/tag-security/tree/main/community/resources/security-whitepaper/v2