Ubuntu is a distribution, that means it's a bunch of programs packed together in a nice way. You can contribute in many ways to distributions: maintaining package repositories, checking for bugs, artwork... If you're interested in the programming side, I'm sure you'll enjoy fixing bugs for the many packages that Ubuntu is made of (which are open source projects on their own.) Think of it as a layered approach, and you've got to settle in a layer to help.
Dive into their bugtrackers, find a bug, fix it and submit the patch.
As a rule of thumb the place to start contributing to a project is the bug tracker. Also start following the project from their public VCS compile->run->report bug->provide patch.
I'm not a C++ coder, so I can't help there beyond Googling for tutorials, but if you want to figure out where to start in any open source project, the easiest way is to check out their bug tracker, find a bug, and try to fix it. If you try to dive into something like Ubuntu without direction, you're likely to get lost and overwhelmed.
I bealive you would be more interested on Chromium project for a setout. The browser code can be manipulated on Linux, Windows and Mac with the more appropriate tools. They have a IRC channel too, there you can clarify your doubts. Generally, when you get on great code, it is allways good to resort to the one with more means to do things quickly and easier. Google has a lot of tools and informations that fit to start-up programmers.
如果您想开始为 Linux 内核本身（用 C 编写，而不是 C++ 编写）做出贡献，请观看讲座 编写并提交您的第一个 Linux 内核补丁，该补丁由 FOSDEM 会议提供en.wikipedia.org/wiki/Greg_Kroah-Hartman" rel="nofollow">Grek Groah Hartman，Linux 内核团队的核心成员，是一个很好的开始和激励因素。作为奖励，我认为讲座中提出的建议和贡献点适用于任何其他开源项目。
If you're looking to start contributing to the Linux kernel itself(written in C, not C++) the lecture Write and Submit your first Linux kernel Patch given at the FOSDEM conference by Grek Groah Hartman, core member of the Linux Kernel team himself, is a great start and motivating factor. As a bonus point, the advices and contributing points revealed in the lecture are applicable to any other open source project in my opinion.
There's nothing standing in your way to contributing to Open Source. Start right now with as low as documentation, minor bug fixing or even adding/improving or fixing grammar issues with comments to existing code. All of these are important and they also help develop your knowledge about a given project or part of a project, which will then enable you to dive deeper in more complex aspects of your chosen project.
发布评论
评论（5）
Ubuntu 是一个发行版，这意味着它是一堆以良好方式打包在一起的程序。您可以通过多种方式为发行版做出贡献：维护软件包存储库、检查错误、艺术作品...如果您对编程方面感兴趣，我相信您会喜欢修复 Ubuntu 组成的许多软件包的错误（它们本身就是开源项目。）将其视为一种分层方法，您必须安顿在一个层中来提供帮助。
深入研究他们的错误跟踪器，找到错误，修复它并提交补丁。
Ubuntu is a distribution, that means it's a bunch of programs packed together in a nice way. You can contribute in many ways to distributions: maintaining package repositories, checking for bugs, artwork... If you're interested in the programming side, I'm sure you'll enjoy fixing bugs for the many packages that Ubuntu is made of (which are open source projects on their own.) Think of it as a layered approach, and you've got to settle in a layer to help.
Dive into their bugtrackers, find a bug, fix it and submit the patch.
我想到了几个 C++ 项目：LibreOffice 和 KDE。
LibreOffice 已经列出了一些简单的技巧，因此您应该从这里开始 http://wiki.documentfoundation.org/Easy_Hacks
KDE 还有一些标记为初级作业的任务：
http://techbase.kde.org/Contribute/Junior_Jobs
根据经验，开始为项目做出贡献是错误跟踪器。还可以从他们的公共 VCS 编译 -> 运行 -> 报告错误 -> 提供补丁开始关注该项目。
There are a couple of c++ projects that come to mind: LibreOffice and KDE.
LibreOffice has already made a list of easy hacks so you should start there http://wiki.documentfoundation.org/Easy_Hacks
KDE has also a few tasks marked as Junior Jobs:
http://techbase.kde.org/Contribute/Junior_Jobs
As a rule of thumb the place to start contributing to a project is the bug tracker. Also start following the project from their public VCS compile->run->report bug->provide patch.
我不是 C++ 编码员，所以除了谷歌搜索教程之外我无能为力，但如果你想弄清楚在任何开源项目中从哪里开始，最简单的方法是检查他们的错误跟踪器，找到错误，并尝试修复它。如果你试图在没有方向的情况下深入研究像 Ubuntu 这样的东西，你很可能会迷失方向并不知所措。
您可以在这里找到 Ubuntu 的错误跟踪器：https://launchpad.net/ubuntu
I'm not a C++ coder, so I can't help there beyond Googling for tutorials, but if you want to figure out where to start in any open source project, the easiest way is to check out their bug tracker, find a bug, and try to fix it. If you try to dive into something like Ubuntu without direction, you're likely to get lost and overwhelmed.
You can find Ubuntu's bug tracker here: https://launchpad.net/ubuntu
我相信您会对 Chromium 项目更感兴趣。可以使用更合适的工具在 Linux、Windows 和 Mac 上操作浏览器代码。他们也有一个IRC频道，在那里你可以澄清你的疑虑。
一般来说，当你编写出优秀的代码时，最好求助于具有更多方法的代码来快速、轻松地完成工作。谷歌有很多适合初创程序员的工具和信息。
http 上有一个需要帮助的任务列表://code.google.com/p/chromium/issues/list?q=label:helpwanted&can=2。
克劳迪奥·M·苏扎·儒尼奥尔
开发商
I bealive you would be more interested on Chromium project for a setout. The browser code can be manipulated on Linux, Windows and Mac with the more appropriate tools. They have a IRC channel too, there you can clarify your doubts.
Generally, when you get on great code, it is allways good to resort to the one with more means to do things quickly and easier. Google has a lot of tools and informations that fit to start-up programmers.
There is a list of help-wanted tasks on http://code.google.com/p/chromium/issues/list?q=label:helpwanted&can=2.
Claudio M. Souza Junior
Developer
如果您想开始为 Linux 内核本身（用 C 编写，而不是 C++ 编写）做出贡献，请观看讲座 编写并提交您的第一个 Linux 内核补丁，该补丁由 FOSDEM 会议提供en.wikipedia.org/wiki/Greg_Kroah-Hartman" rel="nofollow">Grek Groah Hartman，Linux 内核团队的核心成员，是一个很好的开始和激励因素。作为奖励，我认为讲座中提出的建议和贡献点适用于任何其他开源项目。
没有什么可以阻碍您为开源做出贡献。现在就从低至文档、小错误修复甚至添加/改进或修复语法问题以及对现有代码的注释开始。所有这些都很重要，它们还有助于加深您对给定项目或项目一部分的了解，这将使您能够更深入地研究所选项目的更复杂的方面。
If you're looking to start contributing to the Linux kernel itself(written in C, not C++) the lecture Write and Submit your first Linux kernel Patch given at the FOSDEM conference by Grek Groah Hartman, core member of the Linux Kernel team himself, is a great start and motivating factor. As a bonus point, the advices and contributing points revealed in the lecture are applicable to any other open source project in my opinion.
There's nothing standing in your way to contributing to Open Source. Start right now with as low as documentation, minor bug fixing or even adding/improving or fixing grammar issues with comments to existing code. All of these are important and they also help develop your knowledge about a given project or part of a project, which will then enable you to dive deeper in more complex aspects of your chosen project.