From 759c2e057789bf8a13d70b60dc349be28b3af504 Mon Sep 17 00:00:00 2001 From: rusefi Date: Sat, 22 Feb 2020 22:36:21 -0500 Subject: [PATCH] HOWTO contribute --- FAQ/HOWTO_contribute_to_firmware.md | 14 ++++++++++++++ FAQ/HOWTO_help_rusEfi.md | 2 ++ 2 files changed, 16 insertions(+) create mode 100644 FAQ/HOWTO_contribute_to_firmware.md diff --git a/FAQ/HOWTO_contribute_to_firmware.md b/FAQ/HOWTO_contribute_to_firmware.md new file mode 100644 index 00000000..b1aecfff --- /dev/null +++ b/FAQ/HOWTO_contribute_to_firmware.md @@ -0,0 +1,14 @@ +The majority of rusEfi code is written in very plain C++ ("C with classes"), with rusEfi console and some code generating +tools written in java. + +Most of the needs are within the C/C++ firmware and automated testing. + +A good first contribution could be adding some automated testing into https://github.com/rusefi/rusefi/tree/master/unit_tests/tests + +For current coverage report see https://rusefi.com/docs/unit_tests_coverage/ + +Testing coverage open tickets: https://github.com/rusefi/rusefi/labels/automated_testing + +All open tickets: https://github.com/rusefi/rusefi/issues + +See https://rusefi.com/wiki/index.php?title=Manual:Try_It for how to work on rusEfi code with zero or minimal hardware. \ No newline at end of file diff --git a/FAQ/HOWTO_help_rusEfi.md b/FAQ/HOWTO_help_rusEfi.md index b1f3d358..0c91032d 100644 --- a/FAQ/HOWTO_help_rusEfi.md +++ b/FAQ/HOWTO_help_rusEfi.md @@ -6,6 +6,8 @@ The weakest point of rusEfi is documentation. If you've played with rusEfi for a [Click here for more details](HOWTO_contribute_to_documentation) +We are also extremely short on software developers. [HOWTO_contribute_to_firmware](HOWTO_contribute_to_firmware) + #### Last but not least