Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

On 03/20/2017 05:39 PM, Hongbin Lu wrote: > > >> -Original Message- >> From: Dean Troyer [mailto:dtro...@gmail.com] >> Sent: March-20-17 5:19 PM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [magnum][osc] What name to use for magnum

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

On Mon, Mar 20, 2017 at 3:37 PM, Adrian Otto wrote: > the argument is actually the service name, such as “ec2”. This is > the same way the openstack cli works. Perhaps there is another tool that you > are referring to. Have I misunderstood something? I am going to

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Clint, On Mar 20, 2017, at 3:02 PM, Clint Byrum > wrote: Excerpts from Adrian Otto's message of 2017-03-20 21:16:09 +: Jay, On Mar 20, 2017, at 12:35 PM, Jay Pipes > wrote:

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Excerpts from Adrian Otto's message of 2017-03-20 22:19:14 +: > I was unsure, so I found him on IRC to clarify, and he pointed me to the > openstack/service-types-authority repository, where I submitted patch 445694 > for review. We have three distinct identifiers in play: > > 1) Our

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

> -Original Message- > From: Dean Troyer [mailto:dtro...@gmail.com] > Sent: March-20-17 5:19 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum][osc] What name to use for magnum > commands in osc? > > On Mon, Mar 20, 2017 at 3:37

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

+1 from me. That looks easy to implement and maintain. On 3/20/17, 2:49 PM, "Davanum Srinivas" wrote: >Dave, > >Here's the precendent from oslo.policy: >https://review.openstack.org/#/admin/groups/556,members > >The reason for setting it up this way with individuals + oslo

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Zun had a similar issue of colliding on the keyword "container", and we chose to use an alternative term "appcontainer" that is not perfect but acceptable. IMHO, this kind of top-level name collision issue would be better resolved by introducing namespace per project, which is the approach

Re: [openstack-dev] [stackalytics] user correction seems not effective

I’m referring to, https://review.openstack.org/#/c/446942/1 / Trinath Somanchi. From: Yujun Zhang (ZTE) [mailto:zhangyujun+...@gmail.com] Sent: Monday, March 20, 2017 11:00 AM To: OpenStack Development Mailing List (not for usage questions) ;

[openstack-dev] [mogan] Nominating liusheng for Mogan core

Hi team, I would like to nominate liusheng to Mogan core. Liusheng has been a significant code contributor since the project's creation providing high quality reviews. Please feel free to respond in public or private your support or any concerns. Thanks, Zhenguo

Re: [openstack-dev] [infra][tripleo] initial discussion for a new periodic pipeline

On Sun, Mar 19, 2017 at 06:54:27PM +0200, Sagi Shnaidman wrote: > Hi, Paul > I would say that real worthwhile try starts from "normal" priority, because > we want to run promotion jobs more *often*, not more *rarely* which happens > with low priority. > In addition the initial idea in the first

Re: [openstack-dev] [User-committee] Boston Forum - Formal Submission Now Open!

+openstack-dev mailing-list. On Mon, Mar 20, 2017 at 3:55 PM, Melvin Hillsman wrote: > Hey everyone! > > We have made it to the next stage of the topic selection process for the > Forum in Boston. > > Starting today, our submission tool is open for you to submit abstracts

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

What about coe? Thanks, Kevin From: Adrian Otto [adrian.o...@rackspace.com] Sent: Monday, March 20, 2017 12:08 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [magnum][osc] What name to use for magnum commands

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

On 03/20/2017 03:08 PM, Adrian Otto wrote: Team, Stephen Watson has been working on an magnum feature to add magnum commands to the openstack client by implementing a plugin: https://review.openstack.org/#/q/status:open+project:openstack/python-magnumclient+osc In review of this work, a

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Kevin, I added that to the list for consideration.Feel free to add others to the list on the team agenda using our Wiki page. Adrian > On Mar 20, 2017, at 12:27 PM, Fox, Kevin M wrote: > > What about coe? > > Thanks, > Kevin > >

[openstack-dev] [neutron] bug deputy report (Mar 14 - Mar 20)

Hi all, I served as the bug deputy for the week of March 14th – March 20th. There were around 25 bugs and three new RFE’s. There was some discussion/confusion regarding this bug: https://bugs.launchpad.net/neutron/+bug/1672629 on IRC. Review for the fix patch:

Re: [openstack-dev] [all][ironic] Kubernetes-based long running processes

I thought somebody already asked in Mistral IRC channel, IMO, Mistral is a good candidate in this case, TripleO[1] already use Mistral for running its own tasks. For those who didn't know Mistral well, Mistral is a workflow engine that can run you designed workflow in a stable, scalable way. For

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Excerpts from Adrian Otto's message of 2017-03-20 21:16:09 +: > Jay, > > On Mar 20, 2017, at 12:35 PM, Jay Pipes > > wrote: > > On 03/20/2017 03:08 PM, Adrian Otto wrote: > Team, > > Stephen Watson has been working on an magnum feature to add

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are happy to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. update/review

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Dean, Thanks for your reply. > On Mar 20, 2017, at 2:18 PM, Dean Troyer wrote: > > On Mon, Mar 20, 2017 at 3:37 PM, Adrian Otto > wrote: >> the argument is actually the service name, such as “ec2”. This is >> the same way the openstack cli

Re: [openstack-dev] [os-upstream-institute] First meeting is starting :)

Hi All, Quick reminder, we have our first meeting now! :) Thanks, Ildikó > On 2017. Mar 19., at 14:14, Ildiko Vancsa wrote: > > Hi All, > > Based on the results of the Doodle poll I sent out earlier the most favorite > slot for the meeting is __Mondays, 2000 UTC__.

[openstack-dev] [charms] Charms IRC meetings

Hi This is just a quick reminder that there are two meetings at different times for folks interested in discussing the OpenStack charms. This is so we can get more geographic coverage: - ODD weeks (next on Monday 27th March at 10:00 UTC) - EVEN weeks (next on Monday 3rd April at 17:00 UTC)

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Hongbin, > On Mar 20, 2017, at 1:10 PM, Hongbin Lu wrote: > > Zun had a similar issue of colliding on the keyword "container", and we chose > to use an alternative term "appcontainer" that is not perfect but acceptable. > IMHO, this kind of top-level name collision

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

On Mon, Mar 20, 2017 at 4:36 PM, Adrian Otto wrote: > So, to be clear, this would result in the following command for what we > currently use “magnum cluster create” for: > > openstack coe cluster create … > > Is this right? Yes. dt -- Dean Troyer

Re: [openstack-dev] [ceilometer]Can't find meter anywhere with ceilometer post REST API

On 18/03/17 04:54 AM, Hui Xiang wrote: > Hi folks, > > I am trying to post samples from third part software to ceilometer via > the REST API as below with Mitaka version. I can see ceilometer-api has > received this post, and seems forwarded to ceilometer notification agent > through RMQ. >

Re: [openstack-dev] [dib] diskimage-builder v2 RC1 release; request for test

On 03/21/2017 03:10 AM, Mikhail Medvedev wrote: On Fri, Mar 17, 2017 at 3:23 PM, Andre Florath wrote: Submitted the bug https://bugs.launchpad.net/diskimage-builder/+bug/1674402 Thanks; some updates there. Would adding a third-party CI job help? I can put together a

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

On Mon, Mar 20, 2017 at 03:35:18PM -0400, Jay Pipes wrote: > On 03/20/2017 03:08 PM, Adrian Otto wrote: > >Team, > > > >Stephen Watson has been working on an magnum feature to add magnum commands > >to the openstack client by implementing a plugin: > > >

Re: [openstack-dev] [ceilometer]Can't find meter anywhere with ceilometer post REST API

Thanks gordon for your info. The reason why not using gnocchi in mitaka is that we are using collectd-ceilometer-plugin[1] to posting samples to ceilometer through ceilometer-api, after mitaka yes we will all move to gnocchi. """ when posting samples to ceilometer-api, the data goes through

[openstack-dev] [neutron] functional job broken by eventlet 0.20.1

Hi all, FYI we were broken by the new eventlet. The fix is at: https://review.openstack.org/#/c/447817/ Hopefully we can find reviewers in EMEA/APAC time zones to groom and land it. Thanks, Ihar __ OpenStack Development

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

On Mon, Mar 20, 2017 at 12:23 PM, Dave McCowan (dmccowan) wrote: > +1 from me. That looks easy to implement and maintain. > > On 3/20/17, 2:49 PM, "Davanum Srinivas" wrote: > >>Dave, >> >>Here's the precendent from oslo.policy:

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Jay, On Mar 20, 2017, at 12:35 PM, Jay Pipes > wrote: On 03/20/2017 03:08 PM, Adrian Otto wrote: Team, Stephen Watson has been working on an magnum feature to add magnum commands to the openstack client by implementing a plugin:

Re: [openstack-dev] [neutron][lbaasv2] Migrate LBaaS instance

Hi Saverio, We completely understand that operators are still on older versions of OpenStack and we are executing against the OpenStack release series [1] and we adhere to the support phases as outlined in [2]. So any new features will only be added to Pike whereas bug fixes will be carried

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

On Mon, Mar 20, 2017 at 5:52 PM, Monty Taylor wrote: >> [Hongbin Lu] >> I think the style would be more consistent if all the resources are >> qualified or un-qualified, not the mix of both. > So - swift got here first, it wins, it gets container. The fine folks in >

Re: [openstack-dev] [vitrage] vitrage Resource API

No, in the implemention of these APIs． see https://github.com/openstack/vitrage/blob/master/vitrage/api/controllers/v1/resource.py#L47 Original Mail Sender: ＜trinath.soman...@nxp.com＞ To: ＜openstack-dev@lists.openstack.org＞ ＜openstack-dev@lists.openstack.org＞ Date:

Re: [openstack-dev] questions about Openstack Ocata replacement API

On 3/19/2017 6:03 AM, Chris Dent wrote: On Sun, 19 Mar 2017, zhihao wang wrote: I am trying the new version openstack ocata in Ubuntu 1604 But I got some problem with nova placement API, there is nothing on the Openstack Ubuntu Installation Doc The docs for that are being updated to include

Re: [openstack-dev] [neutron][lbaasv2] Migrate LBaaS instance

Hi Saverio, First, please note, in the future the best tag for load balancing is [octavia] as it is no longer part of the neutron project. I am sorry that you are so anxious and confused about the current state of load balancing for OpenStack. Let me clarify a few things: 1. LBaaSv2 is not

[openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Team, Stephen Watson has been working on an magnum feature to add magnum commands to the openstack client by implementing a plugin: https://review.openstack.org/#/q/status:open+project:openstack/python-magnumclient+osc In review of this work, a question has resurfaced, as to what the client

[openstack-dev] [vitrage] vitrage Resource API

Hi All, I noticed that the APIs of `resource list` and `resource show` were mocked. Is there any backgroud for the mock or the API is not necessary? BR, dwj__ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

I proposed a blueprint to track the work done: https://blueprints.launchpad.net/tripleo/+spec/tripleo-deploy-guide Target: pike-3 Volunteers to work on it with me, please let me know. Thanks, On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle wrote: > Hey Emilien, > > You

[openstack-dev] [telemetry] Moving Gnocchi out

Hi, After a lot of talk within the Gnocchi team, it appeared to us that Gnocchi, which has been wisely tagged as 'independent' since its inception, has a lot of potential usage outside of OpenStack directly. Being part of the big tent helped the project to be built, but it now appears that it

[openstack-dev] [requirements][keystone][glance] WebOb

Dear Keystone and Glance teams, WebOb update of u-c to 1.7.1 is stuck for a while[1]. Can you please prioritize reviews (keystone) review [1] and (glance) review [2] for this week? Thanks, Dims [1] https://review.openstack.org/#/c/417591/ [2] https://review.openstack.org/#/c/422234/ [3]

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

This sounds good to me. I see it as a "promotion" for Castellan into the core of OpenStack. I think a good first step in this direction is to create a castellan-drivers team in Launchpad and a castellan-core team in Gerrit. We can seed the list with Barbican core reviewers and any Oslo

[openstack-dev] [neutron][tap-as-a-service] neutron-lib breakage

Hi, Can the tap guys please look at https://review.openstack.org/447277. All projects using the tap project are currently stuck Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [mogan] Nominating liusheng for Mogan core

+1 Liusheng is a responsible reviewer and keep good reviewing quality in Mogan. Thank you working hard for Mogan, Liusheng. 2017-03-20 16:19 GMT+08:00 Zhenguo Niu : > Hi team, > > I would like to nominate liusheng to Mogan core. Liusheng has been a > significant code

[openstack-dev] [picasso] Bi-weekly meeting (March 21, 1700 UTC) canceled

Hello everyone, Due to members of the team on vacation, the Picasso IRC meeting has been canceled for this week. We will resume on April 4th. Feel free to reach out in #openstack-functions in the meantime. Regards, Derek Schultz Picasso PTL

Re: [openstack-dev] [horizon] [keystone] [federated auth] [ocata] federated users with "admin" role not authorized for nova, cinder, neutron admin panels

Hey Boris, Any updates on this? Cheers, -E -- Evan F. Bollig, PhD Scientific Computing Consultant, Application Developer | Scientific Computing Solutions (SCS) Minnesota Supercomputing Institute | msi.umn.edu University of Minnesota | umn.edu boll0...@umn.edu | 612-624-1447 | Walter Lib Rm 556

Re: [openstack-dev] [networking-sfc] About insertion modes and SFC Encapsulation

Hi Igor, Moving the correlation from port-pair to port-pair-group makes sense. In the future I think we should add all new attributes for a SF to port-pair-group-param. But I think L2/L3 is different from encap type NSH or MPLS. An L3 type SF can support either NSH or MPLS. I would suggest

Re: [openstack-dev] [kolla] rabbitmq cluster_partition_handling config in kolla-ansible

Hello, It would be extremely hard to detect "reliable" network...if it even exists:) We use autohealing because we also use rabbitmq clusterer plugin, which simplifies recovery from partition. As for hardcoded, one thing I noticed is that these files indeed aren't overridable. I published this

Re: [openstack-dev] [kolla] rabbitmq cluster_partition_handling config in kolla-ansible

Hello Nikita, There is no technical reason this cannot be made variable. I don't think anyone could come up with a valid reason to block such a patch. However, I would ask what you plan to gain from _not_ having it 'autoheal'? The other options for partition handling are basically "let it

Re: [openstack-dev] [telemetry] Moving Gnocchi out

On 03/20/2017 10:10 AM, Chris Dent wrote: On Mon, 20 Mar 2017, Thomas Goirand wrote: I really don't understand why the Telemetry team insists in being release-independent, out of big tent and such, when the reality is that all of released Telemetry components are *very tightly* bound to a

Re: [openstack-dev] [ironic] New mascot design

+1, this looks like a nicely stylized version of PXE Boots. Thanks! Mario On Mon, Mar 13, 2017 at 3:25 PM, Jim Rollenhagen wrote: > > On Fri, Mar 10, 2017 at 11:28 AM, Heidi Joy Tretheway > wrote: >> >> Hi Ironic team, >> Here’s an update on

Re: [openstack-dev] [telemetry] Moving Gnocchi out

On Mon, 20 Mar 2017, Thomas Goirand wrote: I really don't understand why the Telemetry team insists in being release-independent, out of big tent and such, when the reality is that all of released Telemetry components are *very tightly* bound to a specific versions of OpenStack. IMO, it doesn't

Re: [openstack-dev] [dib] diskimage-builder v2 RC1 release; request for test

On Fri, Mar 17, 2017 at 3:23 PM, Andre Florath wrote: > Hello! > > Thanks for the bug report. Can you please file this as a bug? Hi Andre, Submitted the bug https://bugs.launchpad.net/diskimage-builder/+bug/1674402 > > There is a very high probability that I introduced a

Re: [openstack-dev] [ironic] volunteers for cross project liaisons

Hi Ruby. I’d like to volunteer for logging, in case ironic still needs a liaison with this group. In the CrossProjectLiaisons wiki [1], for the logging group, only a few projects are listed. Does this mean that the projects listed there are the only needing help? Or as people volunteer, her/his

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

On Mon, Mar 20, 2017 at 5:31 PM, Emilien Macchi wrote: > I proposed a blueprint to track the work done: > > https://blueprints.launchpad.net/tripleo/+spec/tripleo-deploy-guide > Target: pike-3 > > Volunteers to work on it with me, please let me know. > Please add me (irc

Re: [openstack-dev] [TripleO] Propose Attila Darazs and Gabriele Cerami for tripleo-ci core

On Wed, Mar 15, 2017 at 11:44 AM, John Trowbridge wrote: > Both Attila and Gabriele have been rockstars with the work to transition > tripleo-ci to run via quickstart, and both have become extremely > knowledgeable about how tripleo-ci works during that process. They are > both

[openstack-dev] [kolla] rabbitmq cluster_partition_handling config in kolla-ansible

Hi, Since [1] kolla-ansible have rabbitmq cluster_partition_handling option hard-coded to 'autoheal'. According to [2] it's not a best mode for 3+ node clusters with reliable network. Is it reasonable to make this option changeable by user or even place some logic to pickup mode based on

Re: [openstack-dev] [ironic] Hardware console processes in multi-conductor environment

Hi Yuriy, I like idea #4 (building task management functionality into a separate console driver). I think this was suggested at the PTG, and it's good because it fits into the existing model ironic has for handling console. Thanks, Mario On Fri, Mar 10, 2017 at 10:42 AM, Yuriy Zveryanskyy

[openstack-dev] [neutron] [classifier] New CCF meeting time decided (next tomorrow)

Hi all, After [1], a new meeting time/day has been decided. With 6 votes, Tuesdays at 1400 UTC was the most wanted time slot [2]. Eavesdrop has been updated to reflect this [3] and all up-do-date information can be found at [4]. Due to conflicting times at the IRC channel, the meeting also

[openstack-dev] [networking-sfc] About insertion modes and SFC Encapsulation

Hi networking-sfc, At the latest IRC meeting [1] it was agreed to split TAP from the possible insertion modes (initial spec version [2]). I took the ARs to propose coexistence of insertion modes, correlation and (now) a new tap-enabled attribute, and send this email about possible directions.

Re: [openstack-dev] [ironic] Ironic review party invitation

Hi ironic team, I'm proposing that we move this to 20:00 UTC Thursdays (8pm UTC, 4pm in my timezone which is US Eastern). I think this will better fit with the daylight saving time adjustment that most attendees had last week. Please message me here or in IRC if there are objections. I've updated

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

Hey, I'll like to collaborate, please, just let me know what can I do to help with this task. Might be a good idea to have in the blueprint a list of tasks? Also, I think this can be called Deployment/Upgrade guide for TripleO. Cheers, Carlos. On Mon, Mar 20, 2017 at 3:26 PM, Sanjay

Re: [openstack-dev] [telemetry] Moving Gnocchi out

On 03/20/2017 11:24 AM, Julien Danjou wrote: > Hi, > > After a lot of talk within the Gnocchi team, it appeared to us that > Gnocchi, which has been wisely tagged as 'independent' since its > inception I'm not sure I find this decision as fine as you do. > has a lot of potential usage outside

Re: [openstack-dev] [ironic] volunteers for cross project liaisons

Hi Solio, Thanks for volunteering to be the liaison for the logging working group. The project that are listed there, are the ones that have liaisons with the working group. It gives everyone an idea of which projects have liaisons. So your name will be added there shortly, as the ironic

Re: [openstack-dev] [telemetry] Moving Gnocchi out

-Original Message- From: Chris Friesen Reply: OpenStack Development Mailing List (not for usage questions) Date: March 20, 2017 at 11:39:38 To: openstack-dev@lists.openstack.org Subject: 

Re: [openstack-dev] [telemetry] Moving Gnocchi out

On 20/03/17 11:37 AM, Thomas Goirand wrote: > > I really don't understand why the Telemetry team insists in being > release-independent, out of big tent and such, when the reality is that > all of released Telemetry components are *very tightly* bound to a > specific versions of OpenStack. IMO,

Re: [openstack-dev] [telemetry] Moving Gnocchi out

On 2017-03-20 12:57:17 -0400 (-0400), Ian Cordasco wrote: [...] > Contributing to OpenStack is intimidating, if not utterly > discouraging, to people unfamiliar with CLAs and Gerrit. There's a lot > of process that goes into contributing. Moving this to a friendlier > (if not inferior) developer

Re: [openstack-dev] [vitrage] vitrage Resource API

In tests? Get Outlook for iOS From: dong.wenj...@zte.com.cn Sent: Monday, March 20, 2017 2:49:57 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage] vitrage Resource API Hi All, I

Re: [openstack-dev] [ironic] volunteers for cross project liaisons

Hi Jay, That makes a lot of sense and thank YOU for being the i18n liaison! :D --ruby On 2017-03-15, 11:18 AM, "Jay Faulkner" wrote: > On Mar 15, 2017, at 8:11 AM, Loo, Ruby wrote: > > Hi, > > The ironic community is looking for

Re: [openstack-dev] [ironic] volunteers for cross project liaisons

Hi Rushil, We (or I am) are happy that you are volunteering to be the oslo project liaison. Thanks! There is a section in our etherpad [1] (look for 'Cross-project'), where you could add anything of interest (i.e. anything from oslo that impacts ironic). We look at (and discuss) these during

Re: [openstack-dev] [telemetry] Moving Gnocchi out

On Mon, Mar 20, 2017 at 12:10 PM, gordon chung wrote: > > > On 20/03/17 11:37 AM, Thomas Goirand wrote: > >> >> I really don't understand why the Telemetry team insists in being >> release-independent, out of big tent and such, when the reality is that >> all of released Telemetry

Re: [openstack-dev] [infra][tripleo] initial discussion for a new periodic pipeline

As another data point, from Wednesday to Friday last week rh1 ran at full capacity pretty much round the clock. There were experimental jobs that queued for at least 18 hours. Granted, this is a symptom of a capacity problem we've exacerbated by adding the containers OVB job, but even

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

Dave, Here's the precendent from oslo.policy: https://review.openstack.org/#/admin/groups/556,members The reason for setting it up this way with individuals + oslo core + keystone core is to make sure both core teams are involved in the review process and any future contributors who are not part