Document process and criteria to remove a core plugin [40011335]

Fixed

Bug

FixedIn-3.3.0

Status Update

No update yet.

Description

ek...@google.com

created issue #1

Sep 30, 2019 03:08PM

What are the criteria and the process to downgrade a core plugin to a normal plugin?

Comments

ek...@google.com <ek...@google.com> #2Sep 30, 2019 03:14PM

[Monorail components: ESC]

ma...@gmail.com <ma...@gmail.com> #3Oct 8, 2019 11:42PM

[Monorail components: -Community]

ma...@gmail.com <ma...@gmail.com> #4Feb 10, 2020 09:43PM

I propose to first work on figuring the entry criteria out (

https://crbug.com/gerrit/11635).

ma...@gmail.com <ma...@gmail.com> #5Feb 10, 2020 09:59PM

[Empty comment from Monorail migration]

ma...@gmail.com <ma...@gmail.com> #6Apr 21, 2020 03:29PM

[Empty comment from Monorail migration]

lu...@gmail.com <lu...@gmail.com> #7Apr 21, 2020 10:47PM

@Marco @Edwin this issue is associated to the ESC.
What type of engagement are you expecting from us? Propose a process?

ek...@google.com <ek...@google.com> #8Apr 22, 2020 06:19AM

We (community managers) can take care to define/describe a process, but we would like to get input from you on the criteria that should be used to make such a decision.

lu...@gmail.com <lu...@gmail.com> #9Apr 22, 2020 12:02PM

@Edwin, thanks for the clarification. I'll put an entry in the agenda of the next ESC meeting.

ma...@gmail.com <ma...@gmail.com> #10Apr 22, 2020 04:43PM

Accepted by lu...@gmail.com.

Thanks @Luca. I then set you as Owner, accordingly, until a CM can (based on that ESC input).

[Monorail components: Community]

lu...@gmail.com <lu...@gmail.com> #11Apr 22, 2020 09:37PM

Thanks @Marco, I'm good in taking ownership on this task and present and discuss with the ESC

ma...@gmail.com <ma...@gmail.com> #12Apr 30, 2020 03:30PM

[Empty comment from Monorail migration]

da...@gmail.com <da...@gmail.com> #13May 1, 2020 02:34AM

How is this blocking 11819 if that is closed?

ma...@gmail.com <ma...@gmail.com> #14May 1, 2020 02:53PM

Indeed; removed.

lu...@gmail.com <lu...@gmail.com> #15Jul 6, 2020 11:27PM

Change available for review at:

https://gerrit-review.googlesource.com/c/gerrit/+/274514

ma...@gmail.com <ma...@gmail.com> #16Jul 7, 2020 04:21PM

[Empty comment from Monorail migration]

ma...@gmail.com <ma...@gmail.com> #17Aug 4, 2020 07:31PM

Marked as fixed.

[Empty comment from Monorail migration]

bu...@chops-service-accounts.iam.gserviceaccount.com <bu...@chops-service-accounts.iam.gserviceaccount.com> #18Aug 4, 2020 07:32PM

The following revision refers to this bug:

https://gerrit.googlesource.com/gerrit.git/+/a4a11bb2228897ff4dd5836ab7b9ac27eaa65dc8

commit a4a11bb2228897ff4dd5836ab7b9ac27eaa65dc8
Author: Luca Milanesio <luca.milanesio@gmail.com>
Date: Fri Jul 31 11:54:35 2020

Add a process to remove a core plugin

The technical criteria for removing a core plugin
is the exact opposite of the one for adding a core
plugin.

Even though it was quite obvious, it has been explicitly
requested to be documented.

Bug:

https://crbug.com/gerrit/11637
Change-Id: I5e067310bcdcdc84dfb6754d2f0796ffb7e451b9

[modify]

https://gerrit.googlesource.com/gerrit.git/+/a4a11bb2228897ff4dd5836ab7b9ac27eaa65dc8/Documentation/dev-core-plugins.txt

ma...@gmail.com <ma...@gmail.com> #19Oct 8, 2020 04:02PM

[Empty comment from Monorail migration]

ek...@google.com <ek...@google.com> #20Jul 6, 2022 12:30PM

[Monorail components: SteeringCommittee]

ek...@google.com <ek...@google.com> #21Jul 6, 2022 12:31PM

[Monorail components: -ESC]

ek...@google.com <ek...@google.com> #22Jul 15, 2022 08:49AM

[Empty comment from Monorail migration]

is...@google.com <is...@google.com> #23Jul 15, 2022 08:49AM

Edits were made to reflect the following in Monorail: auto-CCs.

Issue 40011335

Description

Issue summary

Comments

ek...@google.com <ek...@google.com> #2Sep 30, 2019 03:14PM

ma...@gmail.com <ma...@gmail.com> #3Oct 8, 2019 11:42PM

ma...@gmail.com <ma...@gmail.com> #4Feb 10, 2020 09:43PM

ma...@gmail.com <ma...@gmail.com> #5Feb 10, 2020 09:59PM

ma...@gmail.com <ma...@gmail.com> #6Apr 21, 2020 03:29PM

lu...@gmail.com <lu...@gmail.com> #7Apr 21, 2020 10:47PM

ek...@google.com <ek...@google.com> #8Apr 22, 2020 06:19AM

lu...@gmail.com <lu...@gmail.com> #9Apr 22, 2020 12:02PM

ma...@gmail.com <ma...@gmail.com> #10Apr 22, 2020 04:43PM

lu...@gmail.com <lu...@gmail.com> #11Apr 22, 2020 09:37PM

ma...@gmail.com <ma...@gmail.com> #12Apr 30, 2020 03:30PM

da...@gmail.com <da...@gmail.com> #13May 1, 2020 02:34AM

ma...@gmail.com <ma...@gmail.com> #14May 1, 2020 02:53PM

lu...@gmail.com <lu...@gmail.com> #15Jul 6, 2020 11:27PM

ma...@gmail.com <ma...@gmail.com> #16Jul 7, 2020 04:21PM

ma...@gmail.com <ma...@gmail.com> #17Aug 4, 2020 07:31PM

bu...@chops-service-accounts.iam.gserviceaccount.com <bu...@chops-service-accounts.iam.gserviceaccount.com> #18Aug 4, 2020 07:32PM

ma...@gmail.com <ma...@gmail.com> #19Oct 8, 2020 04:02PM

ek...@google.com <ek...@google.com> #20Jul 6, 2022 12:30PM

ek...@google.com <ek...@google.com> #21Jul 6, 2022 12:31PM

ek...@google.com <ek...@google.com> #22Jul 15, 2022 08:49AM

is...@google.com <is...@google.com> #23Jul 15, 2022 08:49AM

Add comment

Issue metadata