Skip to content

Commit e30a94b

Browse files
authored
Merge branch 'master' into new_blog
2 parents af79e46 + 0dafc8b commit e30a94b

File tree

142 files changed

+5863
-2543
lines changed

Some content is hidden

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

142 files changed

+5863
-2543
lines changed

.github/workflows/automerge-orphans.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,8 @@ jobs:
5252
}
5353
- if: steps.orphans.outputs.found == 'true'
5454
name: Convert markdown to slack markdown
55-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
55+
# This workflow is from our own org repo and safe to reference by 'master'.
56+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
5657
id: issuemarkdown
5758
with:
5859
markdown: "-> [${{steps.orphans.outputs.title}}](${{steps.orphans.outputs.url}})"

.github/workflows/if-nodejs-pr-testing.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ jobs:
1313
runs-on: ${{ matrix.os }}
1414
strategy:
1515
matrix:
16-
os: [ubuntu-latest, macos-13, windows-latest]
16+
os: [ubuntu-latest, macos-latest, windows-latest]
1717
steps:
1818
- if: >
1919
!github.event.pull_request.draft && !(

.github/workflows/issues-prs-notifications.yml

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,8 @@ jobs:
2121
runs-on: ubuntu-latest
2222
steps:
2323
- name: Convert markdown to slack markdown for issue
24-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
24+
# This workflow is from our own org repo and safe to reference by 'master'.
25+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
2526
id: issuemarkdown
2627
env:
2728
ISSUE_TITLE: ${{github.event.issue.title}}
@@ -43,7 +44,8 @@ jobs:
4344
runs-on: ubuntu-latest
4445
steps:
4546
- name: Convert markdown to slack markdown for pull request
46-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
47+
# This workflow is from our own org repo and safe to reference by 'master'.
48+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
4749
id: prmarkdown
4850
env:
4951
PR_TITLE: ${{github.event.pull_request.title}}
@@ -65,7 +67,8 @@ jobs:
6567
runs-on: ubuntu-latest
6668
steps:
6769
- name: Convert markdown to slack markdown for pull request
68-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
70+
# This workflow is from our own org repo and safe to reference by 'master'.
71+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
6972
id: discussionmarkdown
7073
env:
7174
DISCUSSION_TITLE: ${{github.event.discussion.title}}

.github/workflows/notify-tsc-members-mention.yml

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,8 @@ jobs:
4343
# Handling Slack notifications
4444
#########
4545
- name: Convert markdown to slack markdown
46-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
46+
# This workflow is from our own org repo and safe to reference by 'master'.
47+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
4748
id: issuemarkdown
4849
with:
4950
markdown: "[${{github.event.issue.title}}](${{github.event.issue.html_url}}) \n ${{github.event.issue.body}}"
@@ -89,7 +90,8 @@ jobs:
8990
# Handling Slack notifications
9091
#########
9192
- name: Convert markdown to slack markdown
92-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
93+
# This workflow is from our own org repo and safe to reference by 'master'.
94+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
9395
id: prmarkdown
9496
with:
9597
markdown: "[${{github.event.pull_request.title}}](${{github.event.pull_request.html_url}}) \n ${{github.event.pull_request.body}}"
@@ -135,7 +137,8 @@ jobs:
135137
# Handling Slack notifications
136138
#########
137139
- name: Convert markdown to slack markdown
138-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
140+
# This workflow is from our own org repo and safe to reference by 'master'.
141+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
139142
id: discussionmarkdown
140143
with:
141144
markdown: "[${{github.event.discussion.title}}](${{github.event.discussion.html_url}}) \n ${{github.event.discussion.body}}"
@@ -181,7 +184,8 @@ jobs:
181184
# Handling Slack notifications
182185
#########
183186
- name: Convert markdown to slack markdown
184-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
187+
# This workflow is from our own org repo and safe to reference by 'master'.
188+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
185189
id: issuemarkdown
186190
with:
187191
markdown: "[${{github.event.issue.title}}](${{github.event.comment.html_url}}) \n ${{github.event.comment.body}}"
@@ -227,7 +231,8 @@ jobs:
227231
# Handling Slack notifications
228232
#########
229233
- name: Convert markdown to slack markdown
230-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
234+
# This workflow is from our own org repo and safe to reference by 'master'.
235+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
231236
id: prmarkdown
232237
with:
233238
markdown: "[${{github.event.issue.title}}](${{github.event.comment.html_url}}) \n ${{github.event.comment.body}}"
@@ -273,7 +278,8 @@ jobs:
273278
# Handling Slack notifications
274279
#########
275280
- name: Convert markdown to slack markdown
276-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
281+
# This workflow is from our own org repo and safe to reference by 'master'.
282+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
277283
id: discussionmarkdown
278284
with:
279285
markdown: "[${{github.event.discussion.title}}](${{github.event.comment.html_url}}) \n ${{github.event.comment.body}}"

.github/workflows/release-announcements.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,8 @@ jobs:
1717
- name: Checkout repository
1818
uses: actions/checkout@v4
1919
- name: Convert markdown to slack markdown for issue
20-
uses: asyncapi/.github/.github/actions/slackify-markdown@master
20+
# This workflow is from our own org repo and safe to reference by 'master'.
21+
uses: asyncapi/.github/.github/actions/slackify-markdown@master # //NOSONAR
2122
id: markdown
2223
env:
2324
RELEASE_TAG: ${{github.event.release.tag_name}}

.gitignore

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ node_modules
77
out
88
config/posts.json
99
config/case-studies.json
10-
config/adopters.json
10+
config/usecases.json
1111
public/rss.xml
1212
.env.local
1313
yarn.lock

CODEOWNERS

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
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-
* @derberg @akshatnema @anshgoyalevil @sambhavgupta0705 @mayaleeeee @asyncapi-bot-eve
8+
* @derberg @akshatnema @anshgoyalevil @sambhavgupta0705 @princerajpoot20 @mayaleeeee @asyncapi-bot-eve
99

1010
# All .md files
1111
*.md @thulieblack @TRohit20 @asyncapi-bot-eve

CODE_OF_CONDUCT.md

Lines changed: 75 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,46 +1,95 @@
1-
# Contributor Covenant Code of Conduct
1+
2+
# Contributor Covenant 3.0 Code of Conduct
23

34
## Our Pledge
45

5-
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6+
We pledge to make our community welcoming, safe, and equitable for all.
67

7-
## Our Standards
8+
We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
89

9-
Examples of behavior that contributes to creating a positive environment include:
10+
## Encouraged Behaviors
1011

11-
- Using welcoming and inclusive language
12-
- Being respectful of differing viewpoints and experiences
13-
- Gracefully accepting constructive criticism
14-
- Focusing on what is best for the community
15-
- Showing empathy towards other community members
12+
While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
1613

17-
Examples of unacceptable behavior by participants include:
14+
With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
1815

19-
- The use of sexualized language or imagery and unwelcome sexual attention or advances
20-
- Trolling, insulting/derogatory comments, and personal or political attacks
21-
- Public or private harassment
22-
- Publishing others' private information, such as a physical or electronic address, without explicit permission
23-
- Other conduct which could reasonably be considered inappropriate in a professional setting
16+
1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
17+
2. Engaging **kindly and honestly** with others.
18+
3. Respecting **different viewpoints** and experiences.
19+
4. **Taking responsibility** for our actions and contributions.
20+
5. Gracefully giving and accepting **constructive feedback**.
21+
6. Committing to **repairing harm** when it occurs.
22+
7. Behaving in other ways that promote and sustain the **well-being of our community**.
2423

25-
## Our Responsibilities
2624

27-
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
25+
## Restricted Behaviors
2826

29-
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
27+
We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
3028

31-
## Scope
29+
1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
30+
2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
31+
3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
32+
4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
33+
5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
34+
6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
35+
7. Behaving in other ways that **threaten the well-being** of our community.
36+
37+
### Other Restrictions
38+
39+
1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
40+
2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
41+
3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
42+
4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
43+
44+
45+
## Reporting an Issue
46+
47+
Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
48+
49+
When an incident does occur, it is important to report it promptly. To report a possible violation, here are a few simple ways to do it:
50+
51+
- Join our [AsyncAPI Slack](https://asyncapi.com/slack-invite) and share your report in the `#coc` channel.
52+
- Reach out directly to any member of the [Code of Conduct Committee](https://github.com/orgs/asyncapi/teams/code_of_conduct).
53+
- Or, if you’d prefer, just send us an email at **conduct@asyncapi.com**.
3254

33-
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
55+
Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
3456

35-
## Enforcement
3657

37-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at fmvilas@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
58+
## Addressing and Repairing Harm
59+
60+
****
61+
62+
If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
63+
64+
1) Warning
65+
1) Event: A violation involving a single incident or series of incidents.
66+
2) Consequence: A private, written warning from the Community Moderators.
67+
3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
68+
2) Temporarily Limited Activities
69+
1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
70+
2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
71+
3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
72+
3) Temporary Suspension
73+
1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
74+
2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
75+
3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
76+
4) Permanent Ban
77+
1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
78+
2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
79+
3) Repair: There is no possible repair in cases of this severity.
80+
81+
This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
82+
83+
84+
## Scope
85+
86+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
3887

39-
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
4088

4189
## Attribution
4290

43-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
91+
This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
92+
93+
Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
4494

45-
[homepage]: http://contributor-covenant.org
46-
[version]: http://contributor-covenant.org/version/1/4/
95+
For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Please use our issues templates, which provide hints on what information we need
5959

6060
**Please open an issue before starting a Pull Request unless it's a typo or a really obvious error.** Pull requests are the best way to propose changes to the specification. It may be rejected if no issue was created first to discuss the need for a pull request.
6161

62-
Get familiar with our document that explains the [Git workflow](https://github.com/asyncapi/community/blob/master/git-workflow.md) used in our repositories.
62+
Get familiar with our document that explains the [Git workflow](https://github.com/asyncapi/community/blob/master/docs/010-contribution-guidelines/git-workflow.md) used in our repositories.
6363

6464
## Conventional commits
6565

0 commit comments

Comments
 (0)