Skip to content
Browse files

Merge pull request #3 from gmotta/master

Updating 6 paragraphs from EN to PT-BR
  • Loading branch information...
2 parents 64f10ff + e5d1944 commit 72a85e5c8d98caa7f3431dbf701a5729ad5b67db @dwildt dwildt committed
Showing with 7 additions and 7 deletions.
  1. +7 −7 Lord-of-the-Files.pt-br.txt
View
14 Lord-of-the-Files.pt-br.txt
@@ -43,31 +43,31 @@ Assim como outros projetos de geeks que tivemos sucesso, o GitHub começou com d
[[As they built out their sites at Cnet, Wanstrath and Hyett wound up making a lot of improvements to Ruby on Rails itself. But they found it wasn’t so easy to get those changes integrated back into the open-source project. Following the then-dominant model of open source development, Rails was managed by a cadre of trusted coders who’d been given permission to “commit” changes to the project’s source code. To get one of their changes added to the central code, Wanstrath and Hyett would have to lobby one of those trusted coders and convince him that their change was worth integrating. That was often more work than writing the code in the first place.]]
-As they built out their sites at Cnet, Wanstrath and Hyett wound up making a lot of improvements to Ruby on Rails itself. But they found it wasn’t so easy to get those changes integrated back into the open-source project. Following the then-dominant model of open source development, Rails was managed by a cadre of trusted coders who’d been given permission to “commit” changes to the project’s source code. To get one of their changes added to the central code, Wanstrath and Hyett would have to lobby one of those trusted coders and convince him that their change was worth integrating. That was often more work than writing the code in the first place.
+Enquanto eles construiam os sites no Cnet, Wanstrath e Hyett acabaram implementando muitas melhorias no Ruby on Rails. Mas eles descobriram que não era tão fácil fazer com que essas melhorias fossem integradas no código fonte do projeto software-livre. Para fazer com que uma alteração fosse incluida no repositório central, Wanstrath e Hyett tiveram que convencer um dos desenvolvedores de confiança daquele projeto para que a mudança deles valesse a pena e fosse integrada. Esse trabalho normalmente levava mais tempo do que desenvolver a melhoria.
[[They weren’t the only developers chafing under that Trusted Gatekeeper model of open source. A decade ago, Linus Torvalds found himself struggling to manage his role as gatekeeper of the Linux operating system he invented. In the beginning, Torvalds hosted Linux on a website belonging to the University of Helsinki. If people found a bug in the code, they’d send him a file with the changes via e-mail. If Torvalds read the e-mail and liked the changes, he’d incorporate them into Linux. But Torvalds is notorious for not reading all of his e-mail, so as the project got popular, more and more submissions were slipping through the cracks.]]
-They weren’t the only developers chafing under that Trusted Gatekeeper model of open source. A decade ago, Linus Torvalds found himself struggling to manage his role as gatekeeper of the Linux operating system he invented. In the beginning, Torvalds hosted Linux on a website belonging to the University of Helsinki. If people found a bug in the code, they’d send him a file with the changes via e-mail. If Torvalds read the e-mail and liked the changes, he’d incorporate them into Linux. But Torvalds is notorious for not reading all of his e-mail, so as the project got popular, more and more submissions were slipping through the cracks.
+Eles não eram os únicos desenvolvedores impacientes que precisavam de um intermediário de confianca para contribuir com o software livre. Uma década atrás, Linus Torvalds estava lutando para lidar com a sua posição de guardião do sistema operacional Linux, que ele inventou. No começo, Torvalds hospedava o Linux em um website que pertencia a Universidade de Helsinki. Se as pessoas encontrassem um problema no código, elas tinham que enviar para ele o arquivo com as alterações via e-mail. Se Torvalds lesse o email e gostasse das alterações ele incorporava as mudanças no Linux. Mas Torvalds é notóriamente conhecido por não ler todos os seus emails, então quando o projeto se popularizou, mais e mais emails de sugestões e correções acabaram sendo perdidos.
[[This was the dirty little secret of open-source software. With the average free software project, large amounts of code — maybe even most code — never actually got used. It was often just too hard for casual users to show developers the changes they’d made and then easily merge those changes back into the open-source code base.]]
-This was the dirty little secret of open-source software. With the average free software project, large amounts of code — maybe even most code — never actually got used. It was often just too hard for casual users to show developers the changes they’d made and then easily merge those changes back into the open-source code base.
+Esse era o segredo escuso do software livre. Como a média dos projetos de software livre, grandes quantidades de código - talvez até maioria do código - nunca foi de fato utilizado. Normalmente era muito díficil para que os usuários mostrassem aos desenvolvedor as suas alterações e que eles integrassem as alterações de volta ao respositório que continha o código do projeto open-source.
[[The Second Coming of Linus]]
-The Second Coming of Linus
+A segunda aparição de Linus
[[So in 2005, Torvalds created Git, version control software specifically designed to take away the busywork of managing a software project. Using Git, anybody can tinker with their own version of Linux — or indeed any software project — and then, with a push of a button, share those changes with Torvalds or anyone else. There is no gatekeeper. In practical terms, Torvalds created a tool that makes it easy for someone to create an alternative to his Linux project. In technical terms, that’s called a “fork”.]]
-So in 2005, Torvalds created Git, version control software specifically designed to take away the busywork of managing a software project. Using Git, anybody can tinker with their own version of Linux — or indeed any software project — and then, with a push of a button, share those changes with Torvalds or anyone else. There is no gatekeeper. In practical terms, Torvalds created a tool that makes it easy for someone to create an alternative to his Linux project. In technical terms, that’s called a “fork”.
+Então em 2005, Torvalds criou Git, um software para controle de versão projetado específicamente para remover o árduo trabalho de gerenciar projetos de software livre. Usando Git, qualquer um poderia trabalhar com a sua própria versão do Linux - ou de qualquer outro projeto de software - e então, com o clique de um botão, compartilhar essas alterações com Torvalds ou qualquer outra pessoa. Não existe nenhum guardião do código fonte. Em termos práticos, Torvalds criou uma ferramenta que possibilita e facilita que outras pessoas criem versões alternativas do seu projeto Linux. Em termos técnicos, chamamos isto de criar um "fork".
[[Back in the 1990s, forking was supposed to be a bad thing. It’s what created all of those competing, incompatible versions of Unix. For a while, there was a big fear that someone would somehow create their own fork of Linux, a version of the operating system that wouldn’t run the same programs or work in the same way. But in the Git world, forking is good. The trick was to make sure the improvements people worked out could be shared back with the community. It’s better to let people fork a project and tinker away with their own changes, than to shut them out altogether by only letting a few trusted authorities touch the code.]]
-Back in the 1990s, forking was supposed to be a bad thing. It’s what created all of those competing, incompatible versions of Unix. For a while, there was a big fear that someone would somehow create their own fork of Linux, a version of the operating system that wouldn’t run the same programs or work in the same way. But in the Git world, forking is good. The trick was to make sure the improvements people worked out could be shared back with the community. It’s better to let people fork a project and tinker away with their own changes, than to shut them out altogether by only letting a few trusted authorities touch the code.
+Em 1990, forking era considerado uma coisa ruim. Foi o que criou toda a competição, versões incompatíveis de Unix. Por um momento, houve um grande temor que alguem criasse o próprio fork do Linux, uma versão do sistema operacional que não executaria os mesmos programas ou que não funcionasse do mesmo modo. Mas no mundo do Git, forking é bom. O segredo era garantir que as melhorias que as pessoas estavam trabalhando pudessem ser compartilhadas com o resto da comunidade. É melhor que várias pessoas façam o fork de um projeto e cada uma contribua do seu jeito com as suas mudanças do que silenciar a todos, permitindo que apenas poucos contribuidores confiáveis possam tocar no código fonte.
[[On a rare sunny February day in Portland, Torvalds demonstrates Git for Wired at his home office. With a few keystrokes, he quickly spots two new kernel submissions that change the same kernel code in different ways, a potential problem source.]]
-On a rare sunny February day in Portland, Torvalds demonstrates Git for Wired at his home office. With a few keystrokes, he quickly spots two new kernel submissions that change the same kernel code in different ways, a potential problem source.
+Em um raro dia ensolarado em Fevereiro na cidade de Portland, Torvalds demonstrou Git para Wired no seu home-office. Com apenas algumas teclas, ele rapidamente identificou duas novas submissões de kernal que alteraram código fonte relacionado ao kernal de maneiras diferentes, seria uma possível fonte de problemas.
[[The old regime “makes it very hard to start radical new branches because you generally need to convince the people involved in the status quo up-front about their need to support that radical branch,” Torvalds says. “In contrast, Git makes it easy to just ‘do it’ without asking for permission, and then come back later and show the end result off — telling people ‘look what I did, and I have the numbers to show that my approach is much better.’”]]

0 comments on commit 72a85e5

Please sign in to comment.
Something went wrong with that request. Please try again.