Hamish Willee 88d623bedb
Move PX4 Guide source into /docs (#24490)
* Add vitepress tree

* Update existing workflows so they dont trigger on changes in the docs path

* Add nojekyll, package.json, LICENCE etc

* Add crowdin docs upload/download scripts

* Add docs flaw checker workflows

* Used docs prefix for docs workflows

* Crowdin obvious fixes

* ci: docs move to self hosted runner

runs on a beefy server for faster builds

Signed-off-by: Ramon Roche <mrpollo@gmail.com>

* ci: don't run build action for docs or ci changes

Signed-off-by: Ramon Roche <mrpollo@gmail.com>

* ci: update runners

Signed-off-by: Ramon Roche <mrpollo@gmail.com>

* Add docs/en

* Add docs assets and scripts

* Fix up editlinks to point to PX4 sources

* Download just the translations that are supported

* Add translation sources for zh, uk, ko

* Update latest tranlsation and uorb graphs

* update vitepress to latest

---------

Signed-off-by: Ramon Roche <mrpollo@gmail.com>
Co-authored-by: Ramon Roche <mrpollo@gmail.com>
2025-03-13 16:08:27 +11:00

2.1 KiB

지원

This page may be out out of date. See the latest version.

이 절에서는 핵심 개발팀과 커뮤니티의 지원을 받는 방법을 알려드립니다.

포럼 및 채팅

The core development team and community are active on the following channels:

  • PX4 Discuss Forum - Post here first!
  • PX4 Discord - Post here if you don't get a response in discuss within a few days (include a link to your forum topic).

:::tip The Discuss Forum is much preferred because it is indexed by search engines and serves as a common knowledge base. :::

문제 진단

문제의 원인이 무엇인지 확실하지 않고 문제 분석의 도움을 원하시면,

Issue & Bug Reporting

  • Upload logs to Flight Log Review
  • Open a Github Issue. This must include a flight report with as much detail as possible (enough for the issue to be reproduced) and links to your logs on Flight review.

주간 온라인 개발자 회의

:::tip Developers are most welcome to attend the weekly dev call (and other developer events) to engage more deeply with the project. :::

The Dev Call is a weekly meeting attended by the PX4 dev team to discuss platform technical details, coordinate activities and perform in-depth analysis.

There is also space in the agenda to discuss pull requests, major impacting issues and Q&A.