Skip to content

Add Sebastian Heid to the foundational infrastructure team (BOSH) #1340

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add Sebastian Heid to the foundational infrastructure team (BOSH) #1340

wants to merge 3 commits into from
+3 −0

Conversation

s4heid
Copy link

@s4heid s4heid commented Oct 21, 2025 •
edited
Loading

I have Azure expertise and would like to help maintain Azure-related BOSH projects, especially the bosh-azure-cpi-release and everything Azure related in the bosh-linux-stemcell-builder.

@s4heid
Add Sebastian Heid to the foundational infrastructure team (BOSH)
425b25e 
I have expertise with Azure and want to help maintain the bosh-azure-cpi-release.
@s4heid
Copy link
Author

s4heid commented Oct 21, 2025

Foundational Infrastructure: VM deployment lifecycle (BOSH) Contributions

PRs Commented on/Reviewed:

Issues that may be relevant:

Code contributions:

Foundational Infrastructure: Storage CLI Contributions

Issues that may be relevant:

Code contributions:

Foundational Infrastructure: Ali Cloud VM deployment lifecycle (BOSH) Contributions

Issues that may be relevant:

beyhan
beyhan requested changes Oct 21, 2025
View reviewed changes
Copy link
Member

@beyhan beyhan left a comment

Choose a reason for hiding this comment

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

Hi @s4heid,
thank you for the interest and the pr. Could you please add yourself also to the https://github.com/cloudfoundry/community/blob/main/orgs/contributors.yml.

@beyhan beyhan added the wg-fi label Oct 21, 2025
@s4heid
Copy link
Author

s4heid commented Oct 21, 2025

@beyhan Sure, I added myself.

beyhan
beyhan previously approved these changes Oct 21, 2025
View reviewed changes
@beyhan beyhan requested a review from rkoster October 21, 2025 09:29
@rkoster
Copy link
Contributor

rkoster commented Oct 21, 2025

Why not go directly for approver? Based on the number of contributions you would qualify easily for that role.

@beyhan
Copy link
Member

beyhan commented Oct 21, 2025

@rkoster because Sebastian hasn't been reviewer for three months we thought going for reviewer first is more appropriate. If everyone is fine with going for approver it can be changed.

@s4heid
Copy link
Author

s4heid commented Oct 21, 2025

I'm good with either option—let's go with what you think is best.

a-hassanin
a-hassanin approved these changes Oct 22, 2025
View reviewed changes
Copy link
Contributor

@a-hassanin a-hassanin left a comment

Choose a reason for hiding this comment

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

I think we should already grant the approver role :)

@beyhan
Copy link
Member

beyhan commented Oct 22, 2025

@s4heid I see people are eager to see you as approver :-). Please update the pr or in case you think you go better for reviewer please comment. Here you can check responsibilities for reviewer and responsibilities for approver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@rkoster rkoster rkoster approved these changes

@beyhan beyhan beyhan left review comments

+1 more reviewer

@a-hassanin a-hassanin a-hassanin approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

wg-fi

Projects

CF Community
Status: Inbox
Foundational Infrastructure Working Group
Status: No status

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@s4heid @rkoster @beyhan @a-hassanin