From 9130829a8630d4f7eca683535bb690505f4e4dfe Mon Sep 17 00:00:00 2001 From: ES-Alexander Date: Tue, 13 Sep 2022 23:57:50 +1000 Subject: [PATCH] content: add developers and contributing section --- content/developers/_index.md | 8 +++++++ content/developers/contributing.md | 37 ++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+) create mode 100644 content/developers/_index.md create mode 100644 content/developers/contributing.md diff --git a/content/developers/_index.md b/content/developers/_index.md new file mode 100644 index 00000000..cb427474 --- /dev/null +++ b/content/developers/_index.md @@ -0,0 +1,8 @@ ++++ +title = "Developers" +description = "Developer documentation." +date = 2022-09-13T23:30:00+00:00 +sort_by = "weight" +weight = 1 +template = "docs/section.html" ++++ diff --git a/content/developers/contributing.md b/content/developers/contributing.md new file mode 100644 index 00000000..58a3447e --- /dev/null +++ b/content/developers/contributing.md @@ -0,0 +1,37 @@ ++++ +title = "Contributing" +description = "Contribution Guidelines." +date = 2022-09-13T22:27:00+10:00 +template = "docs/page.html" +sort_by = "weight" +weight = 0 +draft = false +[extra] +lead = 'Our software and documentation are open for contributions - join us in developing the future!' +toc = true +top = false ++++ + +## Contribution Pathways + +- [Blue Robotics](https://github.com/bluerobotics/software-guidelines) +- [ArduPilot](https://ardupilot.org/dev/docs/contributing.html) + - [Top Contributors](https://github.com/ardupilot/ardupilot#top-contributors) + - [How to Get Involved](https://github.com/ardupilot/ardupilot#how-to-get-involved) +- [QGroundControl](https://dev.qgroundcontrol.com/master/en/contribute/) +- [MAVLink](https://mavlink.io/en/contributing/contributing.html) + +## This Documentation + +Add a new section / version via a repository/branch as a submodule +``` +git submodule add -b --name +``` + +### In General +1. Fork the repo +1. make a new branch for development +1. submit a pull request to the original repo +1. make changes as relevant +1. clean up commits with an interactive rebase and force push +1. sync your repo branch with the upstream branch once the PR is merged