Merge branch 'master' into scroll

.github/workflows/lint-pr-title.yml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       # Since this workflow is REQUIRED for a PR to be mergable, we have to have this 'if' statement in step level instead of job level.
-      - if: ${{ !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors"]'), github.actor) }}
+      - if: ${{ !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors[bot]"]'), github.actor) }}
         uses: amannn/action-semantic-pull-request@505e44b4f33b4c801f063838b3f053990ee46ea7 #version 4.6.0
         id: lint_pr_title
         env:
@@ -24,7 +24,7 @@ jobs:
             The subject "{subject}" found in the pull request title "{title}" should start with a lowercase character.
 
       # Comments the error message from the above lint_pr_title action
-      - if: ${{ always() && steps.lint_pr_title.outputs.error_message != null && !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors"]'), github.actor)}}
+      - if: ${{ always() && steps.lint_pr_title.outputs.error_message != null && !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors[bot]"]'), github.actor)}}
         name: Comment on PR
         uses: marocchino/sticky-pull-request-comment@39c5b5dc7717447d0cba270cd115037d32d28443 #version 2.2
         with:

.github/workflows/sentiment-analysis.yml

@@ -26,7 +26,7 @@ on:
             - edited
 jobs:
     sentiments:
-        if: ${{ !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors"]'), github.actor) }}
+        if: ${{ !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors[bot]"]'), github.actor) }}
         name: Checking sentiments
         runs-on: ubuntu-latest
         steps:

.github/workflows/welcome-first-time-contrib.yml

@@ -14,7 +14,7 @@ on:
 jobs:
   welcome:
     name: Post welcome message
-    if: ${{ !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors"]'), github.actor) }}
+    if: ${{ !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors[bot]"]'), github.actor) }}
     runs-on: ubuntu-latest
     steps:
     - uses: actions/github-script@v3

components/SupportUs.js

@@ -78,6 +78,20 @@ export default function SupportUs({ className = '', showSupportBanner = true })
             title="Restream - Free professional plan subscription."
           />
         </a>
+        </div>
+        <div className="flex flex-wrap mb-4 items-center justify-center md:px-2">
+        <a
+          href="https://sessionize.com/"
+          target="_blank"
+          rel="noopener noreferrer"
+          className="block relative text-center w-2/3 px-4 py-4 sm:p-0 sm:w-1/3 md:w-1/3 lg:w-1/5"
+        >
+          <img
+            className="inline-block px-4 sm:h-9"
+            src="/img/supportus/sessionize.webp"
+            title="Sessionize-Free community license for AACoT Madrid."
+          />
+        </a>
       </div>
 
     </div>

config/meetings.json

@@ -118,5 +118,18 @@
     "calLink": "https://www.google.com/calendar/event?eid=czRmMG5maHRsYjduM2g3dmwxMDM1Z3R0NzAgY19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bn",
     "url": "https://github.com/asyncapi/community/issues/645",
     "date": "2023-04-04T08:00:00.000Z"
+  },
+  {
+    "title": "Spec 3.0 Meeting",
+    "calLink": "https://www.google.com/calendar/event?eid=djhsdjZvbmRsampvb2tsYzhkZWFyc3FtYTAgY19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bn",
+    "url": "https://github.com/asyncapi/community/issues/649",
+    "date": "2023-04-13T15:00:00.000Z"
+  },
+  {
+    "title": "Community Meeting",
+    "calLink": "https://www.google.com/calendar/event?eid=MzgwdmZiMTc4cnBmbTUzdWVlbmM4aWYyM2MgY19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bn",
+    "url": "https://github.com/asyncapi/community/issues/659",
+    "banner": "https://user-images.githubusercontent.com/40604284/229763606-c0b6ed3b-e120-427c-b87d-357856d92777.png",
+    "date": "2023-04-18T16:00:00.000Z"
   }
 ]

pages/docs/tutorials/getting-started/event-driven-architectures.md

@@ -9,7 +9,7 @@ weight: 11
 
 Many developers, architects, and product managers have used REST APIs and are familiar with the synchronous communication paradigm. You make a request and wait for the response. This is exactly how the world wide web works. You enter a URL (e.g., www.google.com) in the browser's address bar and it sends a request to the server. The server then sends the response with the website content. **The web is the greatest implementation of a REST API.**
 
-However, there are certain situations where you don't really need a response from the server. In most cases it's only important to have some confirmation that the request was received. This is also called _"fire and forget"_, and it's very useful when you just want to communicate or inform that "something happened." You're not requesting or asking for anything, thus you don't need a response.  
+However, there are certain situations where you don't need a response from the server. In most cases, it's only important to have some confirmation that the request was received. This is also called _"fire and forget"_, and it's very useful when you just want to communicate or inform that "something happened." You're not requesting or asking for anything, thus you don't need a response.  
 
 Some examples of this can be:
 * A user just signed up.
@@ -24,7 +24,7 @@ Along with the event, you may also want to send _extra information_. For instanc
 
 This extra information is often referred to as the _event payload_ or _message payload_.
 
-An Event-Driven Architecture (EDA) uses events to trigger and communicate between services and is common in modern applications built with microservices. An event is a change in state, or an update, like adding a shopping item in a cart on an e-commerce website.
+An Event-Driven Architecture (EDA) uses events to trigger and communicate between services and is common in modern applications built with microservices. An event is a state change, or an update, like adding a shopping item to a cart on an e-commerce website.
 
 ## Core concepts
 
@@ -40,13 +40,13 @@ A message broker (or _"broker"_) is a piece of infrastructure in charge of recei
 
 A publisher (a.k.a. _producer_) is an application that sends messages to the _broker_.
 
-A subscriber (a.k.a. _consumer_) is an application that connects to the _broker_, manifests an interest in a certain type of messages, and leaves the connection open so the _broker_ can push messages to them.
+A subscriber (a.k.a. _consumer_) is an application that connects to the _broker_, manifests an interest in a certain type of message, and leaves the connection open so the _broker_ can push messages to them.
 
 ### Message
 
-A message is a piece of information that is sent by publishers to the broker, and received by all interested subscribers. Messages can contain anything, and are frequently catalogued as _events_ and _commands_. As you saw above, _events_ communicate a fact that occurred. On the other hand, _commands_ are very similar to _requests_ in REST APIs. They instruct the subscribers to "do this."
+A message is a piece of information that is sent by publishers to the broker, and received by all interested subscribers. Messages can contain anything and are frequently cataloged as _events_ and _commands_. As you saw above, _events_ communicate a fact that occurred. On the other hand, _commands_ are very similar to _requests_ in REST APIs. They instruct the subscribers to "do this."
 
-**To be precise, _events_ and _commands_ share the same structure, but differ conceptually.**
+**To be precise, _events_ and _commands_ share the same structure but differ conceptually.**
 
 ### Channels
 
@@ -56,7 +56,7 @@ A channel is usually assigned a name or identifier (e.g., `user_signed_up`) and
 
 ## Why "event-driven" and not "message-driven"?
 
-You will find both used interchangeably, although they are not exactly the same. You will even find _"message-based"_ and _"event-based"_. In practice, chances are they all refer to the same thing.
+You will find both used interchangeably, although they are not the same. You will even find _"message-based"_ and _"event-based"_. In practice, chances are they all refer to the same thing.
 
 Theoretically, _"message-driven"_ is the most generic term -meaning you may use events and commands- while _event-driven_ means that it's purely about events.
 

scripts/build-meetings.js

@@ -18,7 +18,7 @@ async function buildMeetings() {
       Date.parse(currentTime) - 100 * 24 * 60 * 60 * 1000
     ).toISOString();
     const timeMax = new Date(
-      Date.parse(currentTime) + 8 * 24 * 60 * 60 * 1000
+      Date.parse(currentTime) + 30 * 24 * 60 * 60 * 1000
     ).toISOString();
     const eventsList = await calendar.events.list({
       calendarId:  process.env.CALENDAR_ID,