# Support

## Mailing List/Discussion

The core development team and community are active on the [mailing list](https://groups.google.com/forum/#!forum/mavlink).

## Reporting Bugs & Issues

If you have any problems using MAVLink first post them on the [mailing list](https://groups.google.com/forum/#!forum/mavlink).

If directed by the development team, issues may be raised on [Github here](https://github.com/mavlink/mavlink/issues).

## Dev Call {#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: {#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](https://github.com/mavlink/mavlink/wiki#weekly-meetingsagendas).

- 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**](https://github.com/mavlink/mavlink/labels/Dev%20Call) label on Github.

#### Schedule {#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).

- **Call:** [https://meet.jit.si/mavlink](https://meet.jit.si/mavlink)
- **Time:** See [Dronecode calendar](https://www.dronecode.org/calendar/)
