Skip to content

Commit

Permalink
Merge branch 'master' into seo-guide
Browse files Browse the repository at this point in the history
  • Loading branch information
CBID2 authored Jun 16, 2024
2 parents f3dc224 + dee45e5 commit 7bc89d6
Show file tree
Hide file tree
Showing 9 changed files with 415 additions and 30 deletions.
6 changes: 0 additions & 6 deletions .github/workflows/issues-prs-notifications.yml
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,6 @@ jobs:
name: Notify slack on every new issue
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Convert markdown to slack markdown for issue
uses: asyncapi/.github/.github/actions/slackify-markdown@master
id: issuemarkdown
Expand All @@ -40,8 +38,6 @@ jobs:
name: Notify slack on every new pull request
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Convert markdown to slack markdown for pull request
uses: asyncapi/.github/.github/actions/slackify-markdown@master
id: prmarkdown
Expand All @@ -60,8 +56,6 @@ jobs:
name: Notify slack on every new pull request
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Convert markdown to slack markdown for pull request
uses: asyncapi/.github/.github/actions/slackify-markdown@master
id: discussionmarkdown
Expand Down
4 changes: 4 additions & 0 deletions .github/workflows/slack/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,10 @@ Three main resources are created using the slack integration:
- Use of bot token of the format `xoxo-<your-slack-token>` is not supported for creating user groups.
- The user group should be unique across the workspace (i.e., no channel, user, or user group should have the same handle).
- Please [import](#importing-existing-resources) the user groups to terraform state if they already exist in the workspace, as they **cannot be deleted** in Slack 😢.
- **You have to invite the bot to all managed channels to make it work.**
> [!WARNING]
> **Creation of multitudes of groups leads to a lot of API calls and can lead to rate limiting. Please be cautious while creating groups, otherwise you will get `Error: couldn't get usergroups: slack rate limit exceeded, retry after 30s`**. Related issue (not fixed even thought it is closed): https://github.com/pablovarela/terraform-provider-slack/issues/64
> [!IMPORTANT]
> The terraform state will overwrite any description, name, or topic change. It is better to manage the changes in the YAML files and then apply them. However, the terraform state will not affect bookmarks, pinned items, etc.
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/slack/groups/groups.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@

- name: "Studio"
handle: "studio"
description: "To notify all regular Studio contributors at once. If you don't contribute regularly but want to get notified too, please open a PR to get added."
description: "To notify all regular Studio contributors at once, please open PR to get added"
users:
- "U01RWDD69PZ"
- "U0572R8J927"
Expand Down
87 changes: 64 additions & 23 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -1,46 +1,87 @@
# Contributor Covenant Code of Conduct
# AsyncAPI Code of Conduct

## Our Pledge
## Introduction
Welcome to our community! We are a diverse group of individuals united by our passion for open source and commitment to inclusivity.

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.
Our community promotes and supports inclusivity, welcoming individuals from all backgrounds and experiences. We believe that diversity is our strength, and we actively seek participation from those who enhance it.

## Our Standards
Our Code of Conduct governs how we behave publicly or privately when representing the project. It ensures that diverse groups collaborate for mutual advantage and enjoyment and challenges prejudice that could jeopardize anyone's participation in the project.

We expect everyone in our community to treat each other with kindness, empathy, and respect. We believe fostering a welcoming and respectful environment can create a positive and successful community.

## Our Pledge

Examples of behavior that contributes to creating a positive environment include:
As members, contributors, and admins of our community, we pledge to ensure that every individual is treated with respect and dignity. We pledge to create a safe, inclusive, and welcoming environment that is free from any form of harassment or discrimination regardless of differences in age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
We pledge to encourage a diverse, healthy community that celebrates individuality and promotes equality. We will act and interact in ways that promote openness, empathy, understanding, and acceptance of everyone's unique perspectives and experiences.

Examples of unacceptable behavior by participants include:
## Our Standards

- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
### Examples of behavior that contributes to a positive environment for our community include:

## Our Responsibilities
- Using welcoming and inclusive language.
- Being respectful of differing viewpoints and experiences.
- Gracefully accepting constructive criticism.
- Focusing on what is best for the community.
- Showing empathy towards other community members.

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.
### Examples of unacceptable behavior include:

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.
- The use of sexualized language or imagery and unwelcome sexual attention or advances.
- Trolling, insulting/derogatory comments, and personal or political attacks.
- Public or private harassment.
- Publishing others' private information, such as a physical or electronic address, without explicit permission.
- Publishing content or comments that promote illegal activities.
- Violence, threats of violence, or violent language.
- Other conduct that could reasonably be considered inappropriate in a professional setting.

## Scope

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.

## Enforce Responsibilities

The Code of Conduct Committee (CoC Committee) responds to, investigates, and resolves AsyncAPI Incidents. The Committee is responsible for clarifying the standards of acceptable behavior and taking appropriate and fair corrective action in response to unacceptable behavior.

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).

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. 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.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [email protected]. All complaints will be reviewed and investigated promptly and fairly.

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.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.

## Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

### 2. Warning
Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

### 3. Temporary Ban
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

### 4. Permanent Ban
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [http://contributor-covenant.org/version/2/1][version].

Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
[version]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/inclusion
39 changes: 39 additions & 0 deletions WORKING_GROUPS.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,39 @@ working_groups:
# - The AsyncAPI community grows sustainably.
# 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: maintainers_growth_wg, without @asyncapi/ prefix.

- name: Marketing
description: 'The group is dedicated to leveraging marketing strategies to achieve two key objectives: promoting AsyncAPI adoption and highlighting community achievements. By strategically showcasing AsyncAPI capabilities and celebrating community successes, the group drives both user growth and community engagement. It shares a vision of close collaboration between AsyncAPI community and sponsors.'
chairpersons:
- name: Oluwabamikemi Kayode
github: iambami
slack: U070DE02VQX
members:
- name: Lukasz Gornicki
github: derberg
slack: UD698Q5LM
- name: Aishat Muibudeen
github: Mayaleeeee
slack: U03CNHGEUR1
- name: Thulisile Sibanda
github: thulieblack
slack: U03CNJPMT7C
- name: Christophe Dujarric
github: ChristopheDujarric
slack: U048TMNQ1M0
- name: Georgie from Gravitee.io
github: Georgie-Gravitee
slack: U043BE3QUS2
slack:
channel:
handle: wg-marketing
topic: Tasks board https://github.com/orgs/asyncapi/projects/46
group:
handle: marketing-wg
name: Marketing Working Group
roadmap_url: https://github.com/orgs/asyncapi/projects/46
github_team: marketing_wg

- name: Essential Building Blocks
description: The goal of the Essential Building Blocks Working Group is to provide fundamental building blocks that enable a similar developer experience across languages.
chairpersons:
Expand Down Expand Up @@ -60,6 +93,7 @@ working_groups:
github_team: essential_building_blocks_wg
objectives:
- https://github.com/orgs/asyncapi/projects/44

- name: Developer Experience
description: The goal of this group is to empower AsyncAPI user journey trough intuitive onboarding, tools, and a frictionless experience.
chairpersons:
Expand Down Expand Up @@ -91,6 +125,9 @@ working_groups:
- name: Fran Méndez
github: fmvilas
slack: U34F2JRRS
- name: Aayush Saini
github: AayushSaini101
slack: U04RN9LRV97
slack:
channel:
handle: wg-developer-experience
Expand All @@ -102,6 +139,7 @@ working_groups:
objectives:
- https://github.com/users/Amzani/projects/12/views/1
github_team: developer_experience_wg

- name: Maintainers Growth
description: The Maintainers Growth Working Group aims to help grow the number of maintainers at AsyncAPI.
chairpersons:
Expand Down Expand Up @@ -132,6 +170,7 @@ working_groups:
handle: maintainers-growth-wg
description: Maintainers Growth Working Group
github_team: maintainers_growth_wg

- name: Conference Coordination
description: The goal of the group is to plan, manage, and create a seamless way to enhance the conference experience.
chairpersons:
Expand Down
Loading

0 comments on commit 7bc89d6

Please sign in to comment.