贡献代码

官网英文原文地址：http://dev.px4.io/starting-contributing.html

核心开发团队和社区的联系信息可以在下面找到。PX4项目使用了三个分支Git branching model:

  • master 默认情况下不稳定，可以看到快速的开发。
  • beta 已充分测试，面向飞行测试者。
  • stable 指向最新的发布分支。

我们尝试通过rebases保持一个线性的历史，避免Github flow。但是由于全球的开发队伍和快速的开发转移，我们会定期分类合并。

为了贡献新的功能，首先注册Github账户，然后fork仓库，创建新分支，加入你的改变，最后发送[pull request]。当它们通过我们的持续的综合测试，更新就会被合并。

所有的贡献必须在 BSD 3-clause license许可下进行,并且所有的代码在使用上不能提出任何的，进一步的限制。

Commits and Commit Messages

Please use descriptive, multi-paragraph commit messages for all non-trivial changes. Structure them well so they make sense in the one-line summary but also provide full detail.

  1. Component: Explain the change in one sentence. Fixes #1234
  3. Prepend the software component to the start of the summary
  4. line, either by the module name or a description of it.
  5. (e.g. "mc_att_ctrl" or "multicopter attitude controller").
  7. If the issue number is appended as <Fixes #1234>, Github
  8. will automatically close the issue when the commit is
  9. merged to the master branch.
  11. The body of the message can contain several paragraphs.
  12. Describe in detail what you changed. Link issues and flight
  13. logs either related to this fix or to the testing results
  14. of this commit.
  16. Describe the change and why you changed it, avoid to
  17. paraphrase the code change (Good: "Adds an additional
  18. safety check for vehicles with low quality GPS reception".
  19. Bad: "Add gps_reception_check() function").
  21. Reported-by: Name <email@px4.io>

Use git commit -s to sign off on all of your commits. This will add signed-off-by: with your name and email as the last line.

This commit guide is based on best practices for the Linux Kernel and other projects maintained by Linus Torvalds.

测试飞行结果

飞行测试对于保证质量非常重要，请从microSD卡上传飞行日志到 Log Muncher，并在论坛分享连接，附带有书面飞行报告。

论坛和聊天

 每周开发者电话会议

PX4团队在每周同时进行电话联系（通过Mumble client)客户端连接）。

  • TIME: 19:00h Zurich time, 1 p.m. Eastern Time, 10 a.m. Pacific Standard Time
  • Server: mumble.dronecode.org
    • Port: 10028
    • Channel: PX4 Channel
    • The agenda is announced the same day on the px4users forum