docs: document AsyncAPI Initiative assets and list people that are regularly paid

[derberg]

Resolves: #2013

Summary by CodeRabbit

• Documentation
  • Added a comprehensive "Initiative Inventory" under Governance & Policies consolidating funding/donations, domains, email, GitHub orgs/bots, tools (SonarCloud, CodeCov, etc.), deployments, analytics, package/plugin distribution (TBD), key contributors/roles and budgets, social media, messaging, meetings, video, CRM, accounts/URLs, ownership, usage notes, procurement considerations, and links for future expansion.

[coderabbitai]

Walkthrough

Adds a new markdown document that inventories AsyncAPI governance and policy resources, listing accounts, tools, ownership, budgets, URLs, and usage notes across funding, domains, email, GitHub, deployments, analytics, package/plugin distribution, personnel, social, messaging, meetings, and video. (44 words)

Changes

Cohort / File(s)	Summary of Changes
Docs: Governance inventory docs/020-governance-and-policies/initiative-inventory.md	Added a comprehensive inventory documenting governance- and policy-related resources (payments/donations, domains, email, GitHub orgs/bots, deployments, analytics, package manager notes, plugin channels, staffing/"Amazing Humans", social/messaging, meetings/video), including ownership, budgets, URLs, and TBDs for package managers.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my nose at lists so bright,
I gather accounts from day to night.
Domains, deploys, and budgets too,
A carrot map for all to view.
Hop — the docs are fresh and new. 🥕🐇

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "docs: document AsyncAPI Initiative assets and list people that are regularly paid" concisely and accurately describes the primary change in the PR—adding documentation that inventories initiative assets and lists regularly paid people—so it is specific, relevant, and appropriate for a single-line PR title.
Linked Issues Check	✅ Passed	The PR adds docs/020-governance-and-policies/initiative-inventory.md which catalogs accounts, ownership, budgets, usage notes, and paid contributors, directly addressing the objectives of issue [#2013] to prepare an inventory of AsyncAPI resources and make it part of community docs; a few sections are noted "TBD" (e.g., Package Managers), so while the primary objective is implemented the document may need minor completion and verification.
Out of Scope Changes Check	✅ Passed	The changeset consists of a single new documentation file and does not modify code or other unrelated files, and the content aligns with the linked issue's scope, so there are no apparent out-of-scope changes.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[fmvilas]

Things that come to my mind:

• Zoom
• YouTube (I'm not sure it's part of Google Workspace, most likely not because it's previous to it)
• LinkedIn
• Twitter
• Twitch
• Restream
• Buffer (is there one maybe?)
• Figma

I'm pretty sure there's more but can't think of anything else right now.

[fmvilas]

LGTM 👍

[derberg]

ready for review, feel free to share how should I improve the document. For now I focused on content accuracy not quality. You know, what metadata to add? should some intro be added?

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (16)

docs/020-governance-and-policies/initiative-inventory.md (16)

1-2: Add a clear H1 title, short introduction, and contribution/maintenance notes

This doc starts directly with a second-level heading. Add a title and a short intro that explains scope, who maintains it, and how to request access/changes. This also addresses the author’s question about adding an introduction.

-## Payment/Donations
+# AsyncAPI Initiative assets inventory
+
+This page inventories the services, accounts, domains, and channels used by the AsyncAPI Initiative. It’s intended to help the community and the TSC understand ownership, access, renewals, and related notes.
+
+- Primary maintainer: TSC (with input from service owners listed below)
+- How to request access/changes: open an issue in the community repo and cc the relevant owner(s)
+- Update cadence: update as changes happen; review quarterly
+
+## Payments and donations

If useful, I can also propose a small template (Owner, Backup owner, Billing owner, Renewal, 2FA enforced, Notes) you can apply to each item. Want me to draft it?

---

3-5: Replace bare URLs with proper Markdown links

markdownlint flags MD034 on bare URLs. Converting to Markdown links improves readability and lint compliance.

-- Open Collective and multiple sub-projects: https://opencollective.com/asyncapi
-- Linux Foundation Crowdfunding: https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi
-- GitHub Sponsors: https://github.com/sponsors/asyncapi
+- Open Collective and multiple sub-projects: <https://opencollective.com/asyncapi>
+- Linux Foundation Crowdfunding: <https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi>
+- GitHub Sponsors: <https://github.com/sponsors/asyncapi>

Apply similarly throughout the document where bare URLs appear.

---

7-13: Include asyncapi.io in the Domains section and polish phrasing

The Email section references asyncapi.io as the Google Workspace domain, but it’s missing from Domains. Also, minor grammar polish.

-## Domains
-
-Managed by Linux Foundation
-
-- asyncapi.com
-- asyncapi.org
+## Domains
+
+Managed by the Linux Foundation
+
+- asyncapi.com
+- asyncapi.org
+- asyncapi.io

Please confirm whether asyncapi.io is LF-managed or managed elsewhere and adjust if needed.

---

16-27: Email: improve clarity, grammar, and statuses; convert emails to mailto; expand TSC acronym once

Small clarity/grammar improvements and better status wording. Also expands “TSC” on first use.

-- Google Workspace:
-  - owned by Fran
-  - connected domain: asyncapi.io
-  - used email addresses:
-    - info@asyncapi.io (used for contact with partners/sponsors and for security reports)
-    - press@asyncapi.io (not sure what the status is, never accessed it, old email)
-    - bot@asyncapi.io and alias bot+eve@asyncapi.io used for two AsyncAPI GitHub bot accounts
-- Mailjet: used for emailing TSC members to remind them they did not vote yet
-- Mailchimp:
-  - owned by Fran
-  - used for [newsletter](https://www.asyncapi.com/en/newsletter) and a separate mailing list for [TSC notifications](https://www.asyncapi.com/community/tsc)
+- Google Workspace:
+  - Owner: Fran (primary)
+  - Connected domain: asyncapi.io
+  - Email addresses:
+    - [info@asyncapi.io](mailto:info@asyncapi.io) (partner/sponsor contact and security reports)
+    - [press@asyncapi.io](mailto:press@asyncapi.io) (status unknown; likely legacy — verify or deprecate)
+    - [bot@asyncapi.io](mailto:bot@asyncapi.io) and alias [bot+eve@asyncapi.io](mailto:bot+eve@asyncapi.io) used by two AsyncAPI GitHub bot accounts
+- Mailjet: used to email Technical Steering Committee (TSC) members who have not voted yet
+- Mailchimp:
+  - Owner: Fran
+  - Used for the [newsletter](https://www.asyncapi.com/en/newsletter) and a separate mailing list for [TSC notifications](https://www.asyncapi.com/community/tsc)

Optional: consider adding “Backup owner” and whether 2FA is enforced for Google Workspace and Mailchimp.

---

28-33: GitHub: link formatting and add a note about 2FA/org policies

Convert to links and consider documenting key org policies (2FA required, team structure) for completeness.

-- Main Org: https://github.com/asyncapi
-- Org with archived repos: https://github.com/asyncapi-archived-repos
-- Bots: https://github.com/asyncapi-bot and https://github.com/asyncapi-bot-eve used in GitHub Actions automation
+- Main org: <https://github.com/asyncapi>
+- Org with archived repos: <https://github.com/asyncapi-archived-repos>
+- Bots: <https://github.com/asyncapi-bot> and <https://github.com/asyncapi-bot-eve> (used in GitHub Actions automation)

If you want, I can propose a short “Org policy” sublist (2FA, branch protection, required reviews, bot token rotation cadence).

---

34-39: Rename “Others” to “CI and code quality”; fix Codecov casing

Clearer section title and correct brand casing.

-### Others
+### CI and code quality
@@
-- SonarCloud for PR scanning
-- CodeRabbit for PR scanning
-- CodeCov for PR test coverage scanning
+- SonarCloud for PR scanning
+- CodeRabbit for PR scanning
+- Codecov for PR test coverage scanning

---

42-44: Deployments: tighten phrasing and link formatting

Minor language and consistency improvements.

-- DigitalOcean: for deployment of https://github.com/asyncapi/server-api. Renewal is needed every year.
+- DigitalOcean: hosts <https://github.com/asyncapi/server-api>. Annual renewal required.
 - Netlify: for [website](https://github.com/asyncapi/website), [conference website](https://github.com/asyncapi/conference-website), and [studio](https://github.com/asyncapi/studio) deployments.

---

45-50: Analytics: hyphenate “open-source” and improve wording

Also wrap any remaining bare URLs with angle brackets if present.

-- Netlify: Our additional open source plan gives basic stats too
+- Netlify: Our additional open-source plan provides basic stats too

---

51-57: Package Managers (libraries): grammar, clarity, and “at the moment”

May also consider adding “Owner” and “Backup owner” per ecosystem.

-For packages/libraries:
-- [npm](https://www.npmjs.com/) (JS and TS world): we own `@asyncapi` scope. Publishing is automated, and deprecation is manually done by https://github.com/derberg
-- [Maven Central](https://central.sonatype.com/) (Java world): we own `com.asyncapi` namespace. Manual publishing done by https://github.com/Pakisan
-- [NuGet](https://www.nuget.org/) (.NET world): `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discussions/1804. We have our account and https://github.com/asyncapi/saunter is published there manually. A project like https://github.com/asyncapi/net-sdk is not migrated atm.
+For packages/libraries:
+- [npm](https://www.npmjs.com/) (JS/TS): we own the `@asyncapi` scope. Publishing is automated; deprecations are handled manually by <https://github.com/derberg>.
+- [Maven Central](https://central.sonatype.com/) (Java): we own the `com.asyncapi` namespace. Manual publishing handled by <https://github.com/Pakisan>.
+- [NuGet](https://www.nuget.org/) (.NET): the `asyncapi` prefix is reserved by LEGO. This needs to be solved at some point: <https://github.com/orgs/asyncapi/discussions/1804>. We have our account, and <https://github.com/asyncapi/saunter> is published there manually. Projects like <https://github.com/asyncapi/net-sdk> are not migrated at the moment.

---

58-62: Plugins: brand names, grammar, and clarity

Minor fixes and consistent wording.

-For plugins:
-- [VisualStudio Marketplace](https://marketplace.visualstudio.com/publishers/asyncapi): We have an account under which we publish https://github.com/asyncapi/vs-asyncapi-preview in automated way
-- [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview in automated way
-- [JetBrains](https://plugins.jetbrains.com/plugin/15673-asyncapi#): Not official account to publish https://github.com/asyncapi/jasyncapi-idea-plugin in manual way. Atm https://github.com/Pakisan takes care of it.
+For plugins:
+- [Visual Studio Marketplace](https://marketplace.visualstudio.com/publishers/asyncapi): we publish <https://github.com/asyncapi/vs-asyncapi-preview> automatically.
+- [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): we publish <https://github.com/asyncapi/vs-asyncapi-preview> automatically.
+- [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/15673-asyncapi): not an official account; publishes <https://github.com/asyncapi/jasyncapi-idea-plugin> manually. At the moment, <https://github.com/Pakisan> takes care of it.

---

63-71: Funded roles: confirm consent to publish compensation details; optional rename

Since this page is public, please confirm each person consents to publishing their compensation amounts. Consider renaming the section to “Funded roles and contractors” for governance clarity.

If you want, I can add a brief note stating “All costs are planned in the budget and approved by the TSC,” and link to the budget page for context.

---

72-79: Social media: style and clarity; fix bare URLs

Small clarity/grammar improvements.

-- Buffer: we pay for it $480 once a year. Used to post in one place and send posts to all social media
-- LinkedIn: https://www.linkedin.com/company/asyncapi
-- X: https://x.com/AsyncAPISpec
-- Mastodon: https://fosstodon.org/@AsyncAPISpec
-- Twitch: https://www.twitch.tv/asyncapi
+- Buffer: we pay $480 annually. Used to compose once and publish across social media.
+- LinkedIn: <https://www.linkedin.com/company/asyncapi>
+- X: <https://x.com/AsyncAPISpec>
+- Mastodon: <https://fosstodon.org/@AsyncAPISpec>
+- Twitch: <https://www.twitch.tv/asyncapi>

---

80-83: Fix heading typo and clarify Slack plan

“Messangers” → “Messengers.” Optional clarity on Slack’s plan.

-## Messangers
+## Messengers
@@
-- Slack: Pro Plan for free. We don't need to renew anything.
+- Slack: Pro plan granted for free (open-source program). No renewals required.

---

84-88: Meetings: tighten phrasing

Minor language polish.

-- [Restream](https://restream.io/): Streaming to different social media channels. Free pro access. Needs renewal every year.
-- Zoom: Paid service. We approve it as part of the budget once a year.
+- [Restream](https://restream.io/): streams to multiple social media channels. Pro access granted for free; renews annually.
+- Zoom: paid service; approved annually as part of the budget.

---

89-92: Video: link formatting

-- YouTube: https://www.youtube.com/@AsyncAPI
+- YouTube: <https://www.youtube.com/@AsyncAPI>

---

1-92: Optional: add lightweight metadata per item for access control hygiene

To make this a durable inventory, consider adding a consistent set of fields per service:

• Owner (person or role alias) and backup owner
• Billing owner/source and renewal cadence/date
• Access model (who has access; where it’s managed)
• Security posture (2FA enforced, SSO where applicable)
• Notes (integration details, dependencies)

I can draft a compact bullet template you can copy-paste under each section.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b596920 and 25e9456.

📒 Files selected for processing (1)

• docs/020-governance-and-policies/initiative-inventory.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/020-governance-and-policies/initiative-inventory.md

[grammar] ~3-~3: There might be a mistake here.
Context: ...cts: https://opencollective.com/asyncapi - Linux Foundation Crowdfunding: https://c...

(QB_NEW_EN)

---

[grammar] ~4-~4: There might be a mistake here.
Context: ...fx.linuxfoundation.org/projects/asyncapi - GitHub Sponsors: https://github.com/spon...

(QB_NEW_EN)

---

[grammar] ~11-~11: There might be a mistake here.
Context: ...aged by Linux Foundation - asyncapi.com - asyncapi.org ## Email - Google Workspa...

(QB_NEW_EN)

---

[grammar] ~19-~19: There might be a mistake here.
Context: ...n: asyncapi.io - used email addresses: - info@asyncapi.io (used for contact with ...

(QB_NEW_EN)

---

[grammar] ~20-~20: There might be a mistake here.
Context: ...tners/sponsors and for security reports) - press@asyncapi.io (not sure what the sta...

(QB_NEW_EN)

---

[grammar] ~21-~21: There might be a mistake here.
Context: ...status is, never accessed it, old email) - bot@asyncapi.io and alias bot+eve@asynca...

(QB_NEW_EN)

---

[grammar] ~22-~22: There might be a mistake here.
Context: ...sed for two AsyncAPI GitHub bot accounts - Mailjet: used for emailing TSC members t...

(QB_NEW_EN)

---

[grammar] ~23-~23: There might be a mistake here.
Context: ...ers to remind them they did not vote yet - Mailchimp: - owned by Fran - used fo...

(QB_NEW_EN)

---

[grammar] ~30-~30: There might be a mistake here.
Context: ... - Main Org: https://github.com/asyncapi - Org with archived repos: https://github....

(QB_NEW_EN)

---

[grammar] ~31-~31: There might be a mistake here.
Context: ...tps://github.com/asyncapi-archived-repos - Bots: https://github.com/asyncapi-bot an...

(QB_NEW_EN)

---

[grammar] ~36-~36: There might be a mistake here.
Context: ...### Others - SonarCloud for PR scanning - CodeRabbit for PR scanning - CodeCov for...

(QB_NEW_EN)

---

[grammar] ~37-~37: There might be a mistake here.
Context: ...PR scanning - CodeRabbit for PR scanning - CodeCov for PR test coverage scanning ...

(QB_NEW_EN)

---

[grammar] ~47-~47: There might be a mistake here.
Context: ...syncapi/website) and conference website - Netlify: Our additional open source plan...

(QB_NEW_EN)

---

[uncategorized] ~48-~48: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ence-website) - Netlify: Our additional open source plan gives basic stats too - [LFX Insig...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~53-~53: There might be a mistake here.
Context: ... Managers (TBD) For packages/libraries: - npm (JS and TS ...

(QB_NEW_EN)

---

[grammar] ~55-~55: There might be a mistake here.
Context: ...ps://github.com/derberg - Maven Central (Java world): we own com.asyncapi nam...

(QB_NEW_EN)

---

[style] ~56-~56: This phrase is redundant. Consider writing “point” or “time”.
Context: ...y LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discu...

(MOMENT_IN_TIME)

---

[grammar] ~58-~58: There might be a mistake here.
Context: ...t-sdk is not migrated atm. For plugins: - [VisualStudio Marketplace](https://market...

(QB_NEW_EN)

---

[grammar] ~59-~59: There might be a mistake here.
Context: ...github.com/asyncapi/vs-asyncapi-preview in automated way - [Open VSX Registry](htt...

(QB_NEW_EN)

---

[grammar] ~60-~60: There might be a mistake here.
Context: ...github.com/asyncapi/vs-asyncapi-preview in automated way - [JetBrains](https://plu...

(QB_NEW_EN)

---

[grammar] ~61-~61: There might be a mistake here.
Context: ....jetbrains.com/plugin/15673-asyncapi#): Not official account to publish https://git...

(QB_NEW_EN)

---

[grammar] ~61-~61: There might be a mistake here.
Context: ...thub.com/asyncapi/jasyncapi-idea-plugin in manual way. Atm https://github.com/Paki...

(QB_NEW_EN)

---

[grammar] ~61-~61: Ensure spelling is correct
Context: ...pi/jasyncapi-idea-plugin in manual way. Atm https://github.com/Pakisan takes care o...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~65-~65: There might be a mistake here.
Context: ...g goal is to have dedicated subprojects in Open Collective platform to secure fund...

(QB_NEW_EN)

---

[uncategorized] ~67-~67: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...): hired through official contract with Open Source Collective (on our behalf) to do commun...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~68-~68: There might be a mistake here.
Context: ...sh](https://github.com/aeworxet): makes sure AsyncAPI Bounty program runs smoothly, ...

(QB_NEW_EN)

---

[grammar] ~69-~69: There might be a mistake here.
Context: ...ami](https://github.com/iambami): hired through official contract with Open Source Coll...

(QB_NEW_EN)

---

[uncategorized] ~69-~69: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...): hired through official contract with Open Source Collective (on our behalf) to do commun...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[style] ~70-~70: Consider using the more formal “until”.
Context: ...llective subproject for securing funds. Till now, we did dedicated projects per ment...

(TILL)

---

[grammar] ~75-~75: There might be a mistake here.
Context: ...ttps://www.linkedin.com/company/asyncapi - X: https://x.com/AsyncAPISpec - Mastodon...

(QB_NEW_EN)

---

[grammar] ~76-~76: There might be a mistake here.
Context: ...asyncapi - X: https://x.com/AsyncAPISpec - Mastodon: https://fosstodon.org/@AsyncAP...

(QB_NEW_EN)

---

[grammar] ~77-~77: There might be a mistake here.
Context: ...don: https://fosstodon.org/@AsyncAPISpec - Twitch: https://www.twitch.tv/asyncapi ...

(QB_NEW_EN)

🪛 markdownlint-cli2 (0.17.2)

docs/020-governance-and-policies/initiative-inventory.md

3-3: Bare URL used

(MD034, no-bare-urls)

---

4-4: Bare URL used

(MD034, no-bare-urls)

---

5-5: Bare URL used

(MD034, no-bare-urls)

---

20-20: Bare URL used

(MD034, no-bare-urls)

---

21-21: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

30-30: Bare URL used

(MD034, no-bare-urls)

---

31-31: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

42-42: Bare URL used

(MD034, no-bare-urls)

---

54-54: Bare URL used

(MD034, no-bare-urls)

---

55-55: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

59-59: Bare URL used

(MD034, no-bare-urls)

---

60-60: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

67-67: Bare URL used

(MD034, no-bare-urls)

---

68-68: Bare URL used

(MD034, no-bare-urls)

---

69-69: Bare URL used

(MD034, no-bare-urls)

---

75-75: Bare URL used

(MD034, no-bare-urls)

---

76-76: Bare URL used

(MD034, no-bare-urls)

---

77-77: Bare URL used

(MD034, no-bare-urls)

---

78-78: Bare URL used

(MD034, no-bare-urls)

---

91-91: Bare URL used

(MD034, no-bare-urls)

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (15)

docs/020-governance-and-policies/initiative-inventory.md (15)

1-2: Add an H1 title and brief intro to set context and answer the author’s question.

Currently the file starts with a section heading. Add a top-level title and 1–2 sentence intro outlining purpose, scope, and who maintains it. This also improves docs navigation/SEO.

Apply this diff to add a title and intro and rename the first section:

+# AsyncAPI Initiative: Asset and Accounts Inventory
+
+This document inventories public-facing assets, accounts, and tools used by the AsyncAPI Initiative, including ownership, access, renewal cycles, and usage notes. It is maintained by the TSC and the wider community; please submit PRs to propose updates.
+
-## Payment/Donations
+## Funding and donations

---

3-5: Convert bare URLs to Markdown links (fixes markdownlint MD034).

Use descriptive link text for consistency and to satisfy the linter.

Apply:

-- Open Collective and multiple sub-projects: https://opencollective.com/asyncapi
-- Linux Foundation Crowdfunding: https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi
-- GitHub Sponsors: https://github.com/sponsors/asyncapi
+- Open Collective and sub-projects: [opencollective.com/asyncapi](https://opencollective.com/asyncapi)
+- Linux Foundation Crowdfunding: [lfx.linuxfoundation.org/projects/asyncapi](https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi)
+- GitHub Sponsors: [github.com/sponsors/asyncapi](https://github.com/sponsors/asyncapi)

---

9-13: Grammar tweak and add asyncapi.io (email domain) to the domains list.

• “Managed by Linux Foundation” → “Managed by the Linux Foundation”
• Email section references asyncapi.io; include it here for completeness.

Proposed change:

-Managed by Linux Foundation
+Managed by the Linux Foundation
-
-- asyncapi.com
-- asyncapi.org
+- asyncapi.com
+- asyncapi.org
+- asyncapi.io  <!-- used for email; confirm ownership/management is also LF -->

Please confirm whether asyncapi.io is also LF-managed; if not, note its owner/registrar for clarity.

---

16-27: Clarify ownership phrasing and fix minor grammar; confirm public listing of personal ownership.

• Prefer neutral phrasing (“Owned by …” → “Owned by …”) and consistent style (“automatically/manually”).
• Verify you want to publicly list a named individual as the account owner; consider a role account if possible.

Apply:

- Google Workspace:
-  - owned by Fran
+ Google Workspace:
+  - Owned by Fran
   - connected domain: asyncapi.io
   - used email addresses:
     - info@asyncapi.io (used for contact with partners/sponsors and for security reports)
-    - press@asyncapi.io (not sure what the status is, never accessed it, old email)
-    - bot@asyncapi.io and alias bot+eve@asyncapi.io used for two AsyncAPI GitHub bot accounts
-- Mailjet: used for emailing TSC members to remind them they did not vote yet
+    - press@asyncapi.io (status unknown; legacy)
+    - bot@asyncapi.io and alias bot+eve@asyncapi.io (used by two AsyncAPI GitHub bot accounts)
+- Mailjet: used to email TSC members to remind them they have not voted yet
 - Mailchimp:
-  - owned by Fran
-  - used for [newsletter](https://www.asyncapi.com/en/newsletter) and a separate mailing list for [TSC notifications](https://www.asyncapi.com/community/tsc)
+  - Owned by Fran
+  - Used for the [newsletter](https://www.asyncapi.com/en/newsletter) and a separate mailing list for [TSC notifications](https://www.asyncapi.com/community/tsc)

---

30-33: Linkify GitHub orgs/bots and tighten phrasing.

Fixes MD034 and improves readability.

Apply:

-- Main Org: https://github.com/asyncapi
-- Org with archived repos: https://github.com/asyncapi-archived-repos
-- Bots: https://github.com/asyncapi-bot and https://github.com/asyncapi-bot-eve used in GitHub Actions automation
+- Main org: [github.com/asyncapi](https://github.com/asyncapi)
+- Org with archived repos: [github.com/asyncapi-archived-repos](https://github.com/asyncapi-archived-repos)
+- Bots: [@asyncapi-bot](https://github.com/asyncapi-bot) and [@asyncapi-bot-eve](https://github.com/asyncapi-bot-eve), used in GitHub Actions automation

---

36-39: Add links to tooling; use proper names.

Also fixes MD034.

Apply:

-- SonarCloud for PR scanning
-- CodeRabbit for PR scanning
-- CodeCov for PR test coverage scanning
+- [SonarCloud](https://sonarcloud.io/) for PR scanning
+- [CodeRabbit](https://coderabbit.ai/) for PR scanning
+- [Codecov](https://about.codecov.io/) for PR test coverage scanning

---

42-44: Linkify repos/services and polish renewal wording.

Apply:

-- DigitalOcean: for deployment of https://github.com/asyncapi/server-api. Renewal is needed every year.
-- Netlify: for [website](https://github.com/asyncapi/website), [conference website](https://github.com/asyncapi/conference-website), and [studio](https://github.com/asyncapi/studio) deployments.
+- DigitalOcean: deployment of [asyncapi/server-api](https://github.com/asyncapi/server-api). Renewal is required annually.
+- Netlify: deployments for [website](https://github.com/asyncapi/website), [conference website](https://github.com/asyncapi/conference-website), and [studio](https://github.com/asyncapi/studio).

---

47-50: Hyphenate “open-source” and minor style tweaks.

Apply:

-- Netlify: Our additional open source plan gives basic stats too
+- Netlify: Our additional open-source plan provides basic stats too
 - [LFX Insights](https://lfx.linuxfoundation.org/tools/insights/): Lots of GitHub-stats about the org. We can also manage some of the info.

---

51-57: Remove “(TBD)” and improve clarity/links in package managers section.

This section is already populated; drop the TBD, link user handles, and fix phrasing.

Apply:

-## Package Managers (TBD)
+## Package managers
@@
-For packages/libraries:
+For packages and libraries:
 - [npm](https://www.npmjs.com/) (JS and TS world): we own `@asyncapi` scope. Publishing is automated, and deprecation is manually done by https://github.com/derberg
-- [Maven Central](https://central.sonatype.com/) (Java world): we own `com.asyncapi` namespace. Manual publishing done by https://github.com/Pakisan
-- [NuGet](https://www.nuget.org/) (.NET world): `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discussions/1804. We have our account and https://github.com/asyncapi/saunter is published there manually. A project like https://github.com/asyncapi/net-sdk is not migrated atm.
+- [Maven Central](https://central.sonatype.com/) (Java world): we own the `com.asyncapi` namespace. Manual publishing is done by [@Pakisan](https://github.com/Pakisan).
+- [NuGet](https://www.nuget.org/) (.NET world): the `asyncapi` prefix is already reserved by LEGO. This needs to be resolved at some point: [org discussion #1804](https://github.com/orgs/asyncapi/discussions/1804). We have an account, and [asyncapi/saunter](https://github.com/asyncapi/saunter) is published there manually. A project like [asyncapi/net-sdk](https://github.com/asyncapi/net-sdk) is not migrated currently.
@@
-- [npm](https://www.npmjs.com/) (JS and TS world): we own `@asyncapi` scope. Publishing is automated, and deprecation is manually done by https://github.com/derberg
+- [npm](https://www.npmjs.com/) (JS and TS world): we own the `@asyncapi` scope. Publishing is automated, and deprecation is performed manually by [@derberg](https://github.com/derberg).

---

59-62: Fix product names and phrasing in plugins section.

Also linkify for consistency and fix “atm”.

Apply:

-- [VisualStudio Marketplace](https://marketplace.visualstudio.com/publishers/asyncapi): We have an account under which we publish https://github.com/asyncapi/vs-asyncapi-preview in automated way
-- [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview in automated way
-- [JetBrains](https://plugins.jetbrains.com/plugin/15673-asyncapi#): Not official account to publish https://github.com/asyncapi/jasyncapi-idea-plugin in manual way. Atm https://github.com/Pakisan takes care of it.
+- [Visual Studio Marketplace](https://marketplace.visualstudio.com/publishers/asyncapi): We publish [asyncapi/vs-asyncapi-preview](https://github.com/asyncapi/vs-asyncapi-preview) automatically under our account.
+- [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We publish [asyncapi/vs-asyncapi-preview](https://github.com/asyncapi/vs-asyncapi-preview) automatically under our official account.
+- [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/15673-asyncapi): No official org account; we publish [asyncapi/jasyncapi-idea-plugin](https://github.com/asyncapi/jasyncapi-idea-plugin) manually. Currently, [@Pakisan](https://github.com/Pakisan) takes care of it.

---

74-79: Polish social media section and linkify platform names.

Also fixes MD034.

Apply:

-- Buffer: we pay for it $480 once a year. Used to post in one place and send posts to all social media
-- LinkedIn: https://www.linkedin.com/company/asyncapi
-- X: https://x.com/AsyncAPISpec
-- Mastodon: https://fosstodon.org/@AsyncAPISpec
-- Twitch: https://www.twitch.tv/asyncapi
+- Buffer: we pay $480 once a year. Used to schedule posts across social media.
+- LinkedIn: [linkedin.com/company/asyncapi](https://www.linkedin.com/company/asyncapi)
+- X (Twitter): [x.com/AsyncAPISpec](https://x.com/AsyncAPISpec)
+- Mastodon: [fosstodon.org/@AsyncAPISpec](https://fosstodon.org/@AsyncAPISpec)
+- Twitch: [twitch.tv/asyncapi](https://www.twitch.tv/asyncapi)

---

80-83: Correct heading spelling and minor copy edit.

“Messangers” → “Messengers” (or consider “Messaging”).

Apply:

-## Messangers
+## Messengers
@@
-- Slack: Pro Plan for free. We don't need to renew anything.
+- Slack: Pro plan for free. No renewal needed.

---

86-88: Tighten meeting tools phrasing and renewal wording.

Apply:

-- [Restream](https://restream.io/): Streaming to different social media channels. Free pro access. Needs renewal every year.
-- Zoom: Paid service. We approve it as part of the budget once a year.
+- [Restream](https://restream.io/): Streaming to multiple social media platforms. Complimentary Pro access; requires annual renewal.
+- Zoom: Paid service; approved as part of the annual budget.

---

91-92: Linkify YouTube channel.

Fixes MD034.

Apply:

-- YouTube: https://www.youtube.com/@AsyncAPI
+- YouTube: [youtube.com/@AsyncAPI](https://www.youtube.com/@AsyncAPI)

---

1-92: Consider adding a short “Maintenance and updates” section.

This sets expectations for cadence, owners, and how to propose changes. Optional but helpful given the board’s request for an inventory.

Suggested section (add near the end):

+## Maintenance and updates
+
+- Document owner: TSC (primary), Community Manager (editor)
+- Review cadence: quarterly (or after any major vendor/ownership change)
+- How to propose changes: open a PR to this file; include rationale and any access/ownership updates
+- Last updated: YYYY-MM-DD

I can add this with an initial “Last updated” date if you want.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b596920 and 25e9456.

📒 Files selected for processing (1)

• docs/020-governance-and-policies/initiative-inventory.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/020-governance-and-policies/initiative-inventory.md

[grammar] ~3-~3: There might be a mistake here.
Context: ...cts: https://opencollective.com/asyncapi - Linux Foundation Crowdfunding: https://c...

(QB_NEW_EN)

---

[grammar] ~4-~4: There might be a mistake here.
Context: ...fx.linuxfoundation.org/projects/asyncapi - GitHub Sponsors: https://github.com/spon...

(QB_NEW_EN)

---

[grammar] ~11-~11: There might be a mistake here.
Context: ...aged by Linux Foundation - asyncapi.com - asyncapi.org ## Email - Google Workspa...

(QB_NEW_EN)

---

[grammar] ~19-~19: There might be a mistake here.
Context: ...n: asyncapi.io - used email addresses: - info@asyncapi.io (used for contact with ...

(QB_NEW_EN)

---

[grammar] ~20-~20: There might be a mistake here.
Context: ...tners/sponsors and for security reports) - press@asyncapi.io (not sure what the sta...

(QB_NEW_EN)

---

[grammar] ~21-~21: There might be a mistake here.
Context: ...status is, never accessed it, old email) - bot@asyncapi.io and alias bot+eve@asynca...

(QB_NEW_EN)

---

[grammar] ~22-~22: There might be a mistake here.
Context: ...sed for two AsyncAPI GitHub bot accounts - Mailjet: used for emailing TSC members t...

(QB_NEW_EN)

---

[grammar] ~23-~23: There might be a mistake here.
Context: ...ers to remind them they did not vote yet - Mailchimp: - owned by Fran - used fo...

(QB_NEW_EN)

---

[grammar] ~30-~30: There might be a mistake here.
Context: ... - Main Org: https://github.com/asyncapi - Org with archived repos: https://github....

(QB_NEW_EN)

---

[grammar] ~31-~31: There might be a mistake here.
Context: ...tps://github.com/asyncapi-archived-repos - Bots: https://github.com/asyncapi-bot an...

(QB_NEW_EN)

---

[grammar] ~36-~36: There might be a mistake here.
Context: ...### Others - SonarCloud for PR scanning - CodeRabbit for PR scanning - CodeCov for...

(QB_NEW_EN)

---

[grammar] ~37-~37: There might be a mistake here.
Context: ...PR scanning - CodeRabbit for PR scanning - CodeCov for PR test coverage scanning ...

(QB_NEW_EN)

---

[grammar] ~47-~47: There might be a mistake here.
Context: ...syncapi/website) and conference website - Netlify: Our additional open source plan...

(QB_NEW_EN)

---

[uncategorized] ~48-~48: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ence-website) - Netlify: Our additional open source plan gives basic stats too - [LFX Insig...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~53-~53: There might be a mistake here.
Context: ... Managers (TBD) For packages/libraries: - npm (JS and TS ...

(QB_NEW_EN)

---

[grammar] ~55-~55: There might be a mistake here.
Context: ...ps://github.com/derberg - Maven Central (Java world): we own com.asyncapi nam...

(QB_NEW_EN)

---

[style] ~56-~56: This phrase is redundant. Consider writing “point” or “time”.
Context: ...y LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discu...

(MOMENT_IN_TIME)

---

[grammar] ~58-~58: There might be a mistake here.
Context: ...t-sdk is not migrated atm. For plugins: - [VisualStudio Marketplace](https://market...

(QB_NEW_EN)

---

[grammar] ~59-~59: There might be a mistake here.
Context: ...github.com/asyncapi/vs-asyncapi-preview in automated way - [Open VSX Registry](htt...

(QB_NEW_EN)

---

[grammar] ~60-~60: There might be a mistake here.
Context: ...github.com/asyncapi/vs-asyncapi-preview in automated way - [JetBrains](https://plu...

(QB_NEW_EN)

---

[grammar] ~61-~61: There might be a mistake here.
Context: ....jetbrains.com/plugin/15673-asyncapi#): Not official account to publish https://git...

(QB_NEW_EN)

---

[grammar] ~61-~61: There might be a mistake here.
Context: ...thub.com/asyncapi/jasyncapi-idea-plugin in manual way. Atm https://github.com/Paki...

(QB_NEW_EN)

---

[grammar] ~61-~61: Ensure spelling is correct
Context: ...pi/jasyncapi-idea-plugin in manual way. Atm https://github.com/Pakisan takes care o...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~65-~65: There might be a mistake here.
Context: ...g goal is to have dedicated subprojects in Open Collective platform to secure fund...

(QB_NEW_EN)

---

[uncategorized] ~67-~67: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...): hired through official contract with Open Source Collective (on our behalf) to do commun...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~68-~68: There might be a mistake here.
Context: ...sh](https://github.com/aeworxet): makes sure AsyncAPI Bounty program runs smoothly, ...

(QB_NEW_EN)

---

[grammar] ~69-~69: There might be a mistake here.
Context: ...ami](https://github.com/iambami): hired through official contract with Open Source Coll...

(QB_NEW_EN)

---

[uncategorized] ~69-~69: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...): hired through official contract with Open Source Collective (on our behalf) to do commun...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[style] ~70-~70: Consider using the more formal “until”.
Context: ...llective subproject for securing funds. Till now, we did dedicated projects per ment...

(TILL)

---

[grammar] ~75-~75: There might be a mistake here.
Context: ...ttps://www.linkedin.com/company/asyncapi - X: https://x.com/AsyncAPISpec - Mastodon...

(QB_NEW_EN)

---

[grammar] ~76-~76: There might be a mistake here.
Context: ...asyncapi - X: https://x.com/AsyncAPISpec - Mastodon: https://fosstodon.org/@AsyncAP...

(QB_NEW_EN)

---

[grammar] ~77-~77: There might be a mistake here.
Context: ...don: https://fosstodon.org/@AsyncAPISpec - Twitch: https://www.twitch.tv/asyncapi ...

(QB_NEW_EN)

🪛 markdownlint-cli2 (0.17.2)

docs/020-governance-and-policies/initiative-inventory.md

3-3: Bare URL used

(MD034, no-bare-urls)

---

4-4: Bare URL used

(MD034, no-bare-urls)

---

5-5: Bare URL used

(MD034, no-bare-urls)

---

20-20: Bare URL used

(MD034, no-bare-urls)

---

21-21: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

30-30: Bare URL used

(MD034, no-bare-urls)

---

31-31: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

42-42: Bare URL used

(MD034, no-bare-urls)

---

54-54: Bare URL used

(MD034, no-bare-urls)

---

55-55: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

59-59: Bare URL used

(MD034, no-bare-urls)

---

60-60: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

67-67: Bare URL used

(MD034, no-bare-urls)

---

68-68: Bare URL used

(MD034, no-bare-urls)

---

69-69: Bare URL used

(MD034, no-bare-urls)

---

75-75: Bare URL used

(MD034, no-bare-urls)

---

76-76: Bare URL used

(MD034, no-bare-urls)

---

77-77: Bare URL used

(MD034, no-bare-urls)

---

78-78: Bare URL used

(MD034, no-bare-urls)

---

91-91: Bare URL used

(MD034, no-bare-urls)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Lint PR title
• GitHub Check: automerge-for-humans

🔇 Additional comments (1)

docs/020-governance-and-policies/initiative-inventory.md (1)

16-27: Double-check public exposure of personal account ownership and access details.

The doc publicly lists specific individuals as owners for Google Workspace and Mailchimp, and includes direct links to internal analytics properties. If this is intentional, all good. If not, consider replacing with role-based ownership (e.g., “Owned by AsyncAPI TSC via LF”) and adding “requires org access” notes.

Would you like me to refactor the doc to consistently use role-based ownership and minimize individual naming?

[coderabbitai]

Actionable comments posted: 2

♻️ Duplicate comments (1)

docs/020-governance-and-policies/initiative-inventory.md (1)

70-70: Past feedback addressed: corrected “$1” → “$1k” breakdown.

This resolves the earlier typo and matches the $2k total.

🧹 Nitpick comments (12)

docs/020-governance-and-policies/initiative-inventory.md (12)

3-5: Replace bare URLs with Markdown links (lint: MD034).

This prevents markdownlint failures and improves readability.

Apply:

-- Open Collective and multiple sub-projects: https://opencollective.com/asyncapi
-- Linux Foundation Crowdfunding: https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi
-- GitHub Sponsors: https://github.com/sponsors/asyncapi
+- [Open Collective and multiple sub-projects](https://opencollective.com/asyncapi)
+- [Linux Foundation Crowdfunding](https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi)
+- [GitHub Sponsors](https://github.com/sponsors/asyncapi)

If you prefer to keep the current style, consider wrapping with angle brackets (<...>) to appease MD034.

---

30-33: Convert these to labeled links and tighten wording.

Minor readability and lint improvements.

Apply:

-- Main Org: https://github.com/asyncapi
-- Org with archived repos: https://github.com/asyncapi-archived-repos
-- Bots: https://github.com/asyncapi-bot and https://github.com/asyncapi-bot-eve used in GitHub Actions automation
+- Main org: https://github.com/asyncapi
+- Archived repos org: https://github.com/asyncapi-archived-repos
+- Bots: https://github.com/asyncapi-bot and https://github.com/asyncapi-bot-eve (used in GitHub Actions automation)

---

9-13: Add definite article for clarity.

Small grammar tweak.

Apply:

-Managed by Linux Foundation
+Managed by the Linux Foundation

---

16-27: Clarify ownership phrasing and neutralize uncertain language.

• Prefer “administered by” to avoid implying personal ownership.
• Make legacy mailbox status neutral and factual.
• Minor grammar fixes.

Apply:

- - Google Workspace:
-   - owned by Fran
+ - Google Workspace:
+   - administered by Fran
    - connected domain: asyncapi.io
-   - used email addresses:
-     - info@asyncapi.io (used for contact with partners/sponsors and for security reports)
-     - press@asyncapi.io (not sure what the status is, never accessed it, old email)
-     - bot@asyncapi.io and alias bot+eve@asyncapi.io used for two AsyncAPI GitHub bot accounts
-- Mailjet: used for emailing TSC members to remind them they did not vote yet
+   - mailboxes:
+     - info@asyncapi.io (partners/sponsors contact and security reports)
+     - press@asyncapi.io (status unknown; legacy address)
+     - bot@asyncapi.io and alias bot+eve@asyncapi.io (used by two AsyncAPI GitHub bot accounts)
+- Mailjet: used to email TSC members who have not yet voted
 - Mailchimp:
-  - owned by Fran
-  - used for [newsletter](https://www.asyncapi.com/en/newsletter) and a separate mailing list for [TSC notifications](https://www.asyncapi.com/community/tsc)
+  - administered by Fran
+  - used for the [newsletter](https://www.asyncapi.com/en/newsletter) and a separate mailing list for [TSC notifications](https://www.asyncapi.com/community/tsc)

Optional follow-up: consider listing a backup admin or escalation contact to reduce bus-factor risk.

---

42-42: Tighten wording; keep style consistent.

Apply:

-- DigitalOcean: for deployment of https://github.com/asyncapi/server-api. Renewal is needed every year.
+- DigitalOcean: hosts https://github.com/asyncapi/server-api. Requires annual renewal.

---

47-49: Polish wording; hyphenate “open-source” as a compound adjective.

Apply:

 - [Google Analytics](https://analytics.google.com/analytics/web/#/p271857523) for [website](https://github.com/asyncapi/website) and [conference website](https://github.com/asyncapi/conference-website)
-- Netlify: Our additional open source plan gives basic stats too
-- [LFX Insights](https://lfx.linuxfoundation.org/tools/insights/): Lots of GitHub-stats about the org. We can also manage some of the info.
+- Netlify: Our open-source plan provides basic stats as well
+- [LFX Insights](https://lfx.linuxfoundation.org/tools/insights/): Lots of GitHub stats about the org. We can also manage some of the info.

---

56-56: Avoid redundant phrase “at some point in time”.

Apply:

-- [NuGet](https://www.nuget.org/) (.NET world): `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discussions/1804. We have our account and https://github.com/asyncapi/saunter is published there manually. A project like https://github.com/asyncapi/net-sdk is not migrated atm.
+- [NuGet](https://www.nuget.org/) (.NET world): `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point: https://github.com/orgs/asyncapi/discussions/1804. We have our account and https://github.com/asyncapi/saunter is published there manually. A project like https://github.com/asyncapi/net-sdk is not migrated yet.

---

65-65: Minor grammar: article and preposition.

Apply:

-People we hire through Open Collective contracts or pay for a specific job to be done in one of our official programs. All costs below are always planned in the budget and approved by TSC. For clarity and better budget planning goal is to have dedicated subprojects in Open Collective platform to secure funding more easily.
+People we hire through Open Collective contracts or pay for a specific job to be done in one of our official programs. All costs below are always planned in the budget and approved by TSC. For clarity and better budget planning, the goal is to have dedicated subprojects on the Open Collective platform to secure funding more easily.

---

68-68: Optional wording tweak for readability.

Apply:

-- [Ash](https://github.com/aeworxet): makes sure AsyncAPI Bounty program runs smoothly, organizes 4 rounds each quarter. We pay $400 for each round. We started to manage funding through https://opencollective.com/asyncapi/projects/asyncapi-bounty-program
+- [Ash](https://github.com/aeworxet): ensures the AsyncAPI Bounty program runs smoothly and organizes 4 rounds each quarter. We pay $400 per round. Funding is managed through https://opencollective.com/asyncapi/projects/asyncapi-bounty-program

---

34-34: Heading clarity: “Others” → “Other tools”.

Makes the subsection’s purpose clearer.

Apply:

-### Others
+### Other tools

---

1-1: Add a short introduction with scope, ownership, and maintenance guidance.

The author requested guidance on whether to include an introduction. Adding one helps set expectations and governance signals (update cadence, owners, 2FA, access). Place before the first section.

Apply (insert at top):

+# AsyncAPI Initiative Inventory
+
+This document inventories accounts, tools, services, and recurring payments used by the AsyncAPI Initiative. It is intended to be public and maintained by the community.
+
+- Purpose: transparency, governance, and easier onboarding/offboarding.
+- Update cadence: review quarterly or when ownership changes.
+- Ownership model: prefer role-based access, at least two admins per critical service, and mandatory 2FA where supported.
+- Escalation: when an owner is unavailable, escalate via TSC.
+

If you’d like, I can open a follow-up PR to add an “Owners/Backup” column per section.

---

20-22: Replace bare email strings with mailto links (optional).

Improves UX while keeping content unchanged.

Apply:

-    - info@asyncapi.io (used for contact with partners/sponsors and for security reports)
-    - press@asyncapi.io (status unknown; legacy address)
-    - bot@asyncapi.io and alias bot+eve@asyncapi.io (used by two AsyncAPI GitHub bot accounts)
+    - <mailto:info@asyncapi.io> (partners/sponsors contact and security reports)
+    - <mailto:press@asyncapi.io> (status unknown; legacy address)
+    - <mailto:bot@asyncapi.io> and alias <mailto:bot+eve@asyncapi.io> (used by two AsyncAPI GitHub bot accounts)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 25e9456 and 26f19b3.

📒 Files selected for processing (1)

• docs/020-governance-and-policies/initiative-inventory.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/020-governance-and-policies/initiative-inventory.md

[grammar] ~3-~3: There might be a mistake here.
Context: ...cts: https://opencollective.com/asyncapi - Linux Foundation Crowdfunding: https://c...

(QB_NEW_EN)

---

[grammar] ~4-~4: There might be a mistake here.
Context: ...fx.linuxfoundation.org/projects/asyncapi - GitHub Sponsors: https://github.com/spon...

(QB_NEW_EN)

---

[grammar] ~11-~11: There might be a mistake here.
Context: ...aged by Linux Foundation - asyncapi.com - asyncapi.org ## Email - Google Workspa...

(QB_NEW_EN)

---

[grammar] ~19-~19: There might be a mistake here.
Context: ...n: asyncapi.io - used email addresses: - info@asyncapi.io (used for contact with ...

(QB_NEW_EN)

---

[grammar] ~20-~20: There might be a mistake here.
Context: ...tners/sponsors and for security reports) - press@asyncapi.io (not sure what the sta...

(QB_NEW_EN)

---

[grammar] ~21-~21: There might be a mistake here.
Context: ...status is, never accessed it, old email) - bot@asyncapi.io and alias bot+eve@asynca...

(QB_NEW_EN)

---

[grammar] ~22-~22: There might be a mistake here.
Context: ...sed for two AsyncAPI GitHub bot accounts - Mailjet: used for emailing TSC members t...

(QB_NEW_EN)

---

[grammar] ~23-~23: There might be a mistake here.
Context: ...ers to remind them they did not vote yet - Mailchimp: - owned by Fran - used fo...

(QB_NEW_EN)

---

[grammar] ~30-~30: There might be a mistake here.
Context: ... - Main Org: https://github.com/asyncapi - Org with archived repos: https://github....

(QB_NEW_EN)

---

[grammar] ~31-~31: There might be a mistake here.
Context: ...tps://github.com/asyncapi-archived-repos - Bots: https://github.com/asyncapi-bot an...

(QB_NEW_EN)

---

[grammar] ~36-~36: There might be a mistake here.
Context: ...### Others - SonarCloud for PR scanning - CodeRabbit for PR scanning - CodeCov for...

(QB_NEW_EN)

---

[grammar] ~37-~37: There might be a mistake here.
Context: ...PR scanning - CodeRabbit for PR scanning - CodeCov for PR test coverage scanning ...

(QB_NEW_EN)

---

[grammar] ~47-~47: There might be a mistake here.
Context: ...syncapi/website) and conference website - Netlify: Our additional open source plan...

(QB_NEW_EN)

---

[uncategorized] ~48-~48: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ence-website) - Netlify: Our additional open source plan gives basic stats too - [LFX Insig...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~53-~53: There might be a mistake here.
Context: ... Managers (TBD) For packages/libraries: - npm (JS and TS ...

(QB_NEW_EN)

---

[grammar] ~55-~55: There might be a mistake here.
Context: ...ps://github.com/derberg - Maven Central (Java world): we own com.asyncapi nam...

(QB_NEW_EN)

---

[style] ~56-~56: This phrase is redundant. Consider writing “point” or “time”.
Context: ...y LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discu...

(MOMENT_IN_TIME)

---

[grammar] ~58-~58: There might be a mistake here.
Context: ...t-sdk is not migrated atm. For plugins: - [VisualStudio Marketplace](https://market...

(QB_NEW_EN)

---

[grammar] ~59-~59: There might be a mistake here.
Context: ...github.com/asyncapi/vs-asyncapi-preview in automated way - [Open VSX Registry](htt...

(QB_NEW_EN)

---

[grammar] ~60-~60: There might be a mistake here.
Context: ...github.com/asyncapi/vs-asyncapi-preview in automated way - [JetBrains](https://plu...

(QB_NEW_EN)

---

[grammar] ~61-~61: There might be a mistake here.
Context: ....jetbrains.com/plugin/15673-asyncapi#): Not official account to publish https://git...

(QB_NEW_EN)

---

[grammar] ~61-~61: There might be a mistake here.
Context: ...thub.com/asyncapi/jasyncapi-idea-plugin in manual way. Atm https://github.com/Paki...

(QB_NEW_EN)

---

[grammar] ~61-~61: Ensure spelling is correct
Context: ...pi/jasyncapi-idea-plugin in manual way. Atm https://github.com/Pakisan takes care o...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~65-~65: There might be a mistake here.
Context: ...g goal is to have dedicated subprojects in Open Collective platform to secure fund...

(QB_NEW_EN)

---

[uncategorized] ~67-~67: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...): hired through official contract with Open Source Collective (on our behalf) to do commun...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~68-~68: There might be a mistake here.
Context: ...sh](https://github.com/aeworxet): makes sure AsyncAPI Bounty program runs smoothly, ...

(QB_NEW_EN)

---

[grammar] ~69-~69: There might be a mistake here.
Context: ...ami](https://github.com/iambami): hired through official contract with Open Source Coll...

(QB_NEW_EN)

---

[uncategorized] ~69-~69: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...): hired through official contract with Open Source Collective (on our behalf) to do commun...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~74-~74: There might be a mistake here.
Context: ...ttps://www.linkedin.com/company/asyncapi - X: https://x.com/AsyncAPISpec - Mastodon...

(QB_NEW_EN)

---

[grammar] ~75-~75: There might be a mistake here.
Context: ...asyncapi - X: https://x.com/AsyncAPISpec - Mastodon: https://fosstodon.org/@AsyncAP...

(QB_NEW_EN)

---

[grammar] ~76-~76: There might be a mistake here.
Context: ...don: https://fosstodon.org/@AsyncAPISpec - Twitch: https://www.twitch.tv/asyncapi ...

(QB_NEW_EN)

🪛 markdownlint-cli2 (0.17.2)

docs/020-governance-and-policies/initiative-inventory.md

3-3: Bare URL used

(MD034, no-bare-urls)

---

4-4: Bare URL used

(MD034, no-bare-urls)

---

5-5: Bare URL used

(MD034, no-bare-urls)

---

20-20: Bare URL used

(MD034, no-bare-urls)

---

21-21: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

30-30: Bare URL used

(MD034, no-bare-urls)

---

31-31: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

42-42: Bare URL used

(MD034, no-bare-urls)

---

54-54: Bare URL used

(MD034, no-bare-urls)

---

55-55: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

59-59: Bare URL used

(MD034, no-bare-urls)

---

60-60: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

67-67: Bare URL used

(MD034, no-bare-urls)

---

68-68: Bare URL used

(MD034, no-bare-urls)

---

69-69: Bare URL used

(MD034, no-bare-urls)

---

74-74: Bare URL used

(MD034, no-bare-urls)

---

75-75: Bare URL used

(MD034, no-bare-urls)

---

76-76: Bare URL used

(MD034, no-bare-urls)

---

77-77: Bare URL used

(MD034, no-bare-urls)

---

90-90: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (1)

docs/020-governance-and-policies/initiative-inventory.md (1)

73-73: Optional: add purchase/renewal month for Buffer.

Helps with budgeting and renewal tracking.

Would you like to include the renewal month (e.g., “renews in March”) here for easier tracking?

[coderabbitai]

Actionable comments posted: 0

♻️ Duplicate comments (1)

docs/020-governance-and-policies/initiative-inventory.md (1)

58-62: Finish phrasing fix: “in automated way” → “automatically”.

Line 59 was fixed; line 60 still uses the old phrasing.

- [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview in automated way
+ [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview automatically

🧹 Nitpick comments (12)

docs/020-governance-and-policies/initiative-inventory.md (12)

1-6: Add a title/intro and fix bare URLs in the opening section.

• Add an H1 and short intro for context (author asked if an intro is needed).
• Convert bare URLs to markdown links (markdownlint MD034).

+# AsyncAPI Initiative Asset Inventory
+
+Public inventory of accounts, tools, and services used by the AsyncAPI Initiative, with notes on ownership, renewal cadence, and usage. If you spot inaccuracies, open a PR or contact the TSC.
+
 ## Payment/Donations
 
-- Open Collective and multiple sub-projects: https://opencollective.com/asyncapi
-- Linux Foundation Crowdfunding: https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi
-- GitHub Sponsors: https://github.com/sponsors/asyncapi
+- Open Collective and multiple subprojects: [opencollective.com/asyncapi](https://opencollective.com/asyncapi)
+- Linux Foundation Crowdfunding: [crowdfunding.lfx.linuxfoundation.org/projects/asyncapi](https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi)
+- GitHub Sponsors: [github.com/sponsors/asyncapi](https://github.com/sponsors/asyncapi)

---

9-13: Minor grammar: add article to “Linux Foundation” and consider a colon.

-Managed by Linux Foundation
+Managed by the Linux Foundation:

---

16-27: Tighten wording; clarify unknown mailbox status; fix phrasing.

• Prefer “Owned by … (admin)” style for consistency.
• Avoid uncertainty in public docs; either mark as “unknown—needs verification” or deprecate.
• Minor grammar fixes.

 - Google Workspace:
-  - owned by Fran
+  - Owned by Fran (primary admin)
   - connected domain: asyncapi.io
   - used email addresses:
-    - info@asyncapi.io (used for contact with partners/sponsors and for security reports)
-    - press@asyncapi.io (not sure what the status is, never accessed it, old email)
-    - bot@asyncapi.io and alias bot+eve@asyncapi.io used for two AsyncAPI GitHub bot accounts
+    - info@asyncapi.io (used for partner/sponsor contacts and security reports)
+    - press@asyncapi.io (status unknown; likely deprecated—needs verification)
+    - bot@asyncapi.io and alias bot+eve@asyncapi.io (used by two AsyncAPI GitHub bot accounts)
 - Mailjet: used for emailing TSC members to remind them they did not vote yet
 - Mailchimp:
-  - owned by Fran
-  - used for [newsletter](https://www.asyncapi.com/en/newsletter) and a separate mailing list for [TSC notifications](https://www.asyncapi.com/community/tsc)
+  - Owned by Fran
+  - Used for the [newsletter](https://www.asyncapi.com/en/newsletter) and a separate mailing list for [TSC notifications](https://www.asyncapi.com/community/tsc)

Action: Please confirm the status of press@asyncapi.io and either mark it deprecated or provide its intended use.

---

34-39: Linkify tools and fix Codecov capitalization.

Also unify descriptions.

-### Others
-
-- SonarCloud for PR scanning
-- CodeRabbit for PR scanning
-- CodeCov for PR test coverage scanning
+### Other tooling
+
+- [SonarCloud](https://sonarcloud.io/) for PR scanning
+- [CodeRabbit](https://coderabbit.ai/) for PR code reviews
+- [Codecov](https://about.codecov.io/) for PR test coverage reporting

---

42-44: Tighten deployment phrasing and add link.

-- DigitalOcean: for deployment of https://github.com/asyncapi/server-api. Renewal is needed every year.
+- DigitalOcean: hosts https://github.com/asyncapi/server-api. Renews annually.
 - Netlify: for [website](https://github.com/asyncapi/website), [conference website](https://github.com/asyncapi/conference-website), and [studio](https://github.com/asyncapi/studio) deployments.

---

47-50: Minor grammar/hyphenation; clarify Netlify note.

 - [Google Analytics](https://analytics.google.com/analytics/web/#/p271857523) for [website](https://github.com/asyncapi/website) and [conference website](https://github.com/asyncapi/conference-website)
-- Netlify: Our additional open source plan gives basic stats too
+- Netlify: Our additional open-source plan provides basic stats as well
 - [LFX Insights](https://lfx.linuxfoundation.org/tools/insights/): Lots of GitHub-stats about the org. We can also manage some of the info.

---

51-57: Clean up phrasing; avoid slang; reduce redundancy.

• “some point in time” → “some point”
• “atm” → “currently”
• Slightly smoother Maven/NuGet wording.

 For packages/libraries:
 - [npm](https://www.npmjs.com/) (JS and TS world): we own `@asyncapi` scope. Publishing is automated, and deprecation is manually done by https://github.com/derberg
-- [Maven Central](https://central.sonatype.com/) (Java world): we own `com.asyncapi` namespace. Manual publishing done by https://github.com/Pakisan
-- [NuGet](https://www.nuget.org/) (.NET world): `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discussions/1804. We have our account and https://github.com/asyncapi/saunter is published there manually. A project like https://github.com/asyncapi/net-sdk is not migrated atm.
+- [Maven Central](https://central.sonatype.com/) (Java world): we own the `com.asyncapi` namespace. Publishing is manual (by https://github.com/Pakisan).
+- [NuGet](https://www.nuget.org/) (.NET world): the `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point: https://github.com/orgs/asyncapi/discussions/1804. We have our account and https://github.com/asyncapi/saunter is published there manually. A project like https://github.com/asyncapi/net-sdk is not migrated currently.

---

72-79: Minor grammar and add link for Buffer.

-- Buffer: we pay for it $480 once a year. Used to post in one place and send posts to all social media
+- [Buffer](https://buffer.com/): $480 annually. Used to post centrally and distribute to all social media channels.
 - LinkedIn: https://www.linkedin.com/company/asyncapi
 - X: https://x.com/AsyncAPISpec
 - Mastodon: https://fosstodon.org/@AsyncAPISpec
 - Twitch: https://www.twitch.tv/asyncapi

---

80-83: Slack line reads a bit informal; tighten wording.

-- Slack: Pro Plan for free. We don't need to renew anything.
+- Slack: Free Pro Plan (nonprofit). No renewal required.

---

86-88: Meeting tools: small style improvements.

 - [Restream](https://restream.io/): Streaming to different social media channels. Free pro access. Needs renewal every year.
-- Zoom: Paid service. We approve it as part of the budget once a year.
+- Zoom: Paid service. Approved annually as part of the budget.

---

95-96: Optional: add a one-liner on Attio usage.

Clarifies scope for readers unfamiliar with the tool.

-- Attio: https://attio.com/
+- Attio: https://attio.com/ (CRM for partners, sponsors, and contacts)

---

93-96: Add a short maintenance section at the end.

Helps keep the inventory current and assign accountability (author asked what metadata to add).

Proposed addition after this section:

## Maintenance

- Review cadence: quarterly, before budget planning.
- Maintainers: TSC (primary), Community Manager (backup).
- Change control: PR with at least one TSC approval.
- Please annotate each entry with:
  - Owner/admin (role + person)
  - Access model (SSO/OAuth, org-managed, personal)
  - Renewal cadence and budget line (if any)
  - Backup owner/failsafe
  - Notes (automation, links to GitHub Actions, etc.)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 26f19b3 and d662504.

📒 Files selected for processing (1)

• docs/020-governance-and-policies/initiative-inventory.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/020-governance-and-policies/initiative-inventory.md

[grammar] ~3-~3: There might be a mistake here.
Context: ...cts: https://opencollective.com/asyncapi - Linux Foundation Crowdfunding: https://c...

(QB_NEW_EN)

---

[grammar] ~4-~4: There might be a mistake here.
Context: ...fx.linuxfoundation.org/projects/asyncapi - GitHub Sponsors: https://github.com/spon...

(QB_NEW_EN)

---

[grammar] ~9-~9: There might be a mistake here.
Context: .../sponsors/asyncapi ## Domains Managed by Linux Foundation - asyncapi.com - asyn...

(QB_NEW_EN)

---

[grammar] ~11-~11: There might be a mistake here.
Context: ...aged by Linux Foundation - asyncapi.com - asyncapi.org ## Email - Google Workspa...

(QB_NEW_EN)

---

[grammar] ~19-~19: There might be a mistake here.
Context: ...n: asyncapi.io - used email addresses: - info@asyncapi.io (used for contact with ...

(QB_NEW_EN)

---

[grammar] ~20-~20: There might be a mistake here.
Context: ...tners/sponsors and for security reports) - press@asyncapi.io (not sure what the sta...

(QB_NEW_EN)

---

[grammar] ~21-~21: There might be a mistake here.
Context: ...status is, never accessed it, old email) - bot@asyncapi.io and alias bot+eve@asynca...

(QB_NEW_EN)

---

[grammar] ~22-~22: There might be a mistake here.
Context: ...sed for two AsyncAPI GitHub bot accounts - Mailjet: used for emailing TSC members t...

(QB_NEW_EN)

---

[grammar] ~23-~23: There might be a mistake here.
Context: ...ers to remind them they did not vote yet - Mailchimp: - owned by Fran - used fo...

(QB_NEW_EN)

---

[grammar] ~30-~30: There might be a mistake here.
Context: ... - Main Org: https://github.com/asyncapi - Org with archived repos: https://github....

(QB_NEW_EN)

---

[grammar] ~31-~31: There might be a mistake here.
Context: ...tps://github.com/asyncapi-archived-repos - Bots: https://github.com/asyncapi-bot an...

(QB_NEW_EN)

---

[grammar] ~36-~36: There might be a mistake here.
Context: ...### Others - SonarCloud for PR scanning - CodeRabbit for PR scanning - CodeCov for...

(QB_NEW_EN)

---

[grammar] ~37-~37: There might be a mistake here.
Context: ...PR scanning - CodeRabbit for PR scanning - CodeCov for PR test coverage scanning ...

(QB_NEW_EN)

---

[grammar] ~47-~47: There might be a mistake here.
Context: ...syncapi/website) and conference website - Netlify: Our additional open source plan...

(QB_NEW_EN)

---

[uncategorized] ~48-~48: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ence-website) - Netlify: Our additional open source plan gives basic stats too - [LFX Insig...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~53-~53: There might be a mistake here.
Context: ... Managers (TBD) For packages/libraries: - npm (JS and TS ...

(QB_NEW_EN)

---

[grammar] ~55-~55: There might be a mistake here.
Context: ...ps://github.com/derberg - Maven Central (Java world): we own com.asyncapi nam...

(QB_NEW_EN)

---

[style] ~56-~56: This phrase is redundant. Consider writing “point” or “time”.
Context: ...y LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discu...

(MOMENT_IN_TIME)

---

[grammar] ~58-~58: There might be a mistake here.
Context: ...t-sdk is not migrated atm. For plugins: - [Visual Studio Marketplace](https://marke...

(QB_NEW_EN)

---

[grammar] ~60-~60: There might be a mistake here.
Context: ...github.com/asyncapi/vs-asyncapi-preview in automated way - [JetBrains](https://plu...

(QB_NEW_EN)

---

[grammar] ~65-~65: There might be a mistake here.
Context: ...g goal is to have dedicated subprojects in Open Collective platform to secure fund...

(QB_NEW_EN)

---

[uncategorized] ~67-~67: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...): hired through official contract with Open Source Collective (on our behalf) to do commun...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~68-~68: There might be a mistake here.
Context: ...sh](https://github.com/aeworxet): makes sure AsyncAPI Bounty program runs smoothly, ...

(QB_NEW_EN)

---

[grammar] ~69-~69: There might be a mistake here.
Context: ...ami](https://github.com/iambami): hired through official contract with Open Source Coll...

(QB_NEW_EN)

---

[uncategorized] ~69-~69: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...): hired through official contract with Open Source Collective (on our behalf) to do commun...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~75-~75: There might be a mistake here.
Context: ...ttps://www.linkedin.com/company/asyncapi - X: https://x.com/AsyncAPISpec - Mastodon...

(QB_NEW_EN)

---

[grammar] ~76-~76: There might be a mistake here.
Context: ...asyncapi - X: https://x.com/AsyncAPISpec - Mastodon: https://fosstodon.org/@AsyncAP...

(QB_NEW_EN)

---

[grammar] ~77-~77: There might be a mistake here.
Context: ...don: https://fosstodon.org/@AsyncAPISpec - Twitch: https://www.twitch.tv/asyncapi ...

(QB_NEW_EN)

🪛 markdownlint-cli2 (0.17.2)

docs/020-governance-and-policies/initiative-inventory.md

3-3: Bare URL used

(MD034, no-bare-urls)

---

4-4: Bare URL used

(MD034, no-bare-urls)

---

5-5: Bare URL used

(MD034, no-bare-urls)

---

20-20: Bare URL used

(MD034, no-bare-urls)

---

21-21: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

30-30: Bare URL used

(MD034, no-bare-urls)

---

31-31: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

42-42: Bare URL used

(MD034, no-bare-urls)

---

54-54: Bare URL used

(MD034, no-bare-urls)

---

55-55: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

59-59: Bare URL used

(MD034, no-bare-urls)

---

60-60: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

67-67: Bare URL used

(MD034, no-bare-urls)

---

68-68: Bare URL used

(MD034, no-bare-urls)

---

69-69: Bare URL used

(MD034, no-bare-urls)

---

75-75: Bare URL used

(MD034, no-bare-urls)

---

76-76: Bare URL used

(MD034, no-bare-urls)

---

77-77: Bare URL used

(MD034, no-bare-urls)

---

78-78: Bare URL used

(MD034, no-bare-urls)

---

91-91: Bare URL used

(MD034, no-bare-urls)

---

95-95: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (3)

docs/020-governance-and-policies/initiative-inventory.md (3)

30-33: GitHub orgs and bots list looks good.

Clear and accurate.

---

67-71: Ace payment breakdown fix looks correct.

“$1k + $1k = $2k” is now clear and consistent; tone and grammar improved.

---

68-68: Confirm bounty cadence and amount wording.

“organizes 4 rounds each quarter” reads like 16 rounds per year; please confirm this is intended, and whether $400 is “per round”.

If correct, consider making it explicit:

- We pay $400 for each round.
+ We pay $400 per round (4 rounds per quarter).

[derberg]

@fmvilas @hguerrero @thulieblack please have a look and share if something more is needed

[thulieblack]

do we need to add Spotify as well? Also, the AsyncAPI Brand Account (one from Google Workspace) and Google Drive maybe this falls under the Google Workspace, aside it looks good

[coderabbitai]

Actionable comments posted: 0

♻️ Duplicate comments (1)

docs/020-governance-and-policies/initiative-inventory.md (1)

60-60: Grammar: “in automated way” → “automatically”.

Matches nearby phrasing.

- - [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview in automated way
+ - [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview automatically

🧹 Nitpick comments (13)

docs/020-governance-and-policies/initiative-inventory.md (13)

3-5: Replace bare URLs with markdown links (lint: MD034).

Make links clickable with labels.

- - Open Collective and multiple sub-projects: https://opencollective.com/asyncapi
- - Linux Foundation Crowdfunding: https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi
- - GitHub Sponsors: https://github.com/sponsors/asyncapi
+ - Open Collective and multiple sub-projects: [opencollective.com/asyncapi](https://opencollective.com/asyncapi)
+ - Linux Foundation Crowdfunding: [crowdfunding.lfx.linuxfoundation.org/projects/asyncapi](https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi)
+ - GitHub Sponsors: [github.com/sponsors/asyncapi](https://github.com/sponsors/asyncapi)

---

16-23: Expand Google Workspace details and note shared ownership.

Add Drive/Brand Account, clarify ownership backup.

 - Google Workspace:
-  - owned by Fran
+  - owned by Fran (ensure at least one additional admin for redundancy)
   - connected domain: asyncapi.io
   - used email addresses:
     - info@asyncapi.io (used for contact with partners/sponsors and for security reports)
     - press@asyncapi.io (not sure what the status is, never accessed it, old email)
     - bot@asyncapi.io and alias bot+eve@asyncapi.io are used for two AsyncAPI GitHub bot accounts
+  - Google Drive: shared storage for community assets (confirm primary folders/owners)
+  - YouTube Brand Account: used for channel management (see Video)

---

30-33: Linkify orgs and briefly describe bots.

Improves clarity and fixes MD034.

-- Main Org: https://github.com/asyncapi
-- Org with archived repos: https://github.com/asyncapi-archived-repos
-- Bots: https://github.com/asyncapi-bot and https://github.com/asyncapi-bot-eve used in GitHub Actions automation
+- Main Org: [github.com/asyncapi](https://github.com/asyncapi)
+- Org with archived repos: [github.com/asyncapi-archived-repos](https://github.com/asyncapi-archived-repos)
+- Bots: [asyncapi-bot](https://github.com/asyncapi-bot) and [asyncapi-bot-eve](https://github.com/asyncapi-bot-eve) for GitHub Actions automation (token/secrets managed in org).

---

36-39: Add links to scanning services.

Tiny doc quality win.

-- SonarCloud for PR scanning
-- CodeRabbit for PR scanning
-- CodeCov for PR test coverage scanning
+- [SonarCloud](https://sonarcloud.io/organizations/asyncapi) for PR scanning
+- [CodeRabbit](https://github.com/apps/coderabbitai) for PR scanning
+- [Codecov](https://app.codecov.io/gh/asyncapi) for PR test coverage scanning

---

42-44: Add ownership/billing/renewal notes for deployments.

Who pays, renewal date, and access help operational continuity.

- - DigitalOcean: for deployment of https://github.com/asyncapi/server-api. Renewal is needed every year.
+ - DigitalOcean: hosts [server-api](https://github.com/asyncapi/server-api). Annual renewal; note billing owner and backup admin.
- - Netlify: for [website](https://github.com/asyncapi/website), [conference website](https://github.com/asyncapi/conference-website), and [studio](https://github.com/asyncapi/studio) deployments.
+ - Netlify: deploys [website](https://github.com/asyncapi/website), [conference website](https://github.com/asyncapi/conference-website), and [studio](https://github.com/asyncapi/studio). Note billing owner and backup admin.

---

47-50: Avoid deep links to admin dashboards; use neutral labels.

Public doc shouldn’t expose internal property URLs.

-- [Google Analytics](https://analytics.google.com/analytics/web/#/p271857523) for [website](https://github.com/asyncapi/website) and [conference website](https://github.com/asyncapi/conference-website)
+- Google Analytics (for website and conference website; property ID on file)

---

51-51: Drop “(TBD)” from section title.

Section already populated.

-## Package Managers (TBD)
+## Package Managers

---

54-56: Minor wording and link fixes; avoid slang “atm”.

Also fixes MD034 on bare URLs.

- - [npm](https://www.npmjs.com/) (JS and TS world): we own `@asyncapi` scope. Publishing is automated, and deprecation is manually done by https://github.com/derberg
+ - [npm](https://www.npmjs.com/) (JS/TS): we own `@asyncapi`. Publishing is automated; deprecations handled manually by [@derberg](https://github.com/derberg)
- - [Maven Central](https://central.sonatype.com/) (Java world): we own `com.asyncapi` namespace. Manual publishing done by https://github.com/Pakisan
+ - [Maven Central](https://central.sonatype.com/) (Java): we own `com.asyncapi`. Manual publishing by [@Pakisan](https://github.com/Pakisan)
- - [NuGet](https://www.nuget.org/) (.NET world): `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discussions/1804. We have our account and https://github.com/asyncapi/saunter is published there manually. A project like https://github.com/asyncapi/net-sdk is not migrated atm.
+ - [NuGet](https://www.nuget.org/) (.NET): `asyncapi` prefix is reserved by LEGO (see [discussion](https://github.com/orgs/asyncapi/discussions/1804)). We have an account; [saunter](https://github.com/asyncapi/saunter) is published manually. A project like [net-sdk](https://github.com/asyncapi/net-sdk) is not migrated currently.

---

63-71: Compensation transparency: confirm consent and roles.

Publicly listing monthly amounts is OK if everyone consented; also add role titles for resilience.

- - [Thulie](https://github.com/thulieblack): hired through official contract with Open Source Collective (on our behalf) to do community management ($2.5k monthly). Managed through https://opencollective.com/asyncapi/projects/community-manager-budget
+ - [Thulie](https://github.com/thulieblack) — Community Manager ($2.5k/month, via Open Source Collective). Managed through [Community Manager budget](https://opencollective.com/asyncapi/projects/community-manager-budget)

If any person prefers not to list compensation publicly, replace with “budgeted; details on request.”

---

72-79: Consider adding Spotify and any Brand Account notes.

Reflects review comment from Thulie; add if applicable.

 - Buffer: we pay for it $480 once a year. Used to post in one place and send posts to all social media
 - LinkedIn: https://www.linkedin.com/company/asyncapi
 - X: https://x.com/AsyncAPISpec
 - Mastodon: https://fosstodon.org/@AsyncAPISpec
 - Twitch: https://www.twitch.tv/asyncapi
+ - Spotify: add link/owner if we have a podcast or playlist presence
+ - Brand Account: note which networks are under a shared brand account (owner/backup)

---

80-83: Clarify Slack program and renewal.

Name the program and whether annual re-verification is needed.

- - Slack: Pro Plan for free. We don't need to renew anything.
+ - Slack: Pro plan via Slack program for nonprofits/open source (confirm exact program). Note if annual re-verification is required.

---

86-88: Tighten wording and note ownership.

Small clarity win.

- - [Restream](https://restream.io/): Streaming to different social media channels. Free pro access. Needs renewal every year.
- - Zoom: Paid service. We approve it as part of the budget once a year.
+ - [Restream](https://restream.io/): Multistreaming to social channels. Free Pro access; renew annually. Note account owner and backup.
+ - Zoom: Paid service; approved annually in budget. Note billing owner and backup admin.

---

1-96: Global: convert remaining bare URLs and add a brief intro + last-updated.

• Many MD034 warnings remain; convert bare URLs across the doc to markdown links.
• Add a 1–2 sentence intro explaining scope and audience, and a “Last updated: YYYY‑MM‑DD”.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d662504 and 7124184.

📒 Files selected for processing (1)

• docs/020-governance-and-policies/initiative-inventory.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

docs/020-governance-and-policies/initiative-inventory.md

3-3: Bare URL used

(MD034, no-bare-urls)

---

4-4: Bare URL used

(MD034, no-bare-urls)

---

5-5: Bare URL used

(MD034, no-bare-urls)

---

20-20: Bare URL used

(MD034, no-bare-urls)

---

21-21: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

22-22: Bare URL used

(MD034, no-bare-urls)

---

30-30: Bare URL used

(MD034, no-bare-urls)

---

31-31: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

32-32: Bare URL used

(MD034, no-bare-urls)

---

42-42: Bare URL used

(MD034, no-bare-urls)

---

54-54: Bare URL used

(MD034, no-bare-urls)

---

55-55: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

56-56: Bare URL used

(MD034, no-bare-urls)

---

59-59: Bare URL used

(MD034, no-bare-urls)

---

60-60: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

67-67: Bare URL used

(MD034, no-bare-urls)

---

68-68: Bare URL used

(MD034, no-bare-urls)

---

69-69: Bare URL used

(MD034, no-bare-urls)

---

75-75: Bare URL used

(MD034, no-bare-urls)

---

76-76: Bare URL used

(MD034, no-bare-urls)

---

77-77: Bare URL used

(MD034, no-bare-urls)

---

78-78: Bare URL used

(MD034, no-bare-urls)

---

91-91: Bare URL used

(MD034, no-bare-urls)

---

95-95: Bare URL used

(MD034, no-bare-urls)

[thulieblack]

@derberg please add the frontmatter 😁

[derberg]

@thulieblack added, wdyt?

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docs/020-governance-and-policies/initiative-inventory.md (1)

8-101: Fix MD034 (bare URLs): convert bare URLs to descriptive markdown links or autolinks

Multiple bare URLs remain in docs/020-governance-and-policies/initiative-inventory.md — convert the URLs on lines 8, 9, 10, 35, 36, 37, 47, 59, 60, 61, 64, 65, 66, 72, 73, 74, 80, 81, 82, 83, 96, 100 to text or https://....

Spot‑fix pattern (apply broadly):

- Open Collective and multiple sub-projects: https://opencollective.com/asyncapi
+ Open Collective and multiple sub-projects: [opencollective.com/asyncapi](https://opencollective.com/asyncapi)

To re-scan only bare URLs (ignore already-bracketed or autolinks):

rg -nP '(?<![\(<])https?://[^\s\)\]]+' docs/020-governance-and-policies/initiative-inventory.md

🧹 Nitpick comments (10)

docs/020-governance-and-policies/initiative-inventory.md (10)

2-2: Title clarity and capitalization

Recommend a clearer, style‑consistent title.

-title: List Of People and Assets AsyncAPI Depends On
+title: Inventory of People and Assets the AsyncAPI Initiative Depends On

---

4-6: Add a 1–2 sentence intro for scope/context

Briefly state purpose, audience, and maintenance ownership.

 ---
 
+This public inventory lists the accounts, tools, and paid roles the AsyncAPI Initiative relies on, including ownership, budgets, and renewal notes. It is maintained by the TSC and community maintainers to support transparency and continuity.
+
 ## Payment/Donations

---

21-31: Google Workspace: prefer role-based ownership; add Drive/Brand Account note

• Replace personal “owned by” with admin/role to reduce bus factor.
• Consider adding Google Drive details and cross‑reference the YouTube Brand Account.

Proposed tweak:

-  - owned by Fran
+  - primary admin: Fran (use role-based admin where possible)
+  - shared assets: Gmail, Calendar, Meet, Drive (shared drives for long‑term storage; document admin/backup owners)

Would you like to also add a note in the Video section that YouTube runs under a Google Brand Account?

---

41-43: Typo: “CodeCov” → “Codecov”

Brand capitalization.

-- CodeCov for PR test coverage scanning
+- Codecov for PR test coverage scanning

---

53-54: Wording/style

Tighten phrasing.

-- Netlify: Our additional open source plan gives basic stats too
+- Netlify: Our open‑source plan includes basic stats

---

58-61: Consistency and tone; avoid “atm”

Unify phrasing across package managers and remove slang.

- - [npm](https://www.npmjs.com/) (JS and TS world): we own `@asyncapi` scope. Publishing is automated, and deprecation is manually done by https://github.com/derberg
- - [Maven Central](https://central.sonatype.com/) (Java world): we own `com.asyncapi` namespace. Manual publishing done by https://github.com/Pakisan
- - [NuGet](https://www.nuget.org/) (.NET world): `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discussions/1804. We have our account and https://github.com/asyncapi/saunter is published there manually. A project like https://github.com/asyncapi/net-sdk is not migrated atm.
+- [npm](https://www.npmjs.com/) (JS/TS): we own the `@asyncapi` scope. Publishing is automated; deprecations are handled manually by https://github.com/derberg
+- [Maven Central](https://central.sonatype.com/) (Java): we own the `com.asyncapi` namespace. Publishing is manual, currently by https://github.com/Pakisan
+- [NuGet](https://www.nuget.org/) (.NET): the `asyncapi` prefix is reserved by LEGO (issue: https://github.com/orgs/asyncapi/discussions/1804). We have an account and https://github.com/asyncapi/saunter is published manually. A project like https://github.com/asyncapi/net-sdk is not migrated currently.

---

65-65: Leftover phrasing: “in automated way” → “automatically”

Matches line 64.

- - [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview in automated way
+ - [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview automatically

---

70-75: Minor grammar/hyphenation; smoother flow

-People we hire through Open Collective contracts or pay for a specific job to be done in one of our official programs. All costs below are always planned in the budget and approved by TSC. For clarity and better budget planning goal is to have dedicated subprojects in Open Collective platform to secure funding more easily.
+People we hire through Open Collective contracts or pay for specific jobs within our official programs. All costs below are planned in the budget and approved by the TSC. For clarity and better planning, the goal is to have dedicated sub‑projects in the Open Collective platform to secure funding more easily.
@@
-- [Ash](https://github.com/aeworxet): makes sure AsyncAPI Bounty program runs smoothly, organizes 4 rounds each quarter. We pay $400 for each round. We started to manage funding through https://opencollective.com/asyncapi/projects/asyncapi-bounty-program
+- [Ash](https://github.com/aeworxet): ensures the AsyncAPI Bounty program runs smoothly and organizes four rounds each quarter. We pay $400 per round. We started managing funding through https://opencollective.com/asyncapi/projects/asyncapi-bounty-program
@@
-- [Bami](https://github.com/iambami): hired through official contract with Open Source Collective (on our behalf) to do community marketing ($2k monthly). Managed through https://opencollective.com/asyncapi/projects/community-marketing-specialist
+- [Bami](https://github.com/iambami): hired through an official contract with the Open Source Collective (on our behalf) to do community marketing ($2k monthly). Managed through https://opencollective.com/asyncapi/projects/community-marketing-specialist

---

85-88: Slack details

Consider adding the public invite URL and admin/ownership notes.

Example:

• Slack: Free Pro plan via OSS program; public invite: ; workspace admins: .

---

91-93: Meetings: ownership/renewal specifics

Optional: note who holds the Zoom license and renewal month to aid budgeting/continuity.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7124184 and 215c8b0.

📒 Files selected for processing (1)

• docs/020-governance-and-policies/initiative-inventory.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

docs/020-governance-and-policies/initiative-inventory.md

8-8: Bare URL used

(MD034, no-bare-urls)

---

9-9: Bare URL used

(MD034, no-bare-urls)

---

10-10: Bare URL used

(MD034, no-bare-urls)

---

25-25: Bare URL used

(MD034, no-bare-urls)

---

26-26: Bare URL used

(MD034, no-bare-urls)

---

27-27: Bare URL used

(MD034, no-bare-urls)

---

27-27: Bare URL used

(MD034, no-bare-urls)

---

35-35: Bare URL used

(MD034, no-bare-urls)

---

36-36: Bare URL used

(MD034, no-bare-urls)

---

37-37: Bare URL used

(MD034, no-bare-urls)

---

37-37: Bare URL used

(MD034, no-bare-urls)

---

47-47: Bare URL used

(MD034, no-bare-urls)

---

59-59: Bare URL used

(MD034, no-bare-urls)

---

60-60: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

64-64: Bare URL used

(MD034, no-bare-urls)

---

65-65: Bare URL used

(MD034, no-bare-urls)

---

66-66: Bare URL used

(MD034, no-bare-urls)

---

66-66: Bare URL used

(MD034, no-bare-urls)

---

72-72: Bare URL used

(MD034, no-bare-urls)

---

73-73: Bare URL used

(MD034, no-bare-urls)

---

74-74: Bare URL used

(MD034, no-bare-urls)

---

80-80: Bare URL used

(MD034, no-bare-urls)

---

81-81: Bare URL used

(MD034, no-bare-urls)

---

82-82: Bare URL used

(MD034, no-bare-urls)

---

83-83: Bare URL used

(MD034, no-bare-urls)

---

96-96: Bare URL used

(MD034, no-bare-urls)

---

100-100: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (1)

docs/020-governance-and-policies/initiative-inventory.md (1)

77-84: Add Spotify (per review); confirm link

Reviewer requested Spotify. If applicable, add an entry with the canonical URL and who manages it.

Proposed addition:

• Spotify: <add official show/profile URL>; used for podcast distribution; managed by <owner/role>.

[fmvilas]

Added some suggestions.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (11)

docs/020-governance-and-policies/initiative-inventory.md (11)

8-10: Resolve markdownlint MD034: wrap bare URLs.

Apply:

-- Open Collective and multiple sub-projects: https://opencollective.com/asyncapi
-- Linux Foundation Crowdfunding: https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi
-- GitHub Sponsors: https://github.com/sponsors/asyncapi
+- Open Collective and multiple sub-projects: <https://opencollective.com/asyncapi>
+- Linux Foundation Crowdfunding: <https://crowdfunding.lfx.linuxfoundation.org/projects/asyncapi>
+- GitHub Sponsors: <https://github.com/sponsors/asyncapi>

---

35-37: Resolve markdownlint MD034: wrap bare URLs.

Apply:

-- Main Org: https://github.com/asyncapi
-- Org with archived repos: https://github.com/asyncapi-archived-repos
-- Bots: https://github.com/asyncapi-bot and https://github.com/asyncapi-bot-eve used in GitHub Actions automation
+- Main Org: <https://github.com/asyncapi>
+- Org with archived repos: <https://github.com/asyncapi-archived-repos>
+- Bots: <https://github.com/asyncapi-bot> and <https://github.com/asyncapi-bot-eve> used in GitHub Actions automation

---

47-47: Resolve markdownlint MD034: wrap bare URL.

Apply:

-- DigitalOcean: for deployment of https://github.com/asyncapi/server-api. Renewal is needed every year.
+- DigitalOcean: for deployment of <https://github.com/asyncapi/server-api>. Renewal is needed every year.

---

72-73: Resolve markdownlint MD034: wrap bare URLs.

Apply:

-- [Thulie](https://github.com/thulieblack): hired through official contract with Open Source Collective (on our behalf) to do community management ($2.5k monthly). Managed through https://opencollective.com/asyncapi/projects/community-manager-budget
-- [Ash](https://github.com/aeworxet): makes sure AsyncAPI Bounty program runs smoothly, organizes 4 rounds/year, one each quarter. We pay $400 for each round. We started to manage funding through https://opencollective.com/asyncapi/projects/asyncapi-bounty-program
+- [Thulie](https://github.com/thulieblack): hired through official contract with Open Source Collective (on our behalf) to do community management ($2.5k monthly). Managed through <https://opencollective.com/asyncapi/projects/community-manager-budget>
+- [Ash](https://github.com/aeworxet): makes sure AsyncAPI Bounty program runs smoothly, organizes 4 rounds/year, one each quarter. We pay $400 for each round. We started to manage funding through <https://opencollective.com/asyncapi/projects/asyncapi-bounty-program>

---

79-83: Resolve markdownlint MD034: wrap bare URLs.

Apply:

-- LinkedIn: https://www.linkedin.com/company/asyncapi
-- X: https://x.com/AsyncAPISpec
-- Mastodon: https://fosstodon.org/@AsyncAPISpec
-- Twitch: https://www.twitch.tv/asyncapi
+- LinkedIn: <https://www.linkedin.com/company/asyncapi>
+- X: <https://x.com/AsyncAPISpec>
+- Mastodon: <https://fosstodon.org/@AsyncAPISpec>
+- Twitch: <https://www.twitch.tv/asyncapi>

---

95-95: Resolve markdownlint MD034: wrap bare URL.

Apply:

-- YouTube: https://www.youtube.com/@AsyncAPI
+- YouTube: <https://www.youtube.com/@AsyncAPI>

---

99-99: Resolve markdownlint MD034: wrap bare URL.

Apply:

-- Attio: https://attio.com/
+- Attio: <https://attio.com/>

---

39-43: Name and link the tooling; add URLs.

Improves clarity and discoverability.

Apply:

-### Others
-
-- SonarCloud for PR scanning
-- CodeRabbit for PR scanning
-- CodeCov for PR test coverage scanning
+### Other services
+
+- [SonarCloud](https://sonarcloud.io/) for PR scanning
+- [CodeRabbit](https://coderabbit.ai/) for PR scanning
+- [Codecov](https://about.codecov.io/) for PR test coverage scanning

---

52-52: Avoid deep-linking to a private GA property.

Use a generic product link; property URLs won’t work for most readers.

Apply:

-- [Google Analytics](https://analytics.google.com/analytics/web/#/p271857523) for [website](https://github.com/asyncapi/website) and [conference website](https://github.com/asyncapi/conference-website)
+- [Google Analytics](https://analytics.google.com/) for [website](https://github.com/asyncapi/website) and [conference website](https://github.com/asyncapi/conference-website)

---

5-6: Add a one-sentence intro for context.

Helps first-time readers understand scope.

Apply:

 
+This page inventories the public-facing assets, accounts, and services the AsyncAPI Initiative relies on, including ownership, usage, and budgeting notes.
 
 ## Payment/Donations

---

47-47: Clarify what “Renewal is needed every year” means.

Is this account billing renewal, credits, or infra lifecycle? A short note would help operations.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 215c8b0 and 7365aee.

📒 Files selected for processing (1)

• docs/020-governance-and-policies/initiative-inventory.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

docs/020-governance-and-policies/initiative-inventory.md

8-8: Bare URL used

(MD034, no-bare-urls)

---

9-9: Bare URL used

(MD034, no-bare-urls)

---

10-10: Bare URL used

(MD034, no-bare-urls)

---

25-25: Bare URL used

(MD034, no-bare-urls)

---

26-26: Bare URL used

(MD034, no-bare-urls)

---

27-27: Bare URL used

(MD034, no-bare-urls)

---

27-27: Bare URL used

(MD034, no-bare-urls)

---

35-35: Bare URL used

(MD034, no-bare-urls)

---

36-36: Bare URL used

(MD034, no-bare-urls)

---

37-37: Bare URL used

(MD034, no-bare-urls)

---

37-37: Bare URL used

(MD034, no-bare-urls)

---

47-47: Bare URL used

(MD034, no-bare-urls)

---

59-59: Bare URL used

(MD034, no-bare-urls)

---

60-60: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

64-64: Bare URL used

(MD034, no-bare-urls)

---

65-65: Bare URL used

(MD034, no-bare-urls)

---

66-66: Bare URL used

(MD034, no-bare-urls)

---

66-66: Bare URL used

(MD034, no-bare-urls)

---

72-72: Bare URL used

(MD034, no-bare-urls)

---

73-73: Bare URL used

(MD034, no-bare-urls)

---

79-79: Bare URL used

(MD034, no-bare-urls)

---

80-80: Bare URL used

(MD034, no-bare-urls)

---

81-81: Bare URL used

(MD034, no-bare-urls)

---

82-82: Bare URL used

(MD034, no-bare-urls)

---

95-95: Bare URL used

(MD034, no-bare-urls)

---

99-99: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (4)

docs/020-governance-and-policies/initiative-inventory.md (4)

1-6: Solid addition; structure and frontmatter look good.

Meets the PR goal to inventory assets. Small polish suggestions follow below.

---

63-66: Wording: “in automated way” → “automatically”.

Consistent with line 63 wording.

Apply:

- - [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview in automated way
+ - [Open VSX Registry](https://open-vsx.org/namespace/asyncapi): We have an official account to publish https://github.com/asyncapi/vs-asyncapi-preview automatically

---

59-61: Fix slang “atm”; wrap bare links in angle brackets.

Keeps tone formal and resolves MD034 for these lines.

Apply:

- - [Maven Central](https://central.sonatype.com/) (Java world): we own `com.asyncapi` namespace. Manual publishing done by https://github.com/Pakisan
- - [NuGet](https://www.nuget.org/) (.NET world): `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point in time: https://github.com/orgs/asyncapi/discussions/1804. We have our account and https://github.com/asyncapi/saunter is published there manually. A project like https://github.com/asyncapi/net-sdk is not migrated atm.
+ - [Maven Central](https://central.sonatype.com/) (Java world): we own `com.asyncapi` namespace. Manual publishing done by <https://github.com/Pakisan>
+ - [NuGet](https://www.nuget.org/) (.NET world): `asyncapi` prefix is already reserved by LEGO. This needs to be solved at some point in time: <https://github.com/orgs/asyncapi/discussions/1804>. We have our account and <https://github.com/asyncapi/saunter> is published there manually. A project like <https://github.com/asyncapi/net-sdk> is not migrated yet.

---

76-83: Confirm whether Spotify should be listed.

A reviewer asked about Spotify; add it here if applicable.

Would you like me to add an entry (with link and usage) under Social Media if Spotify is indeed used?