Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creation of the [email protected] email #1235

Open
smoya opened this issue Jun 5, 2024 · 3 comments
Open

Creation of the [email protected] email #1235

smoya opened this issue Jun 5, 2024 · 3 comments
Assignees

Comments

@smoya
Copy link
Member

smoya commented Jun 5, 2024

To report a violation in writing, please email [email protected], which goes to all primary (not alternate) members of the AsyncAPI Code of Conduct Committee (CoC Committee).

Source: https:/asyncapi/community/blob/master/code_of_conduct/coc-incident-resolution-procedures.md#submit-in-writing

The Code Of Conduct Committee needs the [email protected] email account so people can report violations of the CoC via email.
That email inbox should redirect emails to all primary/full members of the CoC Committee:

Additionally, the credentials should be shared with those, so we can reply emails via that account instead of each individual.

You can ask emails via DM.

@derberg I believe you are the one who have permission to do this.

@smoya smoya assigned derberg and thulieblack and unassigned derberg Jun 5, 2024
@derberg
Copy link
Member

derberg commented Jun 12, 2024

in contact with LF

Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Oct 11, 2024
@thulieblack
Copy link
Member

Was this resolved right, we can close cc @derberg @smoya

@github-actions github-actions bot removed the stale label Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants