Github Username

@kevinawoo

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @ethanfrogers
• @maggieneterval
• @duftler
• @christopherthielen

List of qualifications for this position

• Name of organization(s) with significant stake in project.
  Armory, we're trying to get EVERYONE to use Spinnaker of course!!11! 🚀 🌔 🎉
• Links to public Spinnaker PRs
  • spinnaker/clouddriver#3286
  • spinnaker/clouddriver#3776
  • spinnaker/deck#6559
  • spinnaker/deck#6842
  • spinnaker/front50#491
  • spinnaker/halyard#1219
  • spinnaker/halyard#1273
  • spinnaker/igor#399
  • spinnaker/orca#2765
  • spinnaker/spinnaker.github.io#1127
  • spinnaker/spinnaker#3835

Github Username

@plumpy

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

@ezimanyi
@duftler

List of qualifications for this position

spinnaker/gate#775
spinnaker/clouddriver#3578
spinnaker/orca#2872
spinnaker/clouddriver#3715
spinnaker/clouddriver#3815

Github Username

@aravindmd

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @jeyrschabu
• @marchello2000

List of qualifications for this position

• Member of Spinnaker team @ Netflix
• PR's authored
  • https://github.com/spinnaker/clouddriver/commits?author=aravindmd
  • https://github.com/spinnaker/orca/commits?author=aravindmd
  • https://github.com/spinnaker/swabbie/commits?author=aravindmd
• PR's reviewed
  • spinnaker/swabbie#292
  • spinnaker/swabbie#293
  • spinnaker/swabbie#233
  • spinnaker/orca#3011
  • spinnaker/gate#764
  • spinnaker/orca#2935

I propose that we create a SIG that is focused on techniques and developing working code to improve operational validation, which will include canary analysis as well as others such as progressive deployment driven by observed behavior. This is a widely defined scope, and if needed we can split it into smaller sections, but we did not want to limit it to just a specific strategy.

Proposed leads: Michael Graff, Chris Sanden, Matt Duftler

Proposed meeting cadence: Either monthly or every 2 weeks. We may start more frequent but change as we evolve.

Cloud Provider

Name of cloud provider TencentCloud(tencent)

Maintaining Organization(s)

• Tencent

Point of Contact(s)

• @shengyu @donghun221

Requirements

• Cloud Provider will be actively backed by a development team from Maintainers with a significant stake in the project.
• Maintainers commit to triaging and addressing major bugs and issues with the integration in a timely manner.
• Maintainers commit to handling routine maintainence tasks for the integrations, such as:
  • Keeping it compatible with updates to the cloud provider itself.
  • Making any cloud provider-specific changes in response to global architecture changes within Spinnaker.
• Maintainers acknowledge failure to maintain cloud provider integration may prompt removal of integration from Spinnaker.
• Maintainers agree to setup and maintain a Special Interest Group for the Cloud Provider integration.

@michaeljqzq @harikumarks @neil-yechenwei

The Azure cloud provider has been identified as not having a Special Interest Group created for it. A SIG must be formed for each Cloud Provider to offer the community a communications channel for feedback and support. Since there is not already a SIG formed for this cloud provider, one will need to be created.

With the creation of the SIG, adherence to the Cloud Provider Requirements will be required.

If no action is taken on this issue by the 1st of June, 2020, this cloud provider will be a candidate for removal from the core Spinnaker project and may be moved to a plugin where it will need to be maintained separately.

Why was I assigned this issue?

We were unable to find a complete list of email address contacts for this cloud provider to contact the owners directly. Please copy any individuals that may be a better contact for fielding this issue if needed.

What we need from you

A new SIG needs to be formed for this cloud provider. You can read about the process on forming a SIG following the directions on the SIG Lifecycle page.

If continued support of this cloud provider is not planned by your organization, please let us know so we may plan accordingly.

Hi, I noticed that https://github.com/spinnaker/spinnaker-monitoring is not in the list of repos that approvers/reviewers have access to. Also mergify is also not setup in this repo.

I vote for adding this into the normal Spinnaker approvers/reviewers workflow also.

@shihchang @guoyongzhang

The Oracle cloud provider has been identified as not having a Special Interest Group created for it. A SIG must be formed for each Cloud Provider to offer the community a communications channel for feedback and support. Since there is not already a SIG formed for this cloud provider, one will need to be created.

With the creation of the SIG, adherence to the Cloud Provider Requirements will be required.

If no action is taken on this issue by the 1st of June, 2020, this cloud provider will be a candidate for removal from the core Spinnaker project and may be moved to a plugin where it will need to be maintained separately.

Why was I assigned this issue?

We were unable to find a complete list of email address contacts for this cloud provider to contact the owners directly. Please copy any individuals that may be a better contact for fielding this issue if needed.

What we need from you

A new SIG needs to be formed for this cloud provider. You can read about the process on forming a SIG following the directions on the SIG Lifecycle page.

If continued support of this cloud provider is not planned by your organization, please let us know so we may plan accordingly.

I nominate Erin Kidwell to replace Ruslan Meshenberg on the Steering Committee. Ruslan's term ends on 12/31/2019.

Erin is the Director of Engineering Tools and Services at Netflix. Her team works closely with Delivery Engineering to reduce the complexity of building and integrating code across the growing polyglot ecosystem at Netflix. As a key stakeholder and trusted partner, Erin has played a vital role in the evolution of Spinnaker. I'm excited at the prospects of Erin joining the SC as she brings deep industry knowledge as well as a passion for open source!

Steering Committee members, please indicate you vote via a +1 for yes or a -1 for no or 0 for abstaining.

@willgorman @mtweten

The DCOS cloud provider has been identified as not having a Special Interest Group created for it. A SIG must be formed for each Cloud Provider to offer the community a communications channel for feedback and support. Since there is not already a SIG formed for this cloud provider, one will need to be created.

With the creation of the SIG, adherence to the Cloud Provider Requirements will be required.

If no action is taken on this issue by the 1st of June, 2020, this cloud provider will be a candidate for removal from the core Spinnaker project and may be moved to a plugin where it will need to be maintained separately.

Why was I assigned this issue?

We were unable to find a complete list of email address contacts for this cloud provider to contact the owners directly. Please copy any individuals that may be a better contact for fielding this issue if needed.

What we need from you

A new SIG needs to be formed for this cloud provider. You can read about the process on forming a SIG following the directions on the SIG Lifecycle page.

If continued support of this cloud provider is not planned by your organization, please let us know so we may plan accordingly.

Github Username

@danielpeach

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

@maggieneterval
@ezimanyi
@claymccoy

List of qualifications for this position

• Name of organization(s) with significant stake in project: Armory
• Links to public Spinnaker PRs

spinnaker/orca#2346
spinnaker/orca#2257
spinnaker/deck#5617
spinnaker/clouddriver#743
spinnaker/orca#2217

As a followup from this mornings meeting: I'm self-nominating myself for TOC Chair. It'll give me so much power, like running meetings and maintaining agendas.

Github Username

@allisaurus

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @clareliguori
• @robzienert

List of qualifications for this position

spinnaker/orca#3016
spinnaker/clouddriver#3825
spinnaker/deck#7162
spinnaker/deck#7338
spinnaker/spinnaker.github.io#1452

smaller fixes/enhancements:
spinnaker/deck#7123
spinnaker/deck#7169
spinnaker/deck#7170
spinnaker/kork#412

@zengchen1024

The Huawei cloud provider has been identified as not having a Special Interest Group created for it. A SIG must be formed for each Cloud Provider to offer the community a communications channel for feedback and support. Since there is not already a SIG formed for this cloud provider, one will need to be created.

With the creation of the SIG, adherence to the Cloud Provider Requirements will be required.

If no action is taken on this issue by the 1st of June, 2020, this cloud provider will be a candidate for removal from the core Spinnaker project and may be moved to a plugin where it will need to be maintained separately.

Why was I assigned this issue?

We were unable to find a complete list of email address contacts for this cloud provider to contact the owners directly. Please copy any individuals that may be a better contact for fielding this issue if needed.

What we need from you

A new SIG needs to be formed for this cloud provider. You can read about the process on forming a SIG following the directions on the SIG Lifecycle page.

If continued support of this cloud provider is not planned by your organization, please let us know so we may plan accordingly.

Github Username

@link108

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• https://github.com/ethanfrogers
• https://github.com/robzienert

List of qualifications for this position

• spinnaker/kork#219
• spinnaker/kork#217
• spinnaker/kork#325
• spinnaker/kork#358
• spinnaker/halyard#1386
• spinnaker/orca#3058
• spinnaker/deck#6842

@shengyu @donghun221

The Tencent cloud provider has been identified as not having a Special Interest Group created for it. A SIG must be formed for each Cloud Provider to offer the community a communications channel for feedback and support. Since there is not already a SIG formed for this cloud provider, one will need to be created.

With the creation of the SIG, adherence to the Cloud Provider Requirements will be required.

If no action is taken on this issue by the 1st of June, 2020, this cloud provider will be a candidate for removal from the core Spinnaker project and may be moved to a plugin where it will need to be maintained separately.

Why was I assigned this issue?

We were unable to find a complete list of email address contacts for this cloud provider to contact the owners directly. Please copy any individuals that may be a better contact for fielding this issue if needed.

What we need from you

A new SIG needs to be formed for this cloud provider. You can read about the process on forming a SIG following the directions on the SIG Lifecycle page.

If continued support of this cloud provider is not planned by your organization, please let us know so we may plan accordingly.

Github Username

caseyhebebrand

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

@christopherthielen
@alanmquach

List of qualifications for this position

• Organizations with a stake in Spinnaker: Netflix

Author:

• Show icon for target group registration in progress
• Type field for CLB details
• Disable CLB deletion if instances exist
• Target Group health check URL
• Refer to Jenkins controller
• [Show load balancer warning based on settings](feat(provider/aws): Show load balancer warning based on settings)
• 2 package bumps

Reviewer:

• Functions listing and searching
• Reactify delete application section
• Allow markdown in validation message
• Reactify edit application modal
• Preventing edits against orphaned load balancers

I nominate Andy Glover for another term on the Steering Committee. Andy's current term ends on 12/31/2019.

Andy Glover is the Director of Delivery Engineering at Netflix. He and his team own and operate Spinnaker at Netflix.

Steering Committee members, please indicate you vote via a +1 for yes or a -1 for no or 0 for abstaining. As per the Spinnaker project’s rules, Andy does not have a vote on his election.

Github Username

@jonsie

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @robzienert
• @marchello2000

List of qualifications for this position

• Name of organization(s) with significant stake in project

Netflix

• Links to public Spinnaker PRs

Open:

spinnaker/clouddriver#4155
spinnaker/front50#625 (and spinnaker/front50#621)

Commits:

https://github.com/spinnaker/orca/commits?author=jonsie
https://github.com/spinnaker/clouddriver/commits?author=jonsie
https://github.com/spinnaker/kork/commits?author=jonsie
https://github.com/spinnaker/front50/commits?author=jonsie
https://github.com/spinnaker/fiat/commits?author=jonsie
https://github.com/spinnaker/rosco/commits?author=jonsie

Github Username

@german-muzquiz

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @ethanfrogers
• @kevinawoo

List of qualifications for this position

• Name of organization(s) with significant stake in project: Armory
• Links to public Spinnaker PRs

spinnaker/halyard#1644
spinnaker/kork#380
spinnaker/halyard#1416
spinnaker/clouddriver#3716
spinnaker/deck#6937

Github Username

@brian-armory

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @ethanfrogers
• @kevinawoo

List of qualifications for this position

• Documentation SIG

Github Username

gal-yardeni

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @emjburns
• @marchello2000

List of qualifications for this position

Organizations with a stake in Spinnaker: Netflix

• Links to public Spinnaker PRs:

Author:

1. orca/precondition: Add a custom message to precondition
2. orca/monitor-deploy: Completed event should include details of success/failure
3. deck/baseOS : Adding display name property for the bakery baseOs options
4. gate/baseOS: Add displayName to baseOS
5. keel/deleteApp: Delete all data for an application

Reviewer:

1. feat(monitoreddeploy): allow overriding maxAnalysisMinutes and failOnError
2. docs(managed): add overview and reference for resource statuses
3. feat(rollback): avoid scaling down during rollback
4. feat(managed): add resource status to infrastructure views
5. fix(actuation): correctly detect active actuations for multi-region resources
6. fix(webhook): Don't try to deserialize fields we don't really need

Github Username

@lorin

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @luispollo
• @emjburns

List of qualifications for this position

• Name of organization with significant stake in project: Netflix
• Links to public Spinnaker PRs

Select reviews

• spinnaker/keel#1055
• spinnaker/keel#1023
• spinnaker/keel#997
• spinnaker/keel#959
• spinnaker/keel#957
• spinnaker/keel#905

Commits

• https://github.com/spinnaker/keel/commits?author=lorin
• https://github.com/spinnaker/spinnaker.github.io/commits?author=lorin

Github Username

@pkandasamy91

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @allisaurus
• @clareliguori

List of qualifications for this position

• Name of organization(s) with significant stake in project: AWS
• Links to public Spinnaker PRs

Merged:

• spinnaker/deck#7692
• spinnaker/deck#7837
• spinnaker/deck#7949
• spinnaker/deck#8188
• spinnaker/clouddriver#4218
• spinnaker/clouddriver#4349
• spinnaker/clouddriver#4496

Reviewed:

• spinnaker/clouddriver#4526
• spinnaker/clouddriver#4275
• spinnaker/clouddriver#4340
• spinnaker/deck#8186
• spinnaker/deck#8049

Github Username

@pdelagrave

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @ezimanyi
• @Jammy-Louie

List of qualifications for this position

• Halyard Boot2 migration
• "Run Job" stage support for CloudFoundry
• New Halyard option to select an image variant when deploying Spinnaker on k8s
• Ubuntu image variant support:
  • Build system
  • Every service: clouddriver, echo front50, orca, +6 other...
• 35 total code PRs merged in spinnaker
• 7 docs PRs merged

Github Username : gal-yardeni

e.g. (at)github_user

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• (at)sponsor-1 : Emily Burns (@emjburns )
• (at)sponsor-2 : Mark Vulfson (@marchello2000 )

List of qualifications for this position

• part of the Spinnaker team @ Netflix.

Github Username

@jonsie

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @robzienert
• @marchello2000

List of qualifications for this position

• spinnaker/orca#3228 (open)
• https://github.com/spinnaker/orca/commits?author=jonsie
• https://github.com/spinnaker/clouddriver/commits?author=jonsie
• https://github.com/spinnaker/fiat/commits?author=jonsie
• https://github.com/spinnaker/front50/commits?author=jonsie
• https://github.com/spinnaker/rosco/commits?author=jonsie
• https://github.com/spinnaker/roer/commits?author=jonsie

Github Username

gal-yardeni

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @emjburns
• @marchello2000

List of qualifications for this position

• Name of organization(s) with significant stake in project: Netflix
• Links to public Spinnaker PRs:

Created by me:
orca/precondition: Add a custom message to precondition
orca/monitor-deploy: Completed event should include details of success/failure
deck/baseOS : Adding display name property for the bakery baseOs options
gate/baseOS: Add displayName to baseOS
keel/deleteApp: Delete all data for an application

Reviewed by me:
feat(monitoreddeploy): allow overriding maxAnalysisMinutes and failOnError
docs(managed): add overview and reference for resource statuses
feat(rollback): avoid scaling down during rollback
feat(managed): add resource status to infrastructure views
fix(actuation): correctly detect active actuations for multi-region resources
fix(webhook): Don't try to deserialize fields we don't really need

• Some more...

I nominate Matt Duftler for another term on the Steering Committee. Matt's previous term ended on 12/31/2019.

Matt is a Staff Software Engineer on the Cloud Continuous Delivery team at Google in NYC. Matt has been working on the Spinnaker project since Google became involved in 2014, and was a co-creator of several of its services.

Steering Committee members, please indicate you vote via a +1 for yes or a -1 for no or 0 for abstaining. As per the Spinnaker project’s rules, Matt does not have a vote on his election.

@xiaozhu36

The Alicloud cloud provider has been identified as not having a Special Interest Group created for it. A SIG must be formed for each Cloud Provider to offer the community a communications channel for feedback and support. Since there is not already a SIG formed for this cloud provider, one will need to be created.

With the creation of the SIG, adherence to the Cloud Provider Requirements will be required.

If no action is taken on this issue by the 1st of June, 2020, this cloud provider will be a candidate for removal from the core Spinnaker project and may be moved to a plugin where it will need to be maintained separately.

Why was I assigned this issue?

We were unable to find a complete list of email address contacts for this cloud provider to contact the owners directly. Please copy any individuals that may be a better contact for fielding this issue if needed.

What we need from you

A new SIG needs to be formed for this cloud provider. You can read about the process on forming a SIG following the directions on the SIG Lifecycle page.

If continued support of this cloud provider is not planned by your organization, please let us know so we may plan accordingly.

Github Username

@plumpy

Requirements

• [:+1:] I am a Spinnaker Approver already
• [:+1:] I have enabled 2FA on my Github account
• [:+1:] I have one sponsor within the Steering Committee
• [:+1:] I have spoken to my sponsor(s) ahead of this application, and they have agreed to sponsor my application

Sponsors

@duftler
@ezimanyi

List of qualifications for this position

• Prior open source experience
  • https://secure2.linuxjournal.com/ljarchive/LJ/107/6489.html
  • http://lkml.iu.edu/hypermail/linux/kernel/0308.1/1798.html
  • https://willysr.blogspot.com/2004/11/another-updates-for-gaim.html
  • https://fossies.org/linux/xmms/ChangeLog
  • https://plugins.jetbrains.com/plugin/8527-google-java-format
• Links to public contributions showing your technical command of the Spinnaker project
  • See #29

Github Username

@anotherchrisberry

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @ajordens
• @asher

List of qualifications for this position

• Name of organization(s) with significant stake in project: Netflix
• Links to public Spinnaker PRs: there are a few

Github Username

@aravindmd

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @marchello2000
• @jeyrschabu

List of qualifications for this position

• https://github.com/spinnaker/clouddriver/commits?author=aravindmd
• https://github.com/spinnaker/orca/commits?author=aravindmd
• https://github.com/spinnaker/swabbie/commits?author=aravindmd

Github Username

@scottfrederick

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @Jammy-Louie
• @claymccoy

List of qualifications for this position

PRs

• spinnaker/clouddriver#3638
• spinnaker/clouddriver#3682
• spinnaker/clouddriver#3683
• spinnaker/clouddriver#3812 (in review)
• spinnaker/kork#286

Design docs

• Spinnaker External Configuration
• Spinnaker Config Secrets Using Config Server

Cloud Provider

Name of cloud provider AlibabaCloud(alicloud)

Maintaining Organization(s)

• Alibaba Group

Point of Contact(s)

• @xiaozhu36

Requirements

• Cloud Provider will be actively backed by a development team from Maintainers with a significant stake in the project.
• Maintainers commit to triaging and addressing major bugs and issues with the integration in a timely manner.
• Maintainers commit to handling routine maintainence tasks for the integrations, such as:
  • Keeping it compatible with updates to the cloud provider itself.
  • Making any cloud provider-specific changes in response to global architecture changes within Spinnaker.
• Maintainers acknowledge failure to maintain cloud provider integration may prompt removal of integration from Spinnaker.
• Maintainers agree to setup and maintain a Special Interest Group for the Cloud Provider integration.

Github Username

@allisaurus

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @clareliguori
• @robzienert

List of qualifications for this position

• Name of organization(s) with significant stake in project: AWS
• Links to public Spinnaker PRs

Select reviews

• spinnaker/clouddriver#4496
• spinnaker/deck#7837
• spinnaker/clouddriver#4218
• spinnaker/clouddriver#4409
• spinnaker/clouddriver#4411
• spinnaker/deck#7949
• spinnaker/clouddriver#4340
• spinnaker/spinnaker.github.io#1736

Commits

• https://github.com/spinnaker/clouddriver/commits?author=allisaurus
• https://github.com/spinnaker/deck/commits?author=allisaurus
• https://github.com/spinnaker/orca/commits?author=allisaurus
• https://github.com/spinnaker/kork/commits?author=allisaurus
• https://github.com/spinnaker/spinnaker.github.io/commits?author=allisaurus

Github Username

@ezimanyi

Requirements

• I am a Spinnaker Approver already
• I have enabled 2FA on my Github account
• I have one sponsor within the Steering Committee
• I have spoken to my sponsor(s) ahead of this application, and they have agreed to sponsor my application

Sponsors

• @duftler
• @skim1420

List of qualifications for this position

• Strong contributor to the OSS Spinnaker project over the past ~1.5 years.
  • Top 5 contributor to most of the core Spinnaker repos (by commits) in that timeframe
  • Made a number of wide-reaching refactors, particularly to orca, igor, and clouddriver-kubernetes
  • Active in triaging/resolving issues, particularly in the kubernetes provider

Github Username

caseyhebebrand

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

christopherthielen
alanmquach

List of qualifications for this position

Author:

• Show icon for target group registration in progress
• Type field for CLB details
• Disable CLB deletion if instances exist
• Target Group health check URL
• Refer to Jenkins controller
• [Show load balancer warning based on settings](feat(provider/aws): Show load balancer warning based on settings)
• 2 package bumps

Reviewer:

• Functions listing and searching
• Reactify delete application section
• Allow markdown in validation message
• Reactify edit application modal
• Preventing edits against orphaned load balancers

Github Username

@fieldju

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @duftler
• @maggieneterval
• @erikmunson
• @cfieber

List of qualifications for this position

Name of organization(s) with significant stake in project

Nike, Inc

We have integrated Kayenta into our Ci/Cd process and are committed to having it be part of our ACA solution.

Links to public Spinnaker PRs

Kayenta

1 open, 18 closed
https://github.com/spinnaker/kayenta/pulls?q=is%3Apr+author%3Afieldju+sort%3Acreated-asc

Deck Kayenta

1 closed
https://github.com/spinnaker/deck-kayenta/pulls?q=is%3Apr+author%3Afieldju+sort%3Acreated-asc

PRs and issues that I have reviewed and triaged
https://github.com/spinnaker/kayenta/issues?q=is%3Aissue+is%3Aclosed+assignee%3Afieldju
https://github.com/spinnaker/kayenta/pulls?q=is%3Apr+is%3Aclosed+reviewed-by%3Afieldju

Github Username

lorin

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @luispollo
• @emjburns

List of qualifications for this position

Organizations with a stake in Spinnaker: Netflix

• Links to public Spinnaker PRs

Author:

1. feat(repository): disallow duplicate artifact refs
2. fix(veto): fix Value annotation syntax
3. feat(api): test endpoint that throws an exception
4. fix(metrics): record drift from last resource check
5. fix(actuator): add coroutine id to help debug
6. fix(resource): tweak thread model, add more debug logging

Reviewer:

1. Don't keep re-trying the same bake
2. fix(artifacts): don't keep marking as deployed over and over
3. feat(artifact): introduce SKIPPED status, more data for previous
4. fix(artifact): more resilient app version parsing
5. fix(events): Fix paused events for resources due to pausing application

Github Username

@luispollo

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @emjburns
• @robfletcher
• @erikmunson

List of qualifications for this position

• Name of organization(s) with significant stake in project: Netflix
• Links to public Spinnaker PRs
  • Created by me:
    • feat(resource-status): Return PAUSED status for vetoed resources
    • feat(serialization): Use friendly names for artifact types
    • fix(rrb): Store RRB before-cleanup pipeline ID in the right context field
    • fix(bake): Fix the fix for inconsistent names in parallel bakes
    • fix(notifications): Don't send failure notifications for cancelled pipelines and stages
    • etc.
  • Reviewed by me:
    • don't treat missing AMI as a fatal resolution error
    • feat(deleteApp): Delete all data for an application
    • feat(environments): allowed-times constraint
    • feat(core/managed): visually refresh/rebrand infra details indicator
    • feat(core/managed): add deep links to status reference doc
    • etc.

Github Username

@plumpy

Requirements

• [:heavy_check_mark:] Belongs to an organization with significant stake in project
• [:heavy_check_mark:] Known active participant in the community
• [:heavy_check_mark:] Has submitted at least 5 PRs of significant scope that are merged
• [:heavy_check_mark:] Is already fulfilling the Reviewer role
• [:heavy_check_mark:] Has reviewed 5 PRs of significant scope
• [:heavy_check_mark:] Sponsored by 2 Approvers

Sponsors

@ezimanyi
@maggieneterval

List of qualifications for this position

• Name of organization(s) with significant stake in project
  

• Links to public Spinnaker PRs
  spinnaker/clouddriver#3968
  spinnaker/clouddriver#3932
  spinnaker/fiat#443
  spinnaker/clouddriver#3970

Github Username

e.g. @srekapalli

Sponsors

• @cfieber
• @marchello2000

List of qualifications for this position

Organization

• Netflix.

Links to public Spinnaker PRs

spinnaker/gate feat(cors): Configurable whitelist of origins

spinnaker/orca fix(SpEL): Execution context injected into expressions dynamically

spinnaker/orca fix(webhooks): Construct Webhook status check URL honoring the

spinnaker/front50 feat(PostgreSQL DB Storage): Added support for Postgres.

spinnaker/orca feat(executions): Adding new ADMIN endpoint to import execution

spinnaker/kork feat(sql): Support for multiple SQL data sources

spinnaker/front50 feat(sql): Enables composite storage service to be backed by SQL

PRs Reviewed.
feat(expressions): Enhance expression evaluation order

feat(plugins): Remote plugin download capabilities

feat(slack): Add slack service

feat(aggregator): enables customization of permission aggregation as well as permission sources

refactor(titus): Allow serde of operation descriptions

spinnaker/keel Limit number of events in history

Github Username

@german-muzquiz

Requirements

• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Sponsored by 2 Approvers

Sponsors

• @ethanfrogers
• @kevinawoo

List of qualifications for this position

• spinnaker/gate#675
• spinnaker/clouddriver#3442
• spinnaker/halyard#1252
• spinnaker/deck#6937
• spinnaker/clouddriver#3716
• spinnaker/clouddriver#3961

• sig-aws
  • mailing list
  • leads mailing list
  • github team (also, there's a sig-aws-ecs team, which isn't a real SIG?)
  • github issue label
  • meeting on SIG calendar
• sig-ci
  • mailing list
  • leads mailing list
  • github team
  • github issue label
  • meeting on SIG calendar
• sig-documentation
  • mailing list
  • leads mailing list
  • github team
  • github issue label (but incorrectly named sig-docs)
  • meeting on SIG calendar
• sig-kubernetes
  • mailing list
  • leads mailing list
  • github team
  • github issue label
  • meeting on SIG calendar
• sig-operational-validation
  • mailing list
  • leads mailing list
  • github team (but incorrectly named sig-opsvalidation
  • github issue label
  • meeting on SIG calendar
• sig-ops
  • mailing list
  • leads mailing list
  • github team
  • github issue label
  • meeting on SIG calendar
• sig-platform
  • mailing list
  • leads mailing list
  • github team
  • github issue label
  • meeting on SIG calendar
• sig-security
  • mailing list
  • leads mailing list
  • github team
  • github issue label
  • meeting on SIG calendar
• sig-spinnaker-as-code
  • mailing list
  • leads mailing list
  • github team (but incorrectly named sig-spin-as-code
  • github issue label
  • meeting on SIG calendar
• sig-summit
  • mailing list
  • leads mailing list
  • github team
  • github issue label
  • meeting on SIG calendar
• sig-ui-ux
  • mailing list (but incorrectly named sig-ui)
  • leads mailing list
  • github team (but incorrectly named sig-ui)
  • github issue label
  • meeting on SIG calendar

@pdelagrave @scottfrederick

The CloudFoundry cloud provider has been identified as not having a Special Interest Group created for it. A SIG must be formed for each Cloud Provider to offer the community a communications channel for feedback and support. Since there is not already a SIG formed for this cloud provider, one will need to be created.

With the creation of the SIG, adherence to the Cloud Provider Requirements will be required.

If no action is taken on this issue by the 1st of June, 2020, this cloud provider will be a candidate for removal from the core Spinnaker project and may be moved to a plugin where it will need to be maintained separately.

Why was I assigned this issue?

We were unable to find a complete list of email address contacts for this cloud provider to contact the owners directly. Please copy any individuals that may be a better contact for fielding this issue if needed.

What we need from you

A new SIG needs to be formed for this cloud provider. You can read about the process on forming a SIG following the directions on the SIG Lifecycle page.

If continued support of this cloud provider is not planned by your organization, please let us know so we may plan accordingly.

Github Username

@srekapalli

Sponsors

• @cfieber
• @marchello2000

List of qualifications for this position

Merged PR's

spinnaker/gate feat(cors): Configurable whitelist of origins

spinnaker/orca fix(SpEL): Execution context injected into expressions dynamically

spinnaker/orca fix(webhooks): Construct Webhook status check URL honoring the

spinnaker/front50 feat(PostgreSQL DB Storage): Added support for Postgres.

spinnaker/orca feat(executions): Adding new ADMIN endpoint to import execution

spinnaker/kork feat(sql): Support for multiple SQL data sources

spinnaker/front50 feat(sql): Enables composite storage service to be backed by SQL

Cloud Provider

Name of cloud provider HuaweiCloud(huaweicloud)

Maintaining Organization(s)

• Huawei

Point of Contact(s)

• @zengchen1024 @niuzhenguo

Requirements

• Cloud Provider will be actively backed by a development team from Maintainers with a significant stake in the project.
• Maintainers commit to triaging and addressing major bugs and issues with the integration in a timely manner.
• Maintainers commit to handling routine maintainence tasks for the integrations, such as:
  • Keeping it compatible with updates to the cloud provider itself.
  • Making any cloud provider-specific changes in response to global architecture changes within Spinnaker.
• Maintainers acknowledge failure to maintain cloud provider integration may prompt removal of integration from Spinnaker.
• Maintainers agree to setup and maintain a Special Interest Group for the Cloud Provider integration.

Github Username

@skandragon

Requirements

• [ X ] Belongs to an organization with significant stake in project
• [ X ] Known active participant in the community
• [ X ] Has submitted at least 5 PRs of significant scope that are merged
• [ X ] Is already fulfilling the Reviewer role
• [ X ] Has reviewed 5 PRs of significant scope
• [ X ] Sponsored by 2 Approvers

Sponsors

• @duftler
• @fieldju

List of qualifications for this position

• Name of organization(s) with significant stake in project

OpsMX

• Links to public Spinnaker PRs

A lot of them on Kayenta, Orca, etc. :)

Github Username

@clareliguori

Requirements

• Belongs to an organization with significant stake in project
• Known active participant in the community
• Has submitted at least 5 PRs of significant scope that are merged
• Is already fulfilling the Reviewer role
• Has reviewed 5 PRs of significant scope
• Sponsored by 2 Approvers

Sponsors

• @emjburns
• @robzienert

List of qualifications for this position

• Name of organization(s) with significant stake in project: AWS
• Links to public Spinnaker PRs:

Merged:

• spinnaker/clouddriver#3604
• spinnaker/clouddriver#3660
• spinnaker/clouddriver#3238
• spinnaker/deck#6687
• spinnaker/clouddriver#2998

Reviewed:

• spinnaker/clouddriver#3825
• spinnaker/clouddriver#3633
• spinnaker/orca#3016
• spinnaker/deck#7162
• spinnaker/clouddriver#3888