Skip to content

Commit ce330dc

Browse files
authored
Merge branch 'master' into aboutguide
2 parents dd2551b + 414bfde commit ce330dc

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

45 files changed

+833
-983
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ jobs:
3030
meeting_desc: ${{ github.event.inputs.desc }}
3131
meeting_banner: ${{ github.event.inputs.meeting_banner }}
3232
host: lpgornicki@gmail.com
33-
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"
33+
alternative_host: "muibudeenaishat@gmail.com,devlopergene@gmail.com,sibanda.thulie@gmail.com,alejandra.olvera.novack@gmail.com,samir.amzani@gmail.com,oluwabamikemi@gmail.com"
3434
issue_template_path: .github/workflows/create-event-helpers/issues_templates/ad-hoc.md
3535
create_zoom: true
3636
secrets:

.github/workflows/slack-integration.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,11 @@ jobs:
1414
steps:
1515
- name: Checkout
1616
uses: actions/checkout@v4
17+
- name: Install terraform
18+
uses: hashicorp/setup-terraform@v3
19+
with:
20+
terraform_version: "^1.3.7"
21+
terraform_wrapper: false
1722
- name: Deploy changes to Slack
1823
run: |
1924
cd .github/workflows/slack
Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
name: Update latest Community documentation in the website
2+
3+
on:
4+
workflow_dispatch:
5+
push:
6+
branches:
7+
- 'master'
8+
paths:
9+
- 'docs/*.md'
10+
11+
jobs:
12+
Make-PR:
13+
name: Make PR on website repository with updated latest Community documentation
14+
runs-on: ubuntu-latest
15+
env:
16+
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
17+
steps:
18+
- name: Checkout Current repository
19+
uses: actions/checkout@v4
20+
with:
21+
path: community
22+
- name: Checkout Another repository
23+
uses: actions/checkout@v4
24+
with:
25+
repository: asyncapi/website
26+
path: website
27+
token: ${{ env.GITHUB_TOKEN }}
28+
- name: Config git
29+
run: |
30+
git config --global user.name asyncapi-bot
31+
git config --global user.email info@asyncapi.io
32+
- name: Create branch
33+
working-directory: ./website
34+
run: |
35+
git checkout -b update-community-docs-${{ github.sha }}
36+
- name: Update edit-page-config.json
37+
uses: actions/github-script@v4
38+
with:
39+
script: |
40+
const fs = require('fs').promises;
41+
const configPath = './website/config/edit-page-config.json';
42+
const configData = require(configPath);
43+
const docsDir = 'community/docs';
44+
45+
async function readDirectories(dirPath) {
46+
const entries = await fs.readdir(dirPath, { withFileTypes: true });
47+
const subdirectories = entries.filter(entry => entry.isDirectory()).map(entry => entry.name);
48+
return subdirectories;
49+
}
50+
51+
async function updateConfigData() {
52+
const subfolders = await readDirectories(docsDir);
53+
54+
for (const subfolder of subfolders) {
55+
const checkSlug = `community/${subfolder}`;
56+
const slug = {
57+
"value": checkSlug,
58+
"href": `https://github.com/asyncapi/community/tree/master/docs/${subfolder}`
59+
};
60+
61+
const entryExists = configData.some(entry => entry.value === checkSlug);
62+
if (!entryExists) {
63+
configData.push(slug);
64+
}
65+
}
66+
67+
await fs.writeFile(configPath, JSON.stringify(configData, null, 2));
68+
}
69+
updateConfigData();
70+
71+
- name: Copy community folder from Current Repo to Another
72+
working-directory: ./website
73+
run: |
74+
find "./markdown/docs/community" -mindepth 1 -maxdepth 1 -type d -exec rm -rf {} +
75+
rm ../community/docs/README.md
76+
mv ../community/docs/* ./markdown/docs/community/
77+
- name: Commit and push
78+
working-directory: ./website
79+
run: |
80+
git add .
81+
git commit -m "docs(community): update latest community docs"
82+
git push https://${{ env.GITHUB_TOKEN }}@github.com/asyncapi/website
83+
- name: Create PR
84+
working-directory: ./website
85+
run: |
86+
gh pr create --title "docs(community): update latest community documentation" --body "Updated community documentation is available and this PR introduces update to community folder on the website" --head "update-community-docs-${{ github.sha }}"

AMBASSADORS_MEMBERS.json

Lines changed: 58 additions & 164 deletions
Original file line numberDiff line numberDiff line change
@@ -287,72 +287,6 @@
287287
}
288288
]
289289
},
290-
{
291-
"name": "Jesse Menning",
292-
"github": "jessemenning",
293-
"twitter": "JesseMenning",
294-
"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.",
295-
"linkedin": "jesse-menning",
296-
"company": "Solace",
297-
"title": "Architect, Office of the CTO at Solace",
298-
"img": "https://avatars.githubusercontent.com/u/62108913?v=4",
299-
"contributions": [
300-
{
301-
"type": "article",
302-
"title": "AsyncAPI 2.3 Adds Solace Bindings to Unlock Full Power of PubSub+",
303-
"date": {
304-
"year": 2022,
305-
"month": "January"
306-
},
307-
"link": "https://solace.com/blog/asyncapi-adds-solace-bindings/"
308-
},
309-
{
310-
"type": "article",
311-
"title": "Align Production Reality and Event Documentation with the AsyncAPI Discovery Tool",
312-
"date": {
313-
"year": 2021,
314-
"month": "November"
315-
},
316-
"link": "https://solace.com/blog/asyncapi-discovery-tool/"
317-
},
318-
{
319-
"type": "article",
320-
"title": "AsyncAPI vs. OpenAPI: Answers to Your Burning Questions About the Two Leading API Specs",
321-
"date": {
322-
"year": 2021,
323-
"month": "June"
324-
},
325-
"link": "https://solace.com/blog/asyncapi-vs-openapi/"
326-
},
327-
{
328-
"type": "article",
329-
"title": "AsyncAPI, CloudEvents, OpenTelemetry: Which Event-Driven Specs Should Your DevOps Include?",
330-
"date": {
331-
"year": 2021,
332-
"month": "March"
333-
},
334-
"link": "https://solace.com/blog/asyncapi-cloudevents-opentelemetry-event-driven-specs-devops/"
335-
},
336-
{
337-
"type": "presentation",
338-
"title": "Future of AsyncAPI, Panel discussion, AsyncAPI Conference",
339-
"date": {
340-
"year": 2021,
341-
"month": "November"
342-
},
343-
"link": "https://www.youtube.com/watch?v=3EeMHhbwyOQ"
344-
},
345-
{
346-
"type": "presentation",
347-
"title": "Thinking Out Loud #4 — with Jesse Menning",
348-
"date": {
349-
"year": 2021,
350-
"month": "August"
351-
},
352-
"link": "https://www.youtube.com/watch?v=eJewFUR-OaM"
353-
}
354-
]
355-
},
356290
{
357291
"name": "Ludovic Dussart",
358292
"github": "M3lkior",
@@ -482,104 +416,6 @@
482416
}
483417
]
484418
},
485-
{
486-
"name": "Mete Atamel",
487-
"github": "meteatamel",
488-
"twitter": "meteatamel",
489-
"country": "🇬🇧",
490-
"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.",
491-
"linkedin": "mete-atamel",
492-
"company": "Google",
493-
"title": "Software Engineer and Developer Advocate at Google",
494-
"img": "https://avatars.githubusercontent.com/u/1177542?v=4",
495-
"contributions": [
496-
{
497-
"type": "article",
498-
"title": "AsyncAPI Basics",
499-
"date": {
500-
"year": 2023,
501-
"month": "May"
502-
},
503-
"link": "https://medium.com/google-cloud/asyncapi-basics-6e6394c9587"
504-
},
505-
{
506-
"type": "article",
507-
"title": "AsyncAPI Tools",
508-
"date": {
509-
"year": 2023,
510-
"month": "May"
511-
},
512-
"link": "https://medium.com/google-cloud/asyncapi-tools-dd59f9236b20"
513-
},
514-
{
515-
"type": "article",
516-
"title": "Understanding AsyncAPI’s publish & subscribe semantics with an example",
517-
"date": {
518-
"year": 2023,
519-
"month": "May"
520-
},
521-
"link": "https://medium.com/google-cloud/understanding-asyncapis-publish-subscribe-semantics-with-an-example-cfa1cc3faef5"
522-
},
523-
{
524-
"type": "article",
525-
"title": "CloudEvents + AsyncAPI",
526-
"date": {
527-
"year": 2023,
528-
"month": "May"
529-
},
530-
"link": "https://medium.com/google-cloud/cloudevents-asyncapi-fa8ef63f28e0"
531-
},
532-
{
533-
"type": "article",
534-
"title": "Google Cloud Pub/Sub + AsyncAPI",
535-
"date": {
536-
"year": 2023,
537-
"month": "May"
538-
},
539-
"link": "https://medium.com/google-cloud/google-cloud-pub-sub-asyncapi-6ea3c1ed3c49"
540-
},
541-
{
542-
"type": "presentation",
543-
"title": "Open standards for building event-driven applications in the cloud",
544-
"date": {
545-
"year": 2023,
546-
"month": "June"
547-
},
548-
"link": "https://www.youtube.com/watch?v=6Igp4DhK_hE"
549-
}
550-
]
551-
},
552-
{
553-
"name": "Raphael De Lio",
554-
"github": "raphaeldelio",
555-
"twitter": "raphaeldelio",
556-
"linkedin": "raphaeldelio",
557-
"country": "🇧🇷",
558-
"bio": "Raphael De Lio is a passionate software engineer who loves to think about solutions and ways to improve anything he touches. He was born in Brazil, lived in Portugal for five years, and now works as a consultant in the Netherlands. In his quest for knowledge, Raphael has always valued learning and sharing insights with others. This pursuit not only led him to Xebia, a place where he found a community of engineers who share his enthusiasm for technology and continuous improvement but also to becoming the co-organizer of the Amsterdam Kotlin MeetUp, where he has been able to enable other speakers to share their knowledge as well.",
559-
"company": "Xebia",
560-
"title": "Software Consultant at Xebia",
561-
"img": "https://avatars.githubusercontent.com/u/25641721?v=4",
562-
"contributions": [
563-
{
564-
"type": "article",
565-
"title": "AsyncAPI — A standard specification for documenting Event-Driven Applications",
566-
"date": {
567-
"year": 2024,
568-
"month": "February"
569-
},
570-
"link": "https://medium.com/@raphaeldelio/asyncapi-a-standard-for-documenting-event-driven-applications-8ff657119036"
571-
},
572-
{
573-
"type": "presentation",
574-
"title": "AsyncAPI & Springwolf - Automated documentation (and more)",
575-
"date": {
576-
"year": 2024,
577-
"month": "May"
578-
},
579-
"link": "https://www.youtube.com/watch?v=DylvTW_ia4Y"
580-
}
581-
]
582-
},
583419
{
584420
"name": "Hari Krishnan",
585421
"github": "harikrishnan83",
@@ -608,6 +444,24 @@
608444
"month": "June"
609445
},
610446
"link": "https://confengine.com/conferences/selenium-conf-2024/proposal/20021/unshackling-your-system-under-test-shift-left-testing-through-dependency-isolation"
447+
},
448+
{
449+
"type": "talk",
450+
"title": "Using API spec as an Executable Contract To Mock and Test Microservices",
451+
"date": {
452+
"year": 2024,
453+
"month": "October"
454+
},
455+
"link": "https://www.youtube.com/watch?v=wiM20HTCerM"
456+
},
457+
{
458+
"type": "talk",
459+
"title": "Contract-Driven Development for Event-Driven Architectures",
460+
"date": {
461+
"year": 2024,
462+
"month": "December"
463+
},
464+
"link": "https://conference.asyncapi.com/venue/Paris"
611465
}
612466
]
613467
},
@@ -686,5 +540,45 @@
686540
"link": "https://www.asyncapi.com/casestudies/hdiglobal"
687541
}
688542
]
543+
},
544+
{
545+
"name": "Lorna Mitchell",
546+
"bio": "Lorna is based in Yorkshire, UK; she is a technology leader and expert in developer experience, passionate about enhancing APIs and developer tools. In her day job as VP of Developer Experience at Redocly, she works on API and documentation tools for technical teams. Lorna is a published author and a regular speaker at conferences, sharing her insights on a variety of tech-related topics. Lorna serves on the OpenUK board, is on the Technical Steering Committee for OpenAPI specification, and maintains open source projects. To learn more about Lorna's activities, visit her website at https://lornajane.net.",
547+
"title": "APIs and Open Source",
548+
"img": "https://lornajane.net/wp-content/uploads/2011/08/IMG_9410-smaller.jpg",
549+
"github": "lornajane",
550+
"twitter": "lornajane",
551+
"linkedin": "lornajane",
552+
"company": "Redocly",
553+
"country": "UK",
554+
"contributions": [
555+
{
556+
"type": "presentation",
557+
"title": "API Governance for AsyncAPI",
558+
"date": {
559+
"year": 2023,
560+
"month": "September"
561+
},
562+
"link": "https://noti.st/lornajane/aOuXwe/api-governance-for-asyncapi"
563+
},
564+
{
565+
"type": "presentation",
566+
"title": "AsyncAPI for Apache Kafka",
567+
"date": {
568+
"year": 2021,
569+
"month": "May"
570+
},
571+
"link": "https://videos.confluent.io/watch/hzjXP8QmLtYRNPukNFUu2D?"
572+
},
573+
{
574+
"type": "article",
575+
"title": "Lint AsyncAPI with Redocly CLI",
576+
"date": {
577+
"year": 2023,
578+
"month": "August"
579+
},
580+
"link": "https://redocly.com/docs/cli/guides/lint-asyncapi"
581+
}
582+
]
689583
}
690584
]

AMBASSADOR_ORGANIZATION.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Examples:
5353

5454
### Become an AsyncAPI Ambassador
5555

56-
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!
56+
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!
5757

5858
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.
5959

CODEOWNERS

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,12 @@
55
# For more details, read the following article on GitHub: https://help.github.com/articles/about-codeowners/.
66

77
# The default owners are automatically added as reviewers when you open a pull request unless different owners are specified in the file.
8-
* @alequetzalli @derberg @asyncapi-bot-eve @thulieblack
8+
* @quetzalliwrites @derberg @asyncapi-bot-eve @thulieblack
99

1010
# All ambassadors related files
1111
AMBASSADOR* @thulieblack
1212

1313
# Code Of Conduct
1414
/code_of_conduct/ @asyncapi/code_of_conduct
15+
CODE_OF_CONDUCT.md @asyncapi/code_of_conduct
16+
slack-etiquette.md @asyncapi/code_of_conduct

CODE_OF_CONDUCT.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,11 @@ The Code of Conduct Committee (CoC Committee) responds to, investigates, and res
4545

4646
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.
4747

48-
For more details, please see the [CoC Committee and Incident Resolution Procedure](https://github.com/asyncapi/community/pull/1013/files).
48+
For more details, please see the [CoC Committee and Incident Resolution Procedure](https://github.com/asyncapi/community/tree/master/code_of_conduct).
4949

5050
## Enforcement
5151

52-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at condcut@asyncapi.io. All complaints will be reviewed and investigated promptly and fairly.
52+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at conduct@asyncapi.io. All complaints will be reviewed and investigated promptly and fairly.
5353

5454
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
5555

0 commit comments

Comments
 (0)