From 46a02afba116eb3da0d7c91c6ebc091c6fa52670 Mon Sep 17 00:00:00 2001 From: Jonas Vautherin Date: Wed, 15 May 2019 09:59:18 +0200 Subject: [PATCH] RFC 0011: Update RFC document following WG call --- text/0011-mavlink-sdk.md | 1 - 1 file changed, 1 deletion(-) diff --git a/text/0011-mavlink-sdk.md b/text/0011-mavlink-sdk.md index b581cf4..c1abbcb 100644 --- a/text/0011-mavlink-sdk.md +++ b/text/0011-mavlink-sdk.md @@ -26,7 +26,6 @@ The proposition goes as follows: * Contributions to the SDK should come with adequate automated testing to the same quality level as standard plugins. * Contributions do not necessarily need to support all flight stacks to be merged, as long as they do not break existing test suites. * The contributor must commit to maintain the code. If not maintained, the code might be removed. - * The people with maintenance rights is the superset of the current MAVLink and SDK teams. # Relation to other MAVLink implementations