Skip to content

Conversation

@aminoxix
Copy link
Contributor

@aminoxix aminoxix commented May 25, 2025

Description

  • read & generate mapped data through TSC_BOARD_MEMBER.yaml (ctx: upcoming changes through community) over UserInfo component
  • created a common layout, say, CommunityLayout as a wrapper for Tsc & Board component/page
  • did changes associated with the aforementioned modifications, such as:
    • TSC board members file used on /community/tsc page
    • for ambassadot, redirection link set to the dedicated ambassador page

Related issue(s)

Resolves #4095

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Introduced a new Community Members layout that displays enriched profiles for TSC and Board members, including social links, avatars, and repository details.
    • Added a dedicated Governance Board page with detailed information and external resource links.
    • Updated TSC page to use the new Community Members layout and present static information sections.
    • Added "Board Members" to community navigation with descriptive details and link.
  • Enhancements

    • Extended community member profiles with additional metadata, such as avatar URLs and membership roles.
  • Style

    • Adjusted the order of CSS utility classes in case study cards and generator diagram for improved consistency.
  • Bug Fixes

    • Improved navigation menu with fixed height and horizontal scrolling on medium screens and above for better usability.

@netlify
Copy link

netlify bot commented May 25, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 004f928
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/686bc00a948ebf0008423ac8
😎 Deploy Preview https://deploy-preview-4127--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 25, 2025

"""

Walkthrough

This update introduces a reusable CommunityLayout component to standardize the rendering of community member pages, such as for the TSC or Board. It enriches member data, adds helper components, and updates related pages to use the new layout. Type definitions are extended, and minor class order changes are made in unrelated UI files.

Changes

File(s) Change Summary
components/layout/CommunityLayout.tsx Introduced CommunityLayout component with helper components, member data enrichment, filtering, and dynamic rendering for TSC/Board member pages. Exported Membership enum and relevant types.
pages/community/board.tsx Added new Board component rendering static governance board information within CommunityLayout.
pages/community/tsc.tsx Replaced previous dynamic TSC member rendering with static informational content inside CommunityLayout. Removed all member data processing and interactive elements.
types/pages/community/Community.ts Extended Ambassador and Tsc interfaces with new optional properties for avatar URLs and membership status flags.
components/CaseStudyCard.tsx, pages/tools/generator.tsx Changed the order of Tailwind CSS utility classes in container elements for layout consistency; no logic or structural changes.
components/navigation/FlyoutMenu.tsx Added fixed height and horizontal scroll overflow properties to the Flyout component's container div.
components/navigation/communityItems.tsx Added new community item entry for "Board Members" with icon, title, link, and description.
config/TSC_BOARD_MEMBERS.json Added "isBoardMember": true property to three existing TSC members: Fran Méndez, Thulisile Sibanda, and Hugo Guerrero.

Sequence Diagram(s)

sequenceDiagram
    participant Page
    participant CommunityLayout
    participant MemberData
    participant HelperComponents

    Page->>CommunityLayout: Render with membership type (TSC or BOARD)
    CommunityLayout->>MemberData: Import and enrich member data
    CommunityLayout->>HelperComponents: Render UserInfo, SocialLink, etc.
    CommunityLayout->>Page: Render children and member grid
Loading

Possibly related PRs

Suggested labels

ready-to-merge, area/design

Suggested reviewers

  • akshatnema
  • anshgoyalevil
  • sambhavgupta0705
  • Mayaleeeee
  • devilkiller-ag
  • vishvamsinh28
  • asyncapi-bot-eve

Poem

Hopping through the code so bright,
A layout for the community takes flight!
TSC and Board, together they show,
Member cards in a tidy row.
With avatars, links, and status clear—
This bunny’s proud to engineer!
🐇✨
"""

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@tisoap/[email protected]',
npm warn EBADENGINE required: { node: '>=16', npm: '^8.0.0' },
npm warn EBADENGINE current: { node: 'v24.3.0', npm: '11.4.2' }
npm warn EBADENGINE }
npm error code ERR_SSL_WRONG_VERSION_NUMBER
npm error errno ERR_SSL_WRONG_VERSION_NUMBER
npm error request to https://10.0.0.28:4873/@parcel/watcher-wasm/-/watcher-wasm-2.4.1.tgz failed, reason: C0AC13DEB07F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
npm error
npm error A complete log of this run can be found in: /.npm/_logs/2025-07-07T12_41_42_866Z-debug-0.log


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d572f5a and 004f928.

📒 Files selected for processing (1)
  • pages/community/board.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pages/community/board.tsx
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Test NodeJS PR - macos-13
  • GitHub Check: Test NodeJS PR - windows-latest
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 16

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 027665d and 8c7b909.

📒 Files selected for processing (5)
  • components/layout/CommunityLayout.tsx (1 hunks)
  • pages/community/board.tsx (1 hunks)
  • pages/community/tsc.tsx (2 hunks)
  • types/packages/yaml.d.ts (1 hunks)
  • types/pages/community/Community.ts (2 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
pages/community/board.tsx (3)
types/pages/community/Community.ts (2)
  • Tsc (39-53)
  • Ambassador (19-37)
components/layout/CommunityLayout.tsx (1)
  • CommunityLayout (263-306)
components/typography/TextLink.tsx (1)
  • TextLink (21-42)
pages/community/tsc.tsx (1)
components/layout/CommunityLayout.tsx (1)
  • CommunityLayout (263-306)
🪛 GitHub Actions: PR testing - if Node project
pages/community/board.tsx

[error] 1-1: Prettier formatting error: Delete newline at start of file.


[error] 2-2: simple-import-sort: Imports are not sorted. Run autofix to sort these imports.


[error] 4-4: import/no-extraneous-dependencies: 'js-yaml' should be listed in the project's dependencies. Run 'npm i -S js-yaml' to add it.


[error] 6-6: import/order: Import '../../components/typography/TextLink' should occur after import of '@/components/layout/CommunityLayout'.


[error] 7-7: @typescript-eslint/consistent-type-imports: All imports in the declaration are only used as types. Use 'import type'.


[error] 15-15: Prettier formatting error: Replace multiline props with inline props for 'members' and 'membership'.


[error] 19-19: Prettier formatting error: Replace multiline attributes with inline attributes for className and data-testid.


[error] 24-24: Prettier formatting error: Replace inline text with multiline formatting for 'What is the Governance Board?'.


[error] 26-26: Prettier formatting error: Replace inline text with multiline formatting for governance description.


[error] 34-34: Prettier formatting error: Insert newline indentation.


[error] 38-38: Prettier formatting error: Replace inline text with multiline formatting for 'How can I become a Board Member?'.


[error] 40-40: Prettier formatting error: Replace inline text with multiline formatting for board member eligibility and election cycle.


[error] 47-47: Prettier formatting error: Insert newline indentation.


[error] 51-51: Prettier formatting error: Replace inline text with multiline formatting for 'Board Member Responsibilities'.


[error] 53-53: Prettier formatting error: Replace inline text with multiline formatting for responsibilities description.


[warning] 70-70: require-jsdoc: Missing JSDoc comment.


[error] 76-76: Prettier formatting error: Replace multiline map function with inline formatting.

pages/community/tsc.tsx

[error] 1-1: simple-import-sort: Imports are not sorted. Run autofix to sort these imports.


[error] 2-2: import/order: Import '@/components/layout/CommunityLayout' should occur before import of '../../components/typography/TextLink'.


[error] 9-9: Prettier formatting error: Replace multiline prop 'membership' with inline formatting.


[error] 12-12: Prettier formatting error: Replace multiline attributes with inline attributes for className and data-testid.


[error] 16-66: Prettier formatting errors: Multiple lines contain trailing spaces or incorrect indentation. Delete extra spaces and fix indentation.

components/layout/CommunityLayout.tsx

[error] 4-4: @typescript-eslint/consistent-type-imports: All imports in the declaration are only used as types. Use 'import type'.


[error] 6-11: import/no-useless-path-segments: Useless path segments detected in multiple imports; should be corrected to relative paths.


[error] 13-13: unused-imports/no-unused-imports and no-unused-vars: 'BoardMembersList' is defined but never used.


[error] 56-56: Prettier and quotes: Replace double quotes with single quotes for string 'repos'.


[error] 142-142: Prettier and quotes: Replace double quotes with single quotes for string 'availableForHire'.


[error] 205-205: Prettier and quotes: Replace double quotes with single quotes for string 'repos' and fix multiline formatting.


[error] 250-250: no-use-before-define: 'Membership' was used before it was defined.


[error] 252-252: Prettier formatting error: Missing semicolon insertion.


[error] 256-257: Prettier and quotes: Replace double quotes with single quotes for strings 'TSC' and 'Board'.


[error] 263-263: Prettier formatting error: Replace multiline props with inline formatting for members, children, membership.


[error] 266-266: comma-dangle: Unexpected trailing comma.


[error] 271-271: Prettier and semi: Missing semicolon at end of statement.


[error] 272-272: Prettier formatting error: Replace parentheses formatting for members array.


[error] 277-277: Prettier formatting error: Fix parentheses placement in conditional expression.


[error] 280-280: Prettier formatting error: Replace inline props with multiline props for title, description, image, wide.


[error] 283-289: Prettier formatting error: Insert newlines and fix indentation in JSX elements.

⏰ Context from checks skipped due to timeout of 180000ms (1)
  • GitHub Check: Lighthouse CI
🔇 Additional comments (4)
types/packages/yaml.d.ts (1)

1-5: LGTM! Clean TypeScript declaration for YAML imports.

This module declaration properly enables TypeScript support for importing YAML files. The use of any type is appropriate since YAML content can have various structures.

types/pages/community/Community.ts (2)

33-36: Well-structured interface extensions for Ambassador.

The new optional properties enhance the Ambassador interface to support board membership roles and avatar URLs, aligning with the community layout requirements.


51-52: Good addition of board membership properties to Tsc interface.

The optional board-related properties maintain consistency with the Ambassador interface extensions.

components/layout/CommunityLayout.tsx (1)

272-277:

✅ Verification successful

Verify type safety for member filtering.

The filtering logic assumes properties exist on both TSC and Ambassador types that may not be present.

The filtering logic relies on isTscMember, isBoardMember, and isBoardChair properties. Please verify these properties exist on the imported types.


🏁 Script executed:

#!/bin/bash
# Description: Verify the type definitions contain the required properties for filtering
# Expected: Properties like isTscMember, isBoardMember, isBoardChair should exist

echo "Checking type definitions for required properties..."
ast-grep --pattern 'interface Tsc {
  $$$
}'

ast-grep --pattern 'interface Ambassador {
  $$$
}'

echo "Checking for board member properties..."
rg -A 10 -B 5 "isTscMember|isBoardMember|isBoardChair"

Length of output: 54879


Filtering Logic Type-Safe
Verified that both the Tsc and Ambassador interfaces declare isTscMember, isBoardMember, and isBoardChair (with appropriate optionality), so the current .filter(...) call is fully type-safe. No changes required.

🧰 Tools
🪛 GitHub Actions: PR testing - if Node project

[error] 272-272: Prettier formatting error: Replace parentheses formatting for members array.


[error] 277-277: Prettier formatting error: Fix parentheses placement in conditional expression.

@aminoxix aminoxix marked this pull request as draft May 25, 2025 16:58
@aminoxix
Copy link
Contributor Author

aminoxix commented May 25, 2025

drafting this up, let's wait for the related changes to be merged!

asyncapi-bot and others added 10 commits June 4, 2025 12:38
Co-authored-by: raghav-97 <[email protected]>
Co-authored-by: Rohit <[email protected]>
Co-authored-by: Akshat Nema <[email protected]>
)

* improve UI responsiveness for 'Latest News' section in Community Newsroom

* fix the preetier part

* refactor: standardize quotation marks in Newsroom component

* liniting fix

* lint fix

* lint fix

* fix: correct indentation in Newsroom component

* Remove duplicate tool rendering in ToolsList using Set for unique titles.

* Remove duplicate tool rendering in ToolsList using Set for unique titles.

* Refactor ToolsList component to simplify rendering and remove duplicate tool handling

* removed inline

* fix: correct typo in Twitter link class name

* fix: adjust width of banner container for better responsiveness

---------

Co-authored-by: Akshat Nema <[email protected]>
asyncapi#3845)

Co-authored-by: Sagar Kori <[email protected]>
Co-authored-by: Chan <[email protected]>
Co-authored-by: Sambhav Gupta <[email protected]>
Co-authored-by: Akshat Nema <[email protected]>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

♻️ Duplicate comments (2)
components/layout/CommunityLayout.tsx (2)

50-52: Critical: Fix potential null reference error in avatar URL construction.

The avatar URL construction assumes userData.github is always defined, but it could be undefined after the social links processing, leading to a runtime error.

This issue was identified in previous reviews and still needs to be addressed:

  // add avatar url
  // github redirects to avatar url using `https://www.github.com/<username>.png`
- userData.avatarUrl = `${userData.github}.png`;
+ if (userData.github) {
+   userData.avatarUrl = `${userData.github}.png`;
+ }

188-193: Add null safety for avatar URL display.

The component doesn't handle cases where avatarUrl might be undefined, which could break the UI if the avatar URL construction fails.

        <img
          data-testid='UserInfo-avatar'
-         src={user.avatarUrl}
+         src={user.avatarUrl || '/img/avatars/default.png'}
          alt={user.name}
          className='mx-auto size-20 rounded-full xl:size-28'
        />
🧹 Nitpick comments (1)
components/layout/CommunityLayout.tsx (1)

309-312: Consider accessibility improvement for the members list.

The user list could benefit from additional ARIA attributes to improve screen reader navigation.

          <ul role='list' className='space-y-4 sm:grid sm:grid-cols-2 sm:gap-6 sm:space-y-0 lg:grid-cols-3 lg:gap-8'>
+           <li className='sr-only'>List of {membership} members</li>
            {tscBoardMembers.map((user) => (
              <UserInfo key={user.github} user={user} />
            ))}
            <QuestionCard />
          </ul>
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8053b66 and 2828eea.

📒 Files selected for processing (1)
  • components/layout/CommunityLayout.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 180000ms (1)
  • GitHub Check: Lighthouse CI
🔇 Additional comments (1)
components/layout/CommunityLayout.tsx (1)

260-268: Good: Enum and interface definitions are properly structured.

The Membership enum is now correctly defined before the interface that uses it, and the interface is clean and well-typed.

@aminoxix
Copy link
Contributor Author

@derberg: btw, hyperlink styling pushed

Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you please do last change - manually update source json file, make 3 random people board members, and one of them a chair - and push to PR, so I can see the board page, how it will look like with available data

@aminoxix
Copy link
Contributor Author

aminoxix commented Jun 12, 2025

can you please do last change - manually update source json file, make 3 random people board members, and one of them a chair - and push to PR, so I can see the board page, how it will look like with available data

please check the screenshots:

Screenshot 2025-06-12 at 2 41 33 PM Screenshot 2025-06-12 at 2 41 44 PM Screenshot 2025-06-12 at 2 41 56 PM

chairperson:
Screenshot 2025-06-16 at 3 10 54 PM

@aminoxix aminoxix requested a review from derberg June 12, 2025 16:18
@derberg
Copy link
Member

derberg commented Jun 16, 2025

ready to merge
we just need to wait until board is elected to merge this one

Copy link
Collaborator

@TRohit20 TRohit20 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great work @aminoxix , thank you so much.

We can merge this after we have the GB elections concluded next month by adding the elected members. :)

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fa26bfc and d572f5a.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • config/TSC_BOARD_MEMBERS.json (4 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: asyncapi-bot
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch
Learnt from: aminoxix
PR: asyncapi/website#4127
File: components/layout/CommunityLayout.tsx:179-179
Timestamp: 2025-06-10T06:27:25.419Z
Learning: In AsyncAPI's community data structure, ambassadors and TSC members are guaranteed to have GitHub accounts. The `github` field is required in both `Ambassador` and `Tsc` interfaces, and the data processing in `addAdditionalUserInfo()` converts GitHub usernames to full URLs, ensuring safe string operations when extracting usernames from URLs.
config/TSC_BOARD_MEMBERS.json (1)
Learnt from: aminoxix
PR: asyncapi/website#4127
File: components/layout/CommunityLayout.tsx:179-179
Timestamp: 2025-06-10T06:27:25.419Z
Learning: In AsyncAPI's community data structure, ambassadors and TSC members are guaranteed to have GitHub accounts. The `github` field is required in both `Ambassador` and `Tsc` interfaces, and the data processing in `addAdditionalUserInfo()` converts GitHub usernames to full URLs, ensuring safe string operations when extracting usernames from URLs.
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
  • GitHub Check: Redirect rules - asyncapi-website
  • GitHub Check: Header rules - asyncapi-website
  • GitHub Check: Pages changed - asyncapi-website
  • GitHub Check: Test NodeJS PR - macos-13
  • GitHub Check: Test NodeJS PR - ubuntu-latest
  • GitHub Check: Test NodeJS PR - windows-latest
  • GitHub Check: Lighthouse CI

@derberg
Copy link
Member

derberg commented Jul 7, 2025

@aminoxix great work mate 👏🏼 thanks for helping out 🍺

@derberg
Copy link
Member

derberg commented Jul 7, 2025

/rtm

@asyncapi-bot asyncapi-bot merged commit 3f82071 into asyncapi:master Jul 7, 2025
26 of 27 checks passed
anushkaaaaaaaa pushed a commit to anushkaaaaaaaa/website that referenced this pull request Jul 10, 2025
Co-authored-by: aminoxix <[email protected]>
Co-authored-by: Chan <[email protected]>
Co-authored-by: Raghav Tandulkar <[email protected]>
Co-authored-by: Pankaj Kumar <[email protected]>
Co-authored-by: Sagar Kori <[email protected]>
Co-authored-by: sharad poddar <[email protected]>
Co-authored-by: Adi Boghawala <[email protected]>
Co-authored-by: Atinuke Oluwabamikemi Kayode <[email protected]>
Co-authored-by: Azeez Elegbede <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: Akshat Nema <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

We need page that lists board members