-
-
Notifications
You must be signed in to change notification settings - Fork 177
chore: add info about who is elected to board 2025 #1976
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -122,6 +122,7 @@ | |||||||||||||||
| availableForHire: false | ||||||||||||||||
| linkedin: fmvilas | ||||||||||||||||
| isTscMember: true | ||||||||||||||||
| isBoardMember: true | ||||||||||||||||
| repos: | ||||||||||||||||
|
Comment on lines
123
to
126
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Schema-breaking field causes CI failure GitHub Actions reports “Validation of maintainers file failed”. Either update the schema (preferred) or drop the key to restore the pipeline: - isBoardMember: true📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||||
| - spec | ||||||||||||||||
| - spec-json-schemas | ||||||||||||||||
|
|
@@ -560,6 +561,7 @@ | |||||||||||||||
| availableForHire: false | ||||||||||||||||
| company: AsyncAPI Initiative | ||||||||||||||||
| isTscMember: true | ||||||||||||||||
| isBoardMember: true | ||||||||||||||||
| repos: | ||||||||||||||||
| - website | ||||||||||||||||
| - conference-website | ||||||||||||||||
|
|
||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isBoardMemberviolates the current ambassadors schemaNo other ambassador entry exposes this flag and the CI does not validate ambassadors, so we have no evidence the schema actually supports it. Consider either
a) extending the ambassadors JSON-schema first, or
b) storing board membership in a separate, already-validated list.
Until the schema is updated this extra field is just silent technical debt that can break downstream consumers expecting a strict schema.
🤖 Prompt for AI Agents