GitBook: [#1] Plugin standards documentation (#2011)

felixwang9817 · web-flow · commit c50b3986cb55 · 2021-11-11T11:56:23.000-08:00
* GitBook: [#1] Plugin standards documentation Signed-off-by: Felix Wang <wangfelix98@gmail.com> * Modify Kafka documentation Signed-off-by: Felix Wang <wangfelix98@gmail.com>
diff --git a/docs/getting-started/third-party-integrations.md b/docs/getting-started/third-party-integrations.md
@@ -1,6 +1,6 @@
 # Third party integrations
 
-We integrate with a wide set of tools and technologies so you can make Feast work in your existing stack. Many of these integrations are maintained as plugins to the main Feast repo.&#x20;
+We integrate with a wide set of tools and technologies so you can make Feast work in your existing stack. Many of these integrations are maintained as plugins to the main Feast repo.
 
 {% hint style="info" %}
 Don't see your offline store or online store of choice here? Check our our guides to make a custom one!
@@ -19,7 +19,7 @@ Don't see your offline store or online store of choice here? Check our our guide
 * [x] [Synapse source (community plugin)](https://github.com/Azure/feast-azure)
 * [x] [Hive (community plugin)](https://github.com/baineng/feast-hive)
 * [x] [Postgres (community plugin)](https://github.com/nossrannug/feast-postgres)
-* [ ] Kafka source (Planned for Q4 2021)
+* [x] Kafka source (with [push support into the online store](https://docs.feast.dev/reference/alpha-stream-ingestion))
 * [ ] Snowflake source (Planned for Q4 2021)
 * [ ] HTTP source
 
@@ -56,3 +56,17 @@ Don't see your offline store or online store of choice here? Check our our guide
 
 
 
+## Standards
+
+In order for a plugin integration to be highlighted on this page, it must meet the following requirements:
+
+1. The plugin must have tests. Ideally it would use the Feast universal tests (see this [guide](broken-reference) for an example), but custom tests are fine.
+2. The plugin must have some basic documentation on how it should be used.
+3. The author must work with a maintainer to pass a basic code review (e.g. to ensure that the implementation roughly matches the core Feast implementations).&#x20;
+
+In order for a plugin integration to be merged into the main Feast repo, it must meet the following requirements:
+
+1. The PR must pass all integration tests. The universal tests (tests specifically designed for custom integrations) must be updated to test the integration.
+2. There is documentation and a tutorial on how to use the integration.
+3. The author (or someone else) agrees to take ownership of all the files, and maintain those files going forward.
+4. If the plugin is being contributed by an organization, and not an individual, the organization should provide the infrastructure (or credits) for integration tests.
