Proposal: Improve repository sustainability

[princerajpoot20]

As part of the 2026 community goals (more details here: asyncapi/community#3495), we conducted an audit of all repositories. A summary of the findings can be found here: asyncapi/community#3495 (comment).

This repository (brand) has only one active maintainer, and more importantly, only one maintainer in total, whether active or inactive. This means the repository is not sustainable in its current state, as everything depends on a single person.

Hence, there are a couple of next steps we could consider:

• Increase the number of maintainers for this repository to make it sustainable.
• Merge this repository into the community repository and eventually increase the number of maintainers there.

In my humble opinion, I would prefer the second option: merging it into the community repository. It is the repository where all the community guidelines and official documentation are maintained. Therefore, having the brand-related assets there also makes sense, as it provides a single source of truth.

This will also make it easier to track changes and improve the visibility of the brand guidelines and assets under the community repository umbrella.

I am opening this issue to gather feedback from the code owners of this repository regarding this proposal.

Tagging all code owners for their feedback:
@Mayaleeeee

@thulie @derberg, could you also share your thoughts on this?

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[thulieblack]

I would love to have the repo as a standalone but yes we need more maintainers here.

I would suggest we hear from @Mayaleeeee what she thinks

[Mayaleeeee]

Thanks for bringing this up, @princerajpoot20!

I prefer keeping the brand as a standalone repository. Brand assets, design systems, and guidelines require a specific focus that can easily get lost or cluttered if merged into a massive, general-purpose repository like a community.

That being said, I completely agree that we need more hands on deck to ensure long-term sustainability. I am very open to onboarding and mentoring new maintainers who want to contribute specifically to AsyncAPI's design and brand layer. Let's focus our efforts on an open call for co-maintainers instead! @thulieblack