docs: add Nikita Pastukhov to Ambassadors list

[Lancetnik]

Hello there! I am Nikita and I am the core maintainer of FastStream.
This is a Python framework for asynchronous services development (like HTTP frameworks, but for MQ).
The main idea of it - simple API and powerful featurs. As an example - FastStream generates AsyncAPI schema automatically based on your service code:

from faststream import FastStream
from faststream.kafka import KafkaBroker

broker = KafkaBroker("localhost:9092")
app = FastStream(broker)

@broker.subscriber("input_data")
@broker.publisher("output_data")
async def on_input_data(user: str, user_id: int) -> str:
    return f"User: {user_id} - {user} registered"

Genereates the following schema representation

FastStream is built for real-time, high-performance data processing, which is crucial for event-driven architectures like those defined by AsyncAPI. It helps developers create scalable, low-latency systems, aligning with AsyncAPI’s goal of supporting asynchronous, real-time communication. Also, FastStreams introduces ordinary developers to the AsyncAPI and they are happy to use it. The tool is production-ready and motivates people to use AsyncAPI in the real-world services.

All our (FastStream) users are AsyncAPI users as well. According my questionnaire 41% FastStream users choose it due native AsyncAPI support. And 35% users really use autogenerated AsyncAPI schemas on production.

We released FastStream just last year, but currently it is #2 porject by #asyncapi topic on GitHub (right after the spec itself) and have more that 1 million installations - https://github.com/topics/asyncapi

All my public speaches and articles are target on FastStream (and AsyncAPI accordingly) promotion. Also, the tool we created stimulates other people to talk about AsyncAPI: last EuroPython speach about FastStream and AsyncAPI as an example.

So I think, my contributions making me a strong candidate for AsyncAPI Ambassador program.

I would like to be an AsyncAPI Ambassador in Russia to have a some kind of "official" position related to tool I promote. Also I wish to use your merch at all my public conference talks 😄 Also, it is a good oportunity to show, that OpenSource is still out of policy (I am also suffering because of the current situation in the world).

Anyway, thank you for your amazing initiative! If you have any python developers would like to improve FastStream and AsyncAPI integration - our team is open for contributions, we have a lot of AsyncAPI features to support.

[draincoder]

Nikita is an excellent candidate! I, like many other guys, learned about such a wonderful thing as AsyncAPI thanks to the appearance of FastStream and Nikita's speeches at major conferences.

[KrySeyt]

+1. I only learned about AsyncAPI and started getting into it because I was contributing to FastStream

[derberg]

Hey @Lancetnik, sorry for the delay, but an AsyncAPI Conference recently kept us busy.

Please have a look at https://github.com/asyncapi/community/blob/master/AMBASSADOR_ORGANIZATION.md#ambassador-requirements. As far as I can see in your PR, you have only 2 contributions that count as Ambassador contributions. I respect the work you folks do with FastStream, but at the moment we do not recognize tooling development as "ambassador contribution" because it is not that easy to count (basically which tool maintainer should be accounted for such contribution) and we would have to do some research first, among other popular tools, like Springwolf or Event Catalog. For now we recognize if creators or someone else promotes their tools and AsyncAPI at the same time at the conference or through articles.

Anyway, this one is easy to fix. Requirements are easy to fulfill, you just need more contributions.

This is one thing, another thing is:

I would like to be an AsyncAPI Ambassador in Russia to have a some kind of "official" position related to tool I promote. Also I wish to use your merch at all my public conference talks 😄 Also, it is a good oportunity to show, that OpenSource is still out of policy (I am also suffering because of the current situation in the world).

For the sake of maintaining a constructive discussion, I’ll refrain from commenting on the subject of suffering.

As for AsyncAPI, the intellectual property and trademark were donated to the Linux Foundation a few years ago. It is currently registered under LF Projects in the United States (Delaware). Given this, I will need to consult with the Linux Foundation to understand the legal and procedural implications of such a request.

This is the first time someone based in Russia has expressed interest in taking on a representative role within the community. To be clear, this isn’t about nationality (our code of conduct is pretty clear, we do not discriminate because of someone's nationality) but the logistical and legal considerations related to your location. I just want to highlight that processing this request may take some time while we clarify the Linux Foundation’s stance and requirements.

---

Please let us know if you plan to fulfill the missing requirements. We prefer to avoid long-lasting PRs, so my strong suggestion would be you close this PR and open a new one once ready.

I will reach out to Linux Foundation, no matter what we do with this particuler PR, so we can update our docs accordingly.

[Lancetnik]

Thank you for the answer! It is totally constructive and I am agree with each position. Moreover, I expected smth like that.

Anyway, I have some comments

Anyway, this one is easy to fix. Requirements are easy to fulfill, you just need more contributions.

Yeah, I knew about formal requirements to be an ambassador, but some contributions can't be measured. I created FastStream and now this is the biggest tool in AsyncAPI ecosystem as I can see, promoting the specification by itself. Anyway, each my speeches and article about FastStream makes accent on AsyncAPI specification and documentation importance for business. Unfortunately, most of them in Russian, so I didn't attached them to the Issue. But, indeed, I can promote more contributions to AsyncAPI itself, it's not a big deal.

This is the first time someone based in Russia has expressed interest in taking on a representative role within the community.

Russia has a strong technical community, promoting a lot of tools and specialist to the world IT. I thing, AsyncAPI presence in the region makes it much stronger. Also, I see the raising day by day interest to AsyncAPI in the our community, so it will be helpful to have some kind of official member in the region. Moreover, I am already actively promoting AsyncAPI 😄

To be clear, this isn’t about nationality (our code of conduct is pretty clear, we do not discriminate because of someone's nationality) but the logistical and legal considerations related to your location

I hope, it shouldn't be a problem. I already collaborating with the Airt company, that bases in USA as well. Anyway, should I just wait the the LF answer ot you or make a request by myself?

Anyway, thank you for your awesome initiative! I am really enjoying working and promoting it. And thank you for your attention and detail answer.

[derberg]

Thanks for your openness and understanding 🙏🏼

Yeah, I knew about formal requirements to be an ambassador, but some contributions can't be measured. I created FastStream and now this is the biggest tool in AsyncAPI ecosystem as I can see, promoting the specification by itself. Anyway, each my speeches and article about FastStream makes accent on AsyncAPI specification and documentation importance for business. Unfortunately, most of them in Russian, so I didn't attached them to the Issue. But, indeed, I can promote more contributions to AsyncAPI itself, it's not a big deal.

I'm not questioning FastStream popularity. I'm also not saying no to such a new type of contribution. It's just that it doesn't exist, and if we want to add it, it ain't gonna be done as part of this PR. There must be a separate discussion. @thulieblack is at the moment the Ambassador Program lead that can make the discussion more visible and drive it.

My personal opinion is that we do not need such new type as I have a feeling that if the tool is popular, it grows ambassadors naturally:

• Springwolf has a strong support from Raphael De Lio that became ambassador mainly because he strongly promotes AsyncAPI and Springwolf at the same time
• Event Catalog created by David Boyne is huge, brings many people to AsyncAPI - but also because he is posting lots of articles about it, and also talks at conferences (btw @thulieblack I know David left AWS to work full time on Event Catalog, might make sense to ask if he is interested to be Ambassador, he produces lots of content, and even his colleagues from AWS recently presented AsyncAPI to huge community at re:Invent)

The same happens to you. You are not just a maintainer. As I understand, you actively promote and educate, just like the folks I mentioned above.

I hope you know what I'm trying to explain.

Also, I see the raising day by day interest to AsyncAPI in the our community, so it will be helpful to have some kind of official member in the region

I saw it also in Google Analytics last time I checked, few months ago.

I hope, it shouldn't be a problem. I already collaborating with the Airt company, that bases in USA as well. Anyway, should I just wait the the LF answer ot you or make a request by myself?

I'm not sure how you could make a request on your own, don't know such a process. I just reached via email my LF contact to understand who should I talk to about this topic.

Anyway, thank you for your awesome initiative! I am really enjoying working and promoting it. And thank you for your attention and detail answer.

🙏🏼