Files
mavlink-devguide/en/about/support.md
T
Hamish Willee b6c49b2cd1 Test migration to vitepress (#551)
* Add package/.vitepress folders - more work to be done

* Fix up config and add site/favicons

* Update styles for wide tables

* Rename English files from README.md to index.md

* Add root home page

* Update .gitignore for vitepress

* Delete unused: travis, book, redirects

* Fix up all Notes

* Warnings and notes - convert to github format

* Add running workflow

* Add yarn lock file

* Fix up links README.md to index.md

* Add lock files
2024-11-27 16:59:53 +11:00

1.7 KiB

Support

Mailing List/Discussion

The core development team and community are active on the mailing list.

Reporting Bugs & Issues

If you have any problems using MAVLink first post them on the mailing list.

If directed by the development team, issues may be raised on Github here.

Dev Call

MAVLink developers, adopting companies and the surrounding community of users meet regularly to help define the direction of the project, discuss RFCs, Issues and have a Q&A session.

Tip

The call is open to anyone who wants to contribute to the ongoing development of the project (not just the dev team). This is a great opportunity to meet the team.

Who should attend:

  • Core project maintainers
  • Component maintainers
  • Dronecode members
  • Community members
  • Anyone interested in the development of MAVLink

Agenda

Meeting agenda (and historical meeting minutes) are available on the MAVLink wiki here.

  • Add topics that you'd like to discuss and issues you'd like to unblock.
  • Nominate Issues and PRs for the call with the Dev Call label on Github.

Schedule

There is a recurring bi-weekly call which covers Asia-Europe overlap (there is also a reserved call slot for a Europe-Americas overlap on PST timezone that can be used when needed).