Add section on the website for the AsyncAPI Ambassador Program

[Barbanio]

Reason/Context

As you know, we are working on the AsyncAPI Ambassador Program. We need to create a new page on the website for this, something similar to the TSC page. This space will house all the clear and concise information about the program:

• how to join the program
• the requirements to become an ambassador
• information about the ambassadors (name, picture, company of project, and social networks links)
• and an agenda or calendar with the planned activities of the ambassadors.

@mcturco could you help us with the design of this space? We need people to work on this, anybody in?

[quetzalliwrites]

@Barbanio Would you like me to help with writing the copy for the page? Do you have something specific in mind? ❤️

[Barbanio]

Yes, great! 🎉 I've summarized everything that's been talked about in the Ambassador Program thread.

And from there, we can work if that's okay with you. The core of my idea is something like this:

What is the AsyncAPI Ambassador Program?

The AsyncAPI Ambassador Program aims to bring AsyncAPI closer to the users and potential users of the project. Provide users and community members with the necessary tools and resources:

• To promote cooperation between users and disseminate the necessary tools to any specification user.
• To be engaged with the project in some way, either as a contributor, blogger, speaker, etc.
• To be willing to speak at community events or write technical content, such as blog posts, solving community needs.
• To ensure that with the community’s growth, we also grow a list of people in the community that are welcoming and help spread the knowledge about the project.

How does the program work?

• The ambassador selection process will, as always, be as transparent as possible.
• The model currently in place for adding members to the Technical Steering Committee through PR will be used.
• The TSC or their designees will evaluate applications according to the compliance with the requirements.
• All ambassador information will be added through PR to the list used to show people on the AsyncAPI website.

Requirements to become an AsyncAPI Ambassador:

To be an official AsyncAPI ambassador, there is no more important requirement than having the desire to work and spread the AsyncAPI tools.

• Be in tune with AsyncAPI's mission and values.

• Always respect the code of conduct.

• Be active in your role as an ambassador.

• Guidelines for AsyncAPI Ambassadors The participation will be determined and checked by quarters. Understood as a minimum contribution, one of the following requirements must be met each quarter:

  • One article on asyncapi.com or other domains.

  • One presentation at an event or workshop. Within it, AsyncAPI should appear at the core of the presentation. The presentation would never be used as a disguised marketing tool for other products/projects.

  • Or interactions with the community at the *(still to define)+ level.

    Note: Candidates may accumulate events or items covering subsequent quarters. The time as an ambassador is limited to one year, and it can be renewed.

Benefits of being an ambassador:

• Receiving special swag for Ambassadors.
• Receiving swags for participants of the conference or workshops.
• Free entry to AsyncAPI conferences.
• Community-wide recognition.
• All our respects for your contribution!

Are you interested in becoming an official AsyncAPI Ambassador?

Get on board and become an ambassador! APPLY NOW

---

Do you want to work on this basis, or would you prefer to start from scratch? As always, thank you very much for your willingness. ✨

[quetzalliwrites]

@Barbanio, awesome! I am very happy to help this great cause, plus I love working with you 😜🤗💜

I will totally start working from this content that you already created and started.

Is there already a new page created for this? We are still waiting for development work right? I just want to make sure I know where I start writing the draft of this… Do you have any specific instructions for me?

[kaf-lamed-beyt]

Hi @Barbanio I'd love to work on the implementation of this design if it is available

CC: @alequetzalli

[darp99]

I would like to work on this

[starlightknown]

I'd like to work on it too.

[mcturco]

Hey @alequetzalli @Barbanio! Sorry it took me so long to jump into this issue haha. I can definitely help lay out a design for this page if you guys want to finalize the content that needs to be added to this new page first? I think that will make it easier for me to make sure I am using the right layout for the information. Thanks!! 😄

[derberg]

first of all, I want to say I'm writing this comment for the 2nd time, not in browser but VScode because the first time, when I was almost ready, my laptop restarted and I lot the comment... almost cried, then tried to kill my laptop, then almost cried again, but yeah, anyway...

The best is if someone who can contribute code starts first with some lorem ipsum text to also enable others that want to help and contribute docs to it.

It is going to basically be a copy of https://www.asyncapi.com/community/tsc, and the differences are:

• URL should be https://www.asyncapi.com/community/ambassadors
• new headers for 3 columns will be: Who is an ambassador?, How to become an ambassador, What are the benefits of being an ambassador
• new columns content should be a few-paragraph-long excerpt of what is already written here by Barbanio -> https://github.com/asyncapi/website/issues/635#issuecomment-1077556815
• Become a member! box should become Become an ambassador! and be a clickable element that will take the user to the FAQ page that Barbanio is working on (will be as a markdown file in the community repo)
• list of members should not be taken from https://github.com/asyncapi/website/blob/master/config/TSC_MEMBERS.json but from the new https://github.com/asyncapi/website/blob/master/config/AMBASSADORS.json
• the original list will be stored in the community repo as it is with TSC https://github.com/asyncapi/community/blob/master/TSC_MEMBERS.json
• this workflow https://github.com/asyncapi/community/blob/master/.github/workflows/update-website.yml needs contribution, to also support the update of the Ambassadors list on the website (as it is with TSC now)
• we will need the same schema validation as in https://github.com/asyncapi/community/blob/master/.github/workflows/validate-tsc-members.yml#L11 and a schema for the Ambassadors list like https://github.com/asyncapi/community/blob/master/.github/workflows/tsc_members_validator/schema.json
• the difference between TSC and Ambassadors if it comes to schema -> https://github.com/asyncapi/community/blob/master/.github/workflows/tsc_members_validator/schema.json is only repos field. Instead of listing repos that someone maintains, as it is on TSC, we need to list the contributions required for an Ambassador. So instead of repo name, we should have contributions array, a list of elements with 3 properties, title (basically display name for the link that will be in the UI), url (that will be a link to presentation or article), type (to specify if it is article or presentation)
• list of members in the UI will be completely the same, except for Maintainer of: {REPO_NAME}. Instead, it should be Contributions: and we should show data taken from AMBASSADORS.json from new contributions property

tl;dr I counted 5 different contributions

• website repo, code for now ambassadors view
• website repo, descriptions contribution, to the same PR as code
• community repo, faq about ambassador - Barbanio works on it, as we need to get on there a final approval from TSC, if they agree with the initial shape of the program
• community repo, contribution to the workflow that updates file from community to website repo
• community repo, can be a separate contribution of new workflow for Ambassadors file validation - in case more people want to engage here

None of these need to wait for each other. Let's be agile and work on mocks where the real content is not yet provided :muscle:

I'm happy to hop on a call with anyone who needs some technical help, more explanation, etc.

Feel free to ask if something that I wrote doesn't make sense

[Barbanio]

Thanks @derberg for explaining so well and in detail how to contribute 🙌

[starlightknown]

progress!

[github-actions[bot]]

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

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 :heart:

[github-actions[bot]]

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

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 :heart: