Master

.github/CODEOWNERS

@@ -1,55 +1,57 @@
 # See for instructions on this file https://help.github.com/articles/about-codeowners/
 
+# By default Microsoft owns the entire repo
+# Unless overridden later
 *       @Microsoft/connectors
 
-/certified-connectors/ahead @tjkb
-/certified-connectors/Data8 @mattybeard
-/certified-connectors/Encodian @Encodian
-/certified-connectors/Plumsail\ Documents @RFlipper
-/certified-connectors/Plumsail\ Forms @RFlipper
-/certified-connectors/Plumsail\ HelpDesk @RFlipper
-/certified-connectors/Plumsail\ SP @RFlipper
-/certified-connectors/Rencore @waldekmastykarz
-/certified-connectors/WebMerge @jeremyjclarke
-/certified-connectors/Yeelight @yusureabc
-/certified-connectors/Aquaforest\ PDF\ Connector @Aquaforest
-/certified-connectors/Cloudmersive\ Data\ Validation @Cloudmersive
-/certified-connectors/Cloudmersive\ Document\ Conversion @Cloudmersive
-/certified-connectors/Cloudmersive\ Image\ Processing @Cloudmersive
-/certified-connectors/Cloudmersive\ PDF @Cloudmersive
-/certified-connectors/Cloudmersive\ Virus\ Scan @Cloudmersive
-/certified-connectors/CompanyConnect @sschutten
-/certified-connectors/D7SMS @d7networks
-/certified-connectors/DBF2XML @yekhoKatyn
-/certified-connectors/ElfsquadProductConfigurator @johannesheesterman
-/certified-connectors/FireText @dp-firetext
-/certified-connectors/HotProfile @masuyama-hammock
-/certified-connectors/JungleMail365 @EnovaPoint-Lewis
-/certified-connectors/KnowledgeLakeRPA @SteveCurran
-/certified-connectors/LeadDesk @Lokenstein
-/certified-connectors/Mitto @mittork
-/certified-connectors/ModuleQ @tom-mq
-/certified-connectors/Mtarget\ SMS @devsmsMTarget
-/certified-connectors/Pushcut @sliemeobn
-/certified-connectors/Rencore\ Governance @waldekmastykarz
-/certified-connectors/Robolytix @ondrejfiala
-/certified-connectors/Scrive\ eSign @MarcusNilssonGithub
-/certified-connectors/ShortURL @cirrussoft
-/certified-connectors/Serverless360 @arunprabhu-kovai
-/certified-connectors/ShareEffect @Rens-Braspenning
-/certified-connectors/SignRequest @michi88
-/certified-connectors/Slascone @its-just-jo
-/certified-connectors/Smarp @pininsmarp
-/certified-connectors/Stormboard @mdbollman
-/certified-connectors/Tallyfy @EricHusa
-/certified-connectors/Way\ We\ Do @danspam
-/certified-connectors/Witivio @NicolasHumann
-/certified-connectors/easyvistaselfhelp @cedric-martin
-/certified-connectors/emfluencemp @ryandeba
-/certified-connectors/envoy @aasimniz95
-/certified-connectors/exghts @exghts
-/certified-connectors/Telephony-Xtended-Service @alainmenag
-/certified-connectors/CloudAppSecurity @robrams
-/certified-connectors/PartnerCenterReferrals @didalal
-/certified-connectors/gofileroom @calvinleong
-/tools/paconn-cli @Microsoft/connectors
+# Speicific owner for Certified Connectors
+/certified-connectors/Aquaforest\ PDF\ Connector/ @Aquaforest
+/certified-connectors/CloudAppSecurity/ @robrams
+/certified-connectors/Cloudmersive\ Data\ Validation/ @Cloudmersive
+/certified-connectors/Cloudmersive\ Document\ Conversion/ @Cloudmersive
+/certified-connectors/Cloudmersive\ Image\ Processing/ @Cloudmersive
+/certified-connectors/Cloudmersive\ PDF/ @Cloudmersive
+/certified-connectors/Cloudmersive\ Virus\ Scan/ @Cloudmersive
+/certified-connectors/CompanyConnect/ @sschutten
+/certified-connectors/D7SMS/ @d7networks
+/certified-connectors/DBF2XML/ @yekhoKatyn
+/certified-connectors/Data8/ @mattybeard
+/certified-connectors/ElfsquadProductConfigurator/ @johannesheesterman
+/certified-connectors/Encodian/ @Encodian
+/certified-connectors/FireText/ @dp-firetext
+/certified-connectors/HotProfile/ @masuyama-hammock
+/certified-connectors/JungleMail365/ @EnovaPoint-Lewis
+/certified-connectors/KnowledgeLakeRPA/ @SteveCurran
+/certified-connectors/LeadDesk/ @Lokenstein
+/certified-connectors/Mitto/ @mittork
+/certified-connectors/ModuleQ/ @tom-mq
+/certified-connectors/Mtarget\ SMS/ @devsmsMTarget
+/certified-connectors/PartnerCenterReferrals/ @didalal
+/certified-connectors/Plumsail\ Documents/ @RFlipper
+/certified-connectors/Plumsail\ Forms/ @RFlipper
+/certified-connectors/Plumsail\ HelpDesk/ @RFlipper
+/certified-connectors/Plumsail\ SP/ @RFlipper
+/certified-connectors/Pushcut/ @sliemeobn
+/certified-connectors/Rencore/ @waldekmastykarz
+/certified-connectors/Rencore\ Governance/ @waldekmastykarz
+/certified-connectors/Robolytix/ @ondrejfiala
+/certified-connectors/Scrive\ eSign/ @MarcusNilssonGithub
+/certified-connectors/Serverless360/ @arunprabhu-kovai
+/certified-connectors/ShareEffect/ @Rens-Braspenning
+/certified-connectors/ShortURL/ @cirrussoft
+/certified-connectors/SignRequest/ @michi88
+/certified-connectors/Slascone/ @its-just-jo
+/certified-connectors/Smarp/ @pininsmarp
+/certified-connectors/Stormboard/ @mdbollman
+/certified-connectors/Tallyfy/ @EricHusa
+/certified-connectors/Telephony-Xtended-Service/ @alainmenag
+/certified-connectors/Way\ We\ Do/ @danspam
+/certified-connectors/WebMerge/ @jeremyjclarke
+/certified-connectors/Witivio/ @NicolasHumann
+/certified-connectors/Yeelight/ @yusureabc
+/certified-connectors/ahead/ @tjkb
+/certified-connectors/easyvistaselfhelp/ @cedric-martin
+/certified-connectors/emfluencemp/ @ryandeba
+/certified-connectors/envoy/ @aasimniz95
+/certified-connectors/exghts/ @exghts
+/certified-connectors/gofileroom/ @calvinleong

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,87 @@
+name: 🐛 Bug report
+description: File a connector bug here!
+title: "[BUG] <title>"
+labels: [bug]
+body: 
+- type: markdown
+  attributes:
+    value: |
+      Thanks for taking the time to fill out this bug report. Remember to include sufficient details and context. If you have multiple bugs, please submit them in separate issues.
+- type: dropdown
+  id: connector-type
+  attributes:
+    label: Type of Connector
+    options:
+      - Certified Connector
+      - Custom Connector
+      - Independent Publisher Connector
+  validations:
+    required: true
+- type: input
+  id: connector-name
+  attributes:
+    label: Name of Connector
+    placeholder: |
+      Enter the name of the connector.
+  validations:
+    required: true
+- type: textarea
+  id: bug-description
+  attributes:
+    label: Describe the bug
+    placeholder: |
+      A clear and concise description of what the bug is.
+  validations:
+    required: true
+- type: dropdown
+  id: security-bug
+  attributes:
+    label: Is this a security bug?
+    options:
+      - Yes, this is a security bug
+      - No, this is not a security bug
+  validations:
+    required: true
+- type: dropdown
+  id: severity
+  attributes:
+    label: What is the severity of this bug?
+    options:
+      - Severity 1 - Connector is broken or there's a very serious issue
+      - Severity 2 - One or more important connector features are down
+      - Severity 3 - Minor issue
+  validations:
+    required: true
+- type: textarea
+  id: reproduce
+  attributes:
+    label: To Reproduce
+    placeholder: |
+      Steps to reproduce the behavior.
+  validations:
+    required: true
+- type: textarea
+  id: expected-behavior
+  attributes:
+    label: Expected behavior
+    placeholder: |
+      A clear and concise description of what you expected to happen.
+  validations:
+    required: true    
+- type: textarea
+  attributes:
+    label: Environment summary
+    value: |
+      Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
+      CLI version (paconn --version)
+      OS version
+      Shell Type (e.g. bash, cmd.exe, Bash on Windows)
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Additional context
+    placeholder: |
+      Add any other context about the problem here.
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,58 @@
+name: 🚀 Feature request
+description: Suggest an idea for an existing connector in this repository!
+title: "[FEATURE REQUEST] <title>"
+body: 
+- type: markdown
+  attributes:
+    value: |
+      New ideas for existing connectors can include support for new actions, triggers, and support for more endpoints. If you need to submit a request for a new connector, please use the New connector request template.
+- type: dropdown
+  id: connector-type
+  attributes:
+    label: Type of Connector
+    options:
+      - Certified Connector
+      - Custom Connector
+      - Independent Publisher Connector
+  validations:
+    required: true
+- type: input
+  id: connector-name
+  attributes:
+    label: Name of Connector
+    placeholder: |
+      Enter the name of the connector.
+  validations:
+    required: true
+- type: textarea
+  id: feature-related-problem
+  attributes:
+    label: Is your feature request related to a problem? Please describe.
+    placeholder: |
+      A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+  validations:
+    required: true
+- type: textarea
+  id: solution-description
+  attributes:
+    label: Describe the solution you'd like
+    placeholder: |
+      A clear and concise description of what you want to happen.
+  validations:
+    required: true
+- type: textarea
+  id: solution-alternatives
+  attributes:
+    label: Describe alternatives you've considered
+    placeholder: |
+      A clear and concise description of any alternative solutions or features you've considered.
+  validations:
+    required: true
+- type: textarea
+  id: additional-context
+  attributes:
+    label: Additional context
+    placeholder: |
+      Add any other context or screenshots about the feature request here.
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/new_connector_request.yaml

@@ -0,0 +1,32 @@
+name: 💡 New connector request
+description: Specify a connector that you need!
+title: "[CONNECTOR REQUEST] <title>"
+body:
+- type: input
+  id: end-service-name
+  attributes:
+    label: Name of the end service.
+    placeholder: |
+      Enter the name of the end service.
+  validations:
+    required: true
+- type: textarea
+  id: potential-use-cases
+  attributes:
+    label:  Describe the potential use cases for this connector
+  validations:
+    required: true
+- type: textarea
+  id: helpful-triggers-actions
+  attributes:
+    label:  What would be the most helpful actions and triggers for this connector?
+  validations:
+    required: true    
+- type: textarea
+  id: additional-context
+  attributes:
+    label: Additional context
+    placeholder: |
+      Add any other context about this new connector.
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/service_team_request.yaml

@@ -0,0 +1,20 @@
+name: 🚧 Service Team Support Request
+description: For select service teams to request CLI-team support for work such as new features, commands, etc.
+title: "[SERVICE TEAM SUPPORT REQUEST] <title>"
+body:
+- type: textarea
+  id: feature-work-requested
+  attributes:
+    label: Description of Feature or Work Requested
+    placeholder: |
+      Provide a brief description of the feature or work requested. A link to conceptual documentation may be helpful too.
+  validations:
+    required: true
+- type: textarea
+  id: target-date
+  attributes:
+    label: Target Date
+    placeholder: |
+      If you have a target date for release of this feature/work, please provide it. While we can't guarantee these dates, it will help us prioritize your request against other requests.
+  validations:
+    required: true

.github/pull_request_template.md

@@ -1,6 +1,19 @@
 
 ---
-Please check the following conditions for your PR.
+### When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :) 
+
+If this is your first time submitting to GitHub and you need some help, please sign up for this [session](https://forms.office.com/pages/responsepage.aspx?id=KtIy2vgLW0SOgZbwvQuRaXDXyCl9DkBHq4A2OG7uLpdUMTFJWFFGVUxBNUFZQjZWRUdaOE5BMFkwNS4u). 
+
+- [ ] I attest that the connector works and I verified by deploying and testing all the operations. 
+- [ ] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
+- [ ] I attest that I have added response schemas to my actions, unless the response schema is dynamic. 
+- [ ] I validated the swagger file, `apiDefinition.swagger.json`, by running `paconn validate` command.
+- [ ] If this is a certified connector, I confirm that `apiProperties.json` has a valid brand color and doesn't use an invalid brand color, `#007ee5` or `#ffffff`. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.
+
+If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:
+- [ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
+- [ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding. 
+- [ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
+- [ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md. 
+
 
-- [ ] `apiDefinition.swagger.json` is validated using `paconn validate` command.
-- [ ] `apiProperties.json` has a valid brand color. Invalid brand colors are `#007ee5` and `#ffffff`.