Merge branch 'master' into AceTheCreator-patch-2

Author: thulieblack

.github/workflows/create-event-ad-hoc.yml

@@ -30,7 +30,7 @@ jobs:
       meeting_desc: ${{ github.event.inputs.desc }}
       meeting_banner: ${{ github.event.inputs.meeting_banner }}
       host: lpgornicki@gmail.com
-      alternative_host: "jonas-lt@live.dk,devlopergene@gmail.com,sibanda.thulie@gmail.com,alejandra.olvera.novack@gmail.com,samir.amzani@gmail.com,oluwabamikemi@gmail.com"
+      alternative_host: "muibudeenaishat@gmail.com,devlopergene@gmail.com,sibanda.thulie@gmail.com,alejandra.olvera.novack@gmail.com,samir.amzani@gmail.com,oluwabamikemi@gmail.com"
       issue_template_path: .github/workflows/create-event-helpers/issues_templates/ad-hoc.md
       create_zoom: true
     secrets:

AMBASSADORS_MEMBERS.json

@@ -287,72 +287,6 @@
       }
     ]
   },
-  {
-    "name": "Jesse Menning",
-    "github": "jessemenning",
-    "twitter": "JesseMenning",
-    "bio": "Jesse Menning teams with companies and government agencies to design event-driven architecture and microservices at scale. To guide those discussions, I draw upon more than 15 years of integration architecture and implementation experience, particularly with IBM and Solace platforms. I've been involved with AsyncAPI since 2020, along with other open-source initiatives such as CloudEvents and OpenTelemetry.",
-    "linkedin": "jesse-menning",
-    "company": "Solace",
-    "title": "Architect, Office of the CTO at Solace",
-    "img": "https://avatars.githubusercontent.com/u/62108913?v=4",
-    "contributions": [
-      {
-        "type": "article",
-        "title": "AsyncAPI 2.3 Adds Solace Bindings to Unlock Full Power of PubSub+",
-        "date": {
-          "year": 2022,
-          "month": "January"
-        },
-        "link": "https://solace.com/blog/asyncapi-adds-solace-bindings/"
-      },
-      {
-        "type": "article",
-        "title": "Align Production Reality and Event Documentation with the AsyncAPI Discovery Tool",
-        "date": {
-          "year": 2021,
-          "month": "November"
-        },
-        "link": "https://solace.com/blog/asyncapi-discovery-tool/"
-      },
-      {
-        "type": "article",
-        "title": "AsyncAPI vs. OpenAPI: Answers to Your Burning Questions About the Two Leading API Specs",
-        "date": {
-          "year": 2021,
-          "month": "June"
-        },
-        "link": "https://solace.com/blog/asyncapi-vs-openapi/"
-      },
-      {
-        "type": "article",
-        "title": "AsyncAPI, CloudEvents, OpenTelemetry: Which Event-Driven Specs Should Your DevOps Include?",
-        "date": {
-          "year": 2021,
-          "month": "March"
-        },
-        "link": "https://solace.com/blog/asyncapi-cloudevents-opentelemetry-event-driven-specs-devops/"
-      },
-      {
-        "type": "presentation",
-        "title": "Future of AsyncAPI, Panel discussion, AsyncAPI Conference",
-        "date": {
-          "year": 2021,
-          "month": "November"
-        },
-        "link": "https://www.youtube.com/watch?v=3EeMHhbwyOQ"
-      },
-      {
-        "type": "presentation",
-        "title": "Thinking Out Loud #4 — with Jesse Menning",
-        "date": {
-          "year": 2021,
-          "month": "August"
-        },
-        "link": "https://www.youtube.com/watch?v=eJewFUR-OaM"
-      }
-    ]
-  },
   {
     "name": "Ludovic Dussart",
     "github": "M3lkior",
@@ -482,73 +416,6 @@
       }
     ]
   },
-  {
-    "name": "Mete Atamel",
-    "github": "meteatamel",
-    "twitter": "meteatamel",
-    "country": "🇬🇧",
-    "bio": "Mete is a Software Engineer and a Developer Advocate with 18+ years of experience. Currently, he works in the Developer Relations team at Google in London. He builds tools, demos, tutorials, and gives talks to educate and help developers to be successful on Google Cloud. As a regular speaker at tech conferences, he has spoken over 345+ events since 2016 on modern application development topics such as Kubernetes, Istio, Knative, serverless, event-driven architectures, and microservice orchestration. Prior to his current role, he was a Software Engineer/Architect/Tech Lead at Nokia, EMC, Adobe, Skype, and Microsoft building various client and server technologies, resulting in multiple patents.",
-    "linkedin": "mete-atamel",
-    "company": "Google",
-    "title": "Software Engineer and Developer Advocate at Google",
-    "img": "https://avatars.githubusercontent.com/u/1177542?v=4",
-    "contributions": [
-      {
-        "type": "article",
-        "title": "AsyncAPI Basics",
-        "date": {
-          "year": 2023,
-          "month": "May"
-        },
-        "link": "https://medium.com/google-cloud/asyncapi-basics-6e6394c9587"
-      },
-      {
-        "type": "article",
-        "title": "AsyncAPI Tools",
-        "date": {
-          "year": 2023,
-          "month": "May"
-        },
-        "link": "https://medium.com/google-cloud/asyncapi-tools-dd59f9236b20"
-      },
-      {
-        "type": "article",
-        "title": "Understanding AsyncAPI’s publish & subscribe semantics with an example",
-        "date": {
-          "year": 2023,
-          "month": "May"
-        },
-        "link": "https://medium.com/google-cloud/understanding-asyncapis-publish-subscribe-semantics-with-an-example-cfa1cc3faef5"
-      },
-      {
-        "type": "article",
-        "title": "CloudEvents + AsyncAPI",
-        "date": {
-          "year": 2023,
-          "month": "May"
-        },
-        "link": "https://medium.com/google-cloud/cloudevents-asyncapi-fa8ef63f28e0"
-      },
-      {
-        "type": "article",
-        "title": "Google Cloud Pub/Sub + AsyncAPI",
-        "date": {
-          "year": 2023,
-          "month": "May"
-        },
-        "link": "https://medium.com/google-cloud/google-cloud-pub-sub-asyncapi-6ea3c1ed3c49"
-      },
-      {
-        "type": "presentation",
-        "title": "Open standards for building event-driven applications in the cloud",
-        "date": {
-          "year": 2023,
-          "month": "June"
-        },
-        "link": "https://www.youtube.com/watch?v=6Igp4DhK_hE"
-      }
-    ]
-  },
   {
     "name": "Raphael De Lio",
     "github": "raphaeldelio",
@@ -608,6 +475,24 @@
           "month": "June"
         },
         "link": "https://confengine.com/conferences/selenium-conf-2024/proposal/20021/unshackling-your-system-under-test-shift-left-testing-through-dependency-isolation"
+      },
+      {
+        "type": "talk",
+        "title": "Using API spec as an Executable Contract To Mock and Test Microservices",
+        "date": {
+          "year": 2024,
+          "month": "October"
+        },
+        "link": "https://www.youtube.com/watch?v=wiM20HTCerM"
+      },
+      {
+        "type": "talk",
+        "title": "Contract-Driven Development for Event-Driven Architectures",
+        "date": {
+          "year": 2024,
+          "month": "December"
+        },
+        "link": "https://conference.asyncapi.com/venue/Paris"
       }
     ]
   },

AMBASSADOR_ORGANIZATION.md

@@ -53,7 +53,7 @@ Examples:
 
 ### Become an AsyncAPI Ambassador
 
-The process of becoming an ambassador is very simple. Go to the **community** repository and open a PR to edit the `ambassadors.json` file. The TSC will then evaluate your candidacy!
+The process of becoming an ambassador is very simple. Go to the **community** repository and open a PR to edit the `AMBASSADORS_MEMBERS.json` file. The TSC will then evaluate your candidacy!
 
 That PR doesn't have to be created by the ambassador candidate; any community member may open a PR to submit someone's application to the AsyncAPI Ambassador Program. 
 

CODEOWNERS

@@ -5,10 +5,12 @@
 # For more details, read the following article on GitHub: https://help.github.com/articles/about-codeowners/.
 
 # The default owners are automatically added as reviewers when you open a pull request unless different owners are specified in the file.
-* @alequetzalli @derberg @asyncapi-bot-eve @thulieblack
+* @quetzalliwrites @derberg @asyncapi-bot-eve @thulieblack
 
 # All ambassadors related files
 AMBASSADOR* @thulieblack
 
 # Code Of Conduct
 /code_of_conduct/ @asyncapi/code_of_conduct
+CODE_OF_CONDUCT.md @asyncapi/code_of_conduct
+slack-etiquette.md @asyncapi/code_of_conduct

CODE_OF_CONDUCT.md

@@ -45,7 +45,7 @@ The Code of Conduct Committee (CoC Committee) responds to, investigates, and res
 
 The Committee has the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that do not align with this Code of Conduct. The Committee may also temporarily or permanently ban any contributor for inappropriate, threatening, offensive, or harmful behaviors to the community.
 
-For more details, please see the [CoC Committee and Incident Resolution Procedure](https://github.com/asyncapi/community/pull/1013/files).
+For more details, please see the [CoC Committee and Incident Resolution Procedure](https://github.com/asyncapi/community/tree/master/code_of_conduct).
 
 ## Enforcement
 

Emeritus.yaml

@@ -1,5 +1,6 @@
-# This file lists individuals who were previously TSC members but are no longer active.
-emeritus:
+# This file lists individuals who were previously TSC members and Ambassadors but are no longer active.
+
+emeritus_tsc:
   - jotamusik 
   - LouisXhaferi
   - aeworxet
@@ -14,4 +15,10 @@ emeritus:
   - kieranm1999
   - jefflufc
   - lewis-relph
-  - emilianozublena
+  - emilianozublena
+  - NektariosFifes
+  - M3lkior
+
+emeritus_ambassadors:
+  - jessemenning
+  - meteatamel