[GitHub] [incubator-devlake-website] keon94 commented on a diff in pull request #265: [issue-3123][Devlake]: Singer-spec Plugin Documentation

[GitBox <gi...@apache.org>]

keon94 commented on code in PR #265:
URL: https://github.com/apache/incubator-devlake-website/pull/265#discussion_r998800958


##########
docs/DeveloperManuals/PluginImplementation.md:
##########
@@ -17,8 +17,15 @@ A plugin may extend DevLake's capability in three ways:
 2. Transforming/enriching existing data
 3. Exporting DevLake data to other data systems
 
+## Types of plugins
 
-## How do plugins work?
+There are, as of now, support for two types of plugins:
+
+1. __*Conventional plugins*__: These are the primary type of plugins used by Devlake, and require the developer to write the most amount of code starting from fetching (collecting) data from data sources to converting them into our normalized datamodels and storing them.
+2. __*Singer-spec plugins*__: These plugins utilize [Singer-taps](https://www.singer.io/) to retrieve data from data-sources thereby eliminating the developer's burden of writing the collection logic. More on them [here](#how-do-singer-spec-plugins-work).
+
+
+## How do conventional plugins work?

Review Comment:
   I chose "conventional" as way of referring to the original plugins. Open to suggestions of better adjectives



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@devlake.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org