-
Notifications
You must be signed in to change notification settings - Fork 534
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
[Proposal] Cloud Native Security White Paper Brazilian Portuguese Translation #509
Comments
Awesome to see this! Glad to pick up this issue as sig-representative. |
Amazing, go for it! Let me know what can I be helpful with :) |
Awesome, let's do this.! .. |
Nice! Let's go boys! |
Thanks to everyone who showed interest. I'll start drafting a document by next week to start off this project and how we'll tackle this and will share with everyone listed here. Please feel free to invite other people that may be interested! Thanks! 😉 |
Yep count on me :)
On Wed 27. Jan 2021 at 19:13 Magno Logan ***@***.***> wrote:
Thanks to everyone who showed interest. I'll start drafting a document by
next week to start off this project and how we'll tackle this and will
share with everyone listed here. Please feel free to invite other people
that may be interested! Thanks! 😉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#509 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7MY7H7MRYEON7HO4VOMVTS4BJTPANCNFSM4WEOXD3Q>
.
--
Typed slowly with one finger on my phone. Please forgive any interesting
auto-corrections or misunderstanding typos.
|
Nicee ! Count on me |
Hi folks, really sorry for delay here, but here's the document I've created so that we can kickstart this project: https://docs.google.com/document/d/1PZfeNRGjvHLWrIpJwHE4q400q0S5Dq5HQQ73YrC7n9k/edit Basically what you have to do is assign a specific topic or paragraph under your name and make the translation as a comment so that we can review it later, makes sense? We can schedule a quick call next week to talk more about this! Thank you! |
Let's go boys!
Obter o Outlook para Android<https://aka.ms/ghei36>
…________________________________
From: Magno Logan <[email protected]>
Sent: Friday, February 26, 2021 9:48:52 PM
To: cncf/sig-security <[email protected]>
Cc: João Victor Cardoso Baptista <[email protected]>; Mention <[email protected]>
Subject: Re: [cncf/sig-security] [Proposal] Cloud Native Security White Paper Brazilian Portuguese Translation (#509)
Hi guys, really sorry for delay here, but here's the document I've created so that we can kickstart this project: https://docs.google.com/document/d/1PZfeNRGjvHLWrIpJwHE4q400q0S5Dq5HQQ73YrC7n9k/edit
Basically what you have to do is assign a specific topic or paragraph under your name and make the translation as a comment so that we can review it later, makes sense? We can schedule a quick call next week to talk more about this! Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#509 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOUEYHGPCM2SNOEQ6CJNJELTBA6PJANCNFSM4WEOXD3Q>.
|
Let’s go guys 🤘🏻
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Magno Logan <[email protected]>
Sent: Friday, February 26, 2021 9:48:52 PM
To: cncf/sig-security <[email protected]>
Cc: Filipi Pires <[email protected]>; Mention <[email protected]>
Subject: Re: [cncf/sig-security] [Proposal] Cloud Native Security White Paper Brazilian Portuguese Translation (#509)
Hi guys, really sorry for delay here, but here's the document I've created so that we can kickstart this project: https://docs.google.com/document/d/1PZfeNRGjvHLWrIpJwHE4q400q0S5Dq5HQQ73YrC7n9k/edit
Basically what you have to do is assign a specific topic or paragraph under your name and make the translation as a comment so that we can review it later, makes sense? We can schedule a quick call next week to talk more about this! Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#509 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHSQDWI325RXVKOZWDT3ZG3TBA6PJANCNFSM4WEOXD3Q>.
|
Let's not use |
Hi @cpanato, thanks for raising this concern. I totally understand your point, and I'm really concerned about being more inclusive. I'm sorry if I offended you or anyone else here, it's just force of habit. But as far as I know, in this specific situation I think that everyone here involved in this project are males or go by the pronouns he/him, please correct me if I'm wrong. Anyways, let's avoid using pronouns altogether to make sure that we are being more inclusive. Thanks for the heads up! =) |
I'd like to contribute @magnologan . By the way I'm she/her. 😉 |
Welcome Carol! Thanks for letting us know your preferred pronouns! That's really helpful! =) Please let us know if you have any questions. |
Awesome! Welcome @krol3 ! @magnologan How is this coming along? Anything the chairs/TLs can do to help? |
Hi @lumjjb, at this time I don't think so. I'll take a look at the doc next week and see how we are doing on the translation piece and start reviewing those so that we can have at least a draft version to announce during KubeCon/CNSD. |
Great!! Count with me!!! |
Joining the team @magnologan! |
Hello all, Some terms don't sound natural in Portuguese, and I don't think people actually use it in Portuguese, like:
I strongly believe there are more... Those were just in the paragraph I've worked on today. |
Hi, @julianocosta89 thanks for sharing and highlighting those terms. We are still deciding on the best approach for the translation so that it could also be used for the pt-PT speakers such as Portugal. After the 1st translation phase is completed we'll review these terms and choose whichever makes more sense for a broader community. |
Hi everyone! Just sharing a bit of a status update here. I've started to review and make the changes on the doc. If you haven't had time to contribute and translate your paragraph please try to do so until next week. Thank you! |
Hi @magnologan , what is the status of this - how far into this are we? |
Hi, @KoelhoSec thanks for all the help and great effort so far! If you could please start reviewing and approving the changes from other people's translations, I'll work on reviewing yours next week. Sounds good? Thank you! |
Sounds good @magnologan ! |
Following up with @KoelhoSec to regroup on this and figure out a schedule. |
Translation is 99% done, just needs review and accepting changes.
|
Hi @KoelhoSec , just checking back on this. How is this going? |
Hi @lumjjb. I am on the final stretch of accepting changes/revision. But I just noticed there were about 5 pages (25-30) that were not translated yet so I will focus on those as well. I believe we should be good to go over to convert to markdown and create the PR over the next 3 weeks, hopefully begining of October. |
Awesome! Looking forward to it. If we get this in by Kubecon we can socialize it during the event! |
@KoelhoSec Home stretch!! I'll check in with you again next week to see if we are ready to share the PR with others for open to comments, and something we can share during Kubecon as well. |
@KoelhoSec how are looking! |
This issue has been automatically marked as inactive because it has not had recent activity. |
@KoelhoSec Hey Bruno, how are things coming along, last time we synced up we were almost there! How are things |
Hi @lumjjb, about two pages left, had a period that had to stop working on it but now I am catching up and will be ready to convert to markup soon 😉 |
@lumjjb here is the markdown file of the translated version. Please take a look and let me know if you need anything else. Cloud Native Security White Paper Brazilian Portuguese Translation.md |
Awesome - can you create a PR with this? I think we would need to just
clean up some of the HTML tags - and make the header more markdown friendly
and we should be good!
…On Thu, Feb 17, 2022 at 5:52 PM Bruno Coelho ***@***.***> wrote:
@lumjjb <https://github.com/lumjjb> here is the markdown file of the
translated version. Please take a look and let me know if you need anything
else.
Cloud Native Security White Paper Brazilian Portuguese Translation.md
<https://github.com/cncf/tag-security/files/8092741/Cloud.Native.Security.White.Paper.Brazilian.Portuguese.Translation.md>
—
Reply to this email directly, view it on GitHub
<#509 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXLDBSONIOEAGETVFPH2V3U3V33FANCNFSM4WEOXD3Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thank you @KoelhoSec for working on this!! Btw, v2 of the paper will be published around May 2022. We are tracking it here #747 in case you are curious |
This issue has been automatically marked as inactive because it has not had recent activity. |
Closed up with #908 |
Description: Similar to #470 I'd like to start the translation of the Cloud Native Security White Paper to Brazilian Portuguese (pt-BR)
Impact: This would help the Portuguese-speaking community with the understanding and adoption of best practices for Cloud Native Security. This would also help the promotion of the white paper inside governmental organizations where only Portuguese documents are allowed.
Scope: Cloud Native Security White Paper (44 pages)
Duration: 3-5 weeks
I'd like to invite some Portuguese speaking professionals that I'm aware that are part of the Security and/or CNCF Community as well if they are interested:
@cpanato
@filipi86
@rikatz
@bizarrenull
@imfvieira
@SatanicDrNull
@damelo
@cardosoJV
@P0ssuidao
If anyone else is also interested feel free to leave your name/contact info on this issue. Thanks!
The text was updated successfully, but these errors were encountered: