Skip to content
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

Adição tradução PT_BR #211

Merged
merged 1 commit into from
May 26, 2023
Merged

Adição tradução PT_BR #211

merged 1 commit into from
May 26, 2023

Conversation

itsfks
Copy link
Contributor

@itsfks itsfks commented May 25, 2023

No description provided.

@Frooodle Frooodle merged commit 4cadfc6 into Stirling-Tools:main May 26, 2023
2 checks passed
@Frooodle
Copy link
Member

Frooodle commented Oct 8, 2023

Hi itsfks,

We are updating Stirling-PDF's license to MPL 2.0 (Mozilla Public License Version 2.0) to continue fostering our open-source commitment while introducing more flexible usage of the project.

What We Need From You:

In order to transition to the MPL 2.0 license, we need the explicit consent of all our contributors.

  1. If you're comfortable relicensing your contributions for this specific PR under MPL 2.0, please respond with:
    I, itsfks, grant permission to relicense my contributions from this PR to Stirling-PDF under the Mozilla Public License 2.0.
  2. If you'd prefer to give blanket permission for all of your contributions to Stirling-PDF (be it through pull requests, commits, or any other form of contribution) rather than on a PR-by-PR basis, please respond with:
    I, itsfks, grant permission to relicense all my contributions to Stirling-PDF under the Mozilla Public License 2.0.

What does this do and why?

As your old code was contributed under a different license it legally cannot move to a new license without your permission, and since we dont want to lose your code we wanted to reach out. Remember this project is remaining open-source!.

Deadline:

If we dont receive a response, or if you decline, unfortunately, we will have to remove your contributions from Stirling-PDF before the license change, which is scheduled in coming months.

Thank You!

Your contributions are invaluable, and we hope to continue having them in Stirling-PDF under the new license. Feel free to ask if you have any questions or concerns about this change.

Best,
Frooodle
Stirling-PDF Maintainer

1 similar comment
@Frooodle
Copy link
Member

Frooodle commented Oct 8, 2023

Hi itsfks,

We are updating Stirling-PDF's license to MPL 2.0 (Mozilla Public License Version 2.0) to continue fostering our open-source commitment while introducing more flexible usage of the project.

What We Need From You:

In order to transition to the MPL 2.0 license, we need the explicit consent of all our contributors.

  1. If you're comfortable relicensing your contributions for this specific PR under MPL 2.0, please respond with:
    I, itsfks, grant permission to relicense my contributions from this PR to Stirling-PDF under the Mozilla Public License 2.0.
  2. If you'd prefer to give blanket permission for all of your contributions to Stirling-PDF (be it through pull requests, commits, or any other form of contribution) rather than on a PR-by-PR basis, please respond with:
    I, itsfks, grant permission to relicense all my contributions to Stirling-PDF under the Mozilla Public License 2.0.

What does this do and why?

As your old code was contributed under a different license it legally cannot move to a new license without your permission, and since we dont want to lose your code we wanted to reach out. Remember this project is remaining open-source!.

Deadline:

If we dont receive a response, or if you decline, unfortunately, we will have to remove your contributions from Stirling-PDF before the license change, which is scheduled in coming months.

Thank You!

Your contributions are invaluable, and we hope to continue having them in Stirling-PDF under the new license. Feel free to ask if you have any questions or concerns about this change.

Best,
Frooodle
Stirling-PDF Maintainer

@Frooodle
Copy link
Member

@itsfks any reply otherwise your commit will be removed!

@Frooodle
Copy link
Member

@itsfks ?

@Frooodle
Copy link
Member

@itsfks Final ask! please reply if you can!
Por favor, responda se puder! é extremamente necessário!

@Frooodle
Copy link
Member

Muito mal o Google Tradutor..

Olá, obrigado,

Estamos atualizando a licença do Stirling-PDF para MPL 2.0 (Mozilla Public License Versão 2.0) para continuar a promover nosso compromisso com o código aberto e, ao mesmo tempo, introduzir um uso mais flexível do projeto.

O que precisamos de você:
Para fazer a transição para a licença MPL 2.0, precisamos do consentimento explícito de todos os nossos colaboradores.

Se você se sentir confortável em licenciar novamente suas contribuições para este PR específico sob MPL 2.0, responda com:
Eu, itsfks, concedo permissão para licenciar novamente minhas contribuições deste PR para Stirling-PDF sob a Licença Pública Mozilla 2.0.
Se você preferir dar permissão geral para todas as suas contribuições ao Stirling-PDF (seja por meio de pull requests, commits ou qualquer outra forma de contribuição) em vez de PR por PR, responda com:
Eu, itsfks, concedo permissão para licenciar novamente todas as minhas contribuições para Stirling-PDF sob a Licença Pública Mozilla 2.0.
O que isso faz e por quê?
Como seu código antigo foi contribuído sob uma licença diferente, legalmente não pode ser movido para uma nova licença sem sua permissão e, como não queremos perder seu código, gostaríamos de entrar em contato. Lembre-se de que este projeto permanece de código aberto!

Prazo final:
Se não recebermos uma resposta, ou se você recusar, infelizmente, teremos que remover suas contribuições do Stirling-PDF antes da mudança de licença, que está prevista para os próximos meses.

Obrigado!
Suas contribuições são inestimáveis ​​e esperamos continuar a tê-las em Stirling-PDF sob a nova licença. Sinta-se à vontade para perguntar se você tiver alguma dúvida ou preocupação sobre essa mudança.

Melhor,
Froodle
Mantenedor Stirling-PDF

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants