From b0994c33a76a9369b09368ba344f671a3ae690f8 Mon Sep 17 00:00:00 2001
From: Sean Madsen <sean@seanmadsen.com>
Date: Wed, 13 Dec 2017 17:07:14 -0500
Subject: [PATCH] Clarify requirements for publication in ext dir

I removed this sentence because I don't think it's accurate.

We have these review criteria:
https://docs.civicrm.org/extensions/lifecycle/#review-criteria

The criteria do say that you can't use PHP overrides. But there are
other interfaces (like BAO functions for example) that are not in the
"supported methods" list but also not prohibited based on the extension
review criteria.
---
 docs/extensions/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/extensions/index.md b/docs/extensions/index.md
index bc94630a..c7995c11 100644
--- a/docs/extensions/index.md
+++ b/docs/extensions/index.md
@@ -54,7 +54,7 @@ Extensions which undergo a [formal review](/extensions/lifecycle.md#formal-revie
 
 ## Interacting with core
 
-There are a number of ways in which extensions can interact with core. These are supported to greater or lesser degrees and only extensions that use fully supported methods are eligible for publication in the extensions directory.
+There are a number of ways in which extensions can interact with core. These are supported to greater or lesser degrees.
 
 Fully supported methods are:
 
-- 
GitLab