Merge branch 'master' into code_of_conduct

asyncapi · Mar 13, 2024 · 94a2183 · 94a2183
2 parents 8efd2cb + 022401b
commit 94a2183
Show file tree

Hide file tree

Showing 11 changed files with 215 additions and 4 deletions.
diff --git a/.github/workflows/update-docs-on-docs-commits.yml b/.github/workflows/update-docs-on-docs-commits.yml
@@ -0,0 +1,57 @@
+# This workflow is centrally managed in https://github.com/asyncapi/.github/
+# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
+
+# The given workflow is responsible for generating docs and creating PR with them when there is a commit with docs: prefix
+
+# This workflow will be updated in all repos with the topic get-global-docs-autoupdate
+
+name: 'Update generated parts of documentation on docs: commits'
+
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  docs-gen:
+    name: 'Generate docs and create PR'
+    runs-on: ubuntu-latest
+    # PR should be created within this GH action only if it is a docs: commit
+    # Otherwise it will conflict with release workflow
+    if: startsWith(github.event.commits[0].message, 'docs:')
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v4
+      - name: Check package-lock version
+        uses: asyncapi/.github/.github/actions/get-node-version-from-package-lock@master
+        id: lockversion
+      - name: Use Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: "${{ steps.lockversion.outputs.version }}"
+          cache: 'npm'
+          cache-dependency-path: '**/package-lock.json'
+      - name: Install dependencies
+        run: npm ci
+      - name: Regenerate docs
+        run: npm run generate:assets --if-present
+      - name: Create Pull Request with updated docs
+        uses: peter-evans/create-pull-request@153407881ec5c347639a548ade7d8ad1d6740e38 # uses 5.0.2 https://github.com/peter-evans/create-pull-request/releases/tag/v5.0.2
+        with:
+          token: ${{ secrets.GH_TOKEN }}
+          commit-message: 'chore: update generated docs'
+          committer: asyncapi-bot <[email protected]>
+          author: asyncapi-bot <[email protected]>
+          title: 'chore: update generated docs'
+          body: 'Update of docs that are generated and were forgotten on PR level.'
+          branch: gen-docs-update/${{ github.job }}
+      - name: Report workflow status to Slack
+        if: failure() # Only, on failure, send a message on the 94_bot-failing-ci slack channel
+        uses: 8398a7/action-slack@fbd6aa58ba854a740e11a35d0df80cb5d12101d8 #using https://github.com/8398a7/action-slack/releases/tag/v3.15.1
+        with:
+          status: ${{ job.status }}
+          fields: repo,action,workflow
+          text: 'AsyncAPI docs generation workflow failed'
+          author_name: asyncapi-bot
+        env:
+          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_CI_FAIL_NOTIFY }}     
diff --git a/AMBASSADORS_MEMBERS.json b/AMBASSADORS_MEMBERS.json
@@ -154,6 +154,90 @@
       }
     ]
   },
+  {
+    "name": "Ivan Garcia Sainz-Aja",
+    "github": "ivangsa",
+    "twitter": "ivangsa",
+    "bio": "Java Architect with a deep understanding of Java, Spring-Boot, Spring-Cloud technologies, specializing in Domain-Driven Design (DDD) and Event-Driven Architectures creating Software Easy to Understand. Building ZenWave 360º. ZenWave 360º is a set of tools built on the foundations of Domain Driven Design and API-First principles for Event-Driven Architectures, to help you create software easy to understand. https://www.zenwave360.io/",
+    "linkedin": "ivangarciasainzaja",
+    "company": "SNGULAR",
+    "title": "Java Architect. Speaker. Building ZenWave 360°.",  
+    "img": "https://avatars.githubusercontent.com/u/1246876?v=4",
+    "contributions": [
+      {
+        "type": "iniciative_driver",
+        "title": "AsyncAPI Conference On Tour 2023 - Madrid",
+        "date": {
+          "year": 2023,
+          "month": "October"
+        },
+        "link": "https://www.youtube.com/playlist?list=PLbi1gRlP7pihD-7XYb6c9wcTdkavDzF3_"
+      },
+      {
+        "type": "iniciative_driver",
+        "title": "ZenWave SDK - Code Generator for AsyncAPI with Spring Cloud Streams",
+        "date": {
+          "year": 2024,
+          "month": "2022"
+        },
+        "link": "https://www.zenwave360.io/zenwave-sdk/plugins/asyncapi-spring-cloud-streams3/"
+      },
+      {
+        "type": "article",
+        "title": "API-First with AsyncAPI",
+        "date": {
+          "year": 2023,
+          "month": "March"
+        },
+        "link": "https://www.zenwave360.io/posts/API-First-with-AsyncAPI-And-ZenWave-SDK/"
+      },
+      {
+        "type": "article",
+        "title": "ZenWave AsyncAPI Code Generator",
+        "date": {
+          "year": 2023,
+          "month": "March"
+        },
+        "link": "https://www.zenwave360.io/posts/ZenWave-AsyncAPI-Code-Generator/"
+      },
+      {
+        "type": "article",
+        "title": "Generating AsyncAPI definition files from JDL with ZenWaveSDK",
+        "date": {
+          "year": 2023,
+          "month": "April"
+        },
+        "link": "https://www.zenwave360.io/posts/JHipster-As-IDL-for-AsyncAPIv2/"
+      },
+      {
+        "type": "presentation",
+        "title": "KIT - API-First with AsyncAPI for Event Driven Architectures",
+        "date": {
+          "year": 2023,
+          "month": "May"
+        },
+        "link": "https://www.youtube.com/watch?v=EoWFZfmspFM"
+      },
+      {
+        "type": "presentation",
+        "title": "Practical Event Storming with AsyncAPI v3 and ZenWave SDK",
+        "date": {
+          "year": 2023,
+          "month": "October"
+        },
+        "link": "https://www.youtube.com/watch?v=-uHONzz-a6U"
+      },
+      {
+        "type": "presentation",
+        "title": "Code Generation For Enterprise Integration Patterns w/ AsyncAPI & ZenWave SDK",
+        "date": {
+          "year": 2023,
+          "month": "October"
+        },
+        "link": "https://www.youtube.com/watch?v=gUsoD8RaCuw"
+      }
+    ]
+  },
   {
     "name": "Jesse Menning",
     "github": "jessemenning",

diff --git a/MAINTAINERS.yaml b/MAINTAINERS.yaml
@@ -544,7 +544,6 @@
   isTscMember: true
   repos:
     - modelina
-
 - name: Sambhav Gupta
   github: sambhavgupta0705
   linkedin: sambhavgupta0705
@@ -554,3 +553,10 @@
   isTscMember: true
   repos:
     - website
+- name: Viacheslav Turovskyi
+  github: aeworxet
+  slack: U01G3U01SVC
+  availableForHire: false
+  isTscMember: false
+  repos:
+    - bundler
diff --git a/WORKING_GROUPS.md b/WORKING_GROUPS.md
@@ -0,0 +1,17 @@
+### Definition of a Working Group
+
+A Working Group is a group of people in our community who share a common interest beyond GitHub repositories.
+
+A Working Group must have at least one of its members appointed as its chairperson.
+
+Anyone can create a Working Group. The only prerequisites are to have at least 3 founding members and the approval of the TSC (Technical Steering Committee).
+
+A Working Group should have clearly defined goals that are easily accessible to everyone on the internet, as this helps maintain alignment within the group.
+
+It is recommended that the Working Group has an associated project management tool like [GitHub Projects](https://docs.github.com/en/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project) (or any other project management tool) to outline their roadmap. It's up to the Working Group to decide the structure of the project. E.g., Kanban, Shape Up, TO-DO list, etc.
+
+The group's name, members, goals, and other relevant information must be added to the `WORKING_GROUPS.yaml` file in the `community` repository.
+
+A Working Group has no authority or power over the roadmap of the projects they may impact. It's up to the repositories' maintainers (code owners) to approve or reject the pull requests. Therefore, it's advisable to either have maintainers of the impacted projects in the Working Group or ensure everyone agrees on the roadmap of the different repositories/projects.
+
+Working Groups should be listed on the [AsyncAPI website](https://www.asyncapi.com), along with their description, goals, members, and anything the Working Group wants to include.
diff --git a/WORKING_GROUPS.yaml b/WORKING_GROUPS.yaml
@@ -0,0 +1,14 @@
+# This file contains the list of the currently active working groups.
+#
+# To learn more about working groups, read the WORKING_GROUPS.md file.
+
+working_groups:
+  # - name: Required. The name of the working group.
+  #   description: Required. Describe what this working group is about.
+  #   chairperson: Required. GitHub handle of the chairperson. Example: @Barbanio.
+  #   members: # Required to have at least 2 members who are not the same as the chairperson.
+  #     - @fmvilas # GitHub handle of the member.
+  #   slack_channel: # Required. The name of the Slack channel in the AsyncAPI workspace. Example: community_growth_wg
+  #   okrs_url: https://example.com/xyz # Required. Link to a GitHub project, issue, or any other tool where the Working Group explains their objectives.
+  #   roadmap_url: https://example.com/xyz # Recommended. Link to a GitHub project, issue, or any other tool where the Working Group outlines their roadmap.
+  #   github_team: # Recommended. The GitHub team handle to tag all the working group members at once. Example: @asyncapi/community_growth_wg.
diff --git a/...ode/2024/asyncapi-ideas-page-gsoc-2024.md → ...erofcode/2024/asyncapi-gsoc-ideas-page.md b/...ode/2024/asyncapi-ideas-page-gsoc-2024.md → ...erofcode/2024/asyncapi-gsoc-ideas-page.md
@@ -17,7 +17,7 @@ Improve the [AsyncAPI website](https://github.com/asyncapi/website)'s robustness
 - 🛠️ **Skills:** JavaScript, Next.js, unit testing, and CI/CD practices.
 - 🧩 **Difficulty:** Medium/Hard
 - 👩🏿‍🏫 **Mentor(s):** [@akshatnema](https://github.com/akshatnema), [@anshgoyalevil](https://github.com/anshgoyalevil)
-- ⏳ **Length:** 320 Hours
+- ⏳ **Length:** 350 Hours
 
 ## 3) [Integration Testing Library for Code Generators](https://github.com/asyncapi/generator/issues/752)
 Enhance the [Generator tool](https://github.com/asyncapi/generator) by introducing a feature or creating a new library to simplify integration testing for code generation templates. This solution facilitates the activation of integration tests, ensuring reliability and robustness with our code generators.
@@ -44,7 +44,7 @@ Create a UI Kit for the AsyncAPI website to ensure brand visual consistency and
 - 🛠️ **Skills:** JavaScript, React, Storybook, and TailwindCSS.
 - 🧩 **Difficulty:** Easy/Medium
 - 👩🏿‍🏫 **Mentor(s):** [@acethecreator](https://github.com/acethecreator), [@akshatnema](https://github.com/akshatnema)
-- ⏳ **Length:** 320 Hours
+- ⏳ **Length:** 350 Hours
 
 ## 6) [Dynamic Open Graph Preview for AsyncAPI Studio](https://github.com/asyncapi/studio/issues/224)
 Improve social sharing for [AsyncAPI Studio](https://studio.asyncapi.com/) by implementing a dynamic Open Graph link preview generator. This feature will create context-specific preview images for shared links, incorporating key details like the title, description, and statistics from the shared AsyncAPI document.
@@ -66,7 +66,7 @@ Upgrade [AsyncAPI Studio](https://studio.asyncapi.com/) to support real-time col
 
 ## Contact AsyncAPI Mentors
 - Join [our Slack workspace](https://www.asyncapi.com/slack-invite).  Observe our [Slack etiquette](https://github.com/asyncapi/.github/blob/master/slack-etiquette.md) and [AsyncAPI code of conduct](https://github.com/asyncapi/.github/blob/master/CODE_OF_CONDUCT.md).
-- Join the dedicated Mentorship channel `#mentorships` to meet all other GSoC mentees and mentors.
+- Join the dedicated Mentorship channel `#09_mentorships` to meet all other GSoC mentees and mentors.
 
 ## FAQ
 1. **How active are previous GSoC contributors in AsyncAPI?**

diff --git a/tweets/recurring-discuss-ideas/2024-03-01.tweet b/tweets/recurring-discuss-ideas/2024-03-01.tweet
@@ -0,0 +1,5 @@
+Do you have some nice ideas for #AsyncAPI-related tools? Do you want to validate and share with the AsyncAPI community?
+
+Drop it 👇 and let us have an open discussion 🚀
+
+https://github.com/asyncapi/community/discussions/categories/ideas
diff --git a/tweets/recurring-slack-link/2024-02-17.tweet b/tweets/recurring-slack-link/2024-02-17.tweet
@@ -0,0 +1,7 @@
+✨ Did you know #AsyncAPI is on Slack? ✨ 
+
+Join our Slack workspace to chat with anyone from our Open-Source community! 
+
+🔗 asyncapi.com/slack-invite 
+
+Ask for help and help others too. 💪🏿💪🏽🦾
diff --git a/tweets/recurring-slack-link/2024-02-24.tweet b/tweets/recurring-slack-link/2024-02-24.tweet
@@ -0,0 +1,7 @@
+✨ Did you know #AsyncAPI is on Slack? ✨ 
+
+Join our Slack workspace to chat with anyone from our Open-Source community! 
+
+🔗 asyncapi.com/slack-invite 
+
+Ask for help and help others too. 💪🏿💪🏽🦾
diff --git a/tweets/recurring-slack-link/2024-03-02.tweet b/tweets/recurring-slack-link/2024-03-02.tweet
@@ -0,0 +1,7 @@
+✨ Did you know #AsyncAPI is on Slack? ✨ 
+
+Join our Slack workspace to chat with anyone from our Open-Source community! 
+
+🔗 asyncapi.com/slack-invite 
+
+Ask for help and help others too. 💪🏿💪🏽🦾
diff --git a/tweets/recurring-slack-link/2024-03-09.tweet b/tweets/recurring-slack-link/2024-03-09.tweet
@@ -0,0 +1,7 @@
+✨ Did you know #AsyncAPI is on Slack? ✨ 
+
+Join our Slack workspace to chat with anyone from our Open-Source community! 
+
+🔗 asyncapi.com/slack-invite 
+
+Ask for help and help others too. 💪🏿💪🏽🦾