Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Managing opt-in/opt-out

My advice:

Send a note to the 26 projects' lists (and/or directly to their PL/PMC?) reminding them of the need for the minimal effort to opt-in (it's not like jury duty or needing to put gas in a car if you want the car to continue to drive), and set a date after which they'll be summarily disabled from the simrel for non-compliance.

I say give them 2 weeks as you might be hitting people during summer vacation. Maybe make it due by Sept 4?

We could also consider having a heavy-handed "miss M2 and you're out [1]" policy for the annual June releases, and a "if you were in for June you can coast through the year without opting in again and again" policy for the other 3 releases, which aligns with the old annual simrel trains' opt-in process and gets around the apathy/vacation schedules.

[1] If kicked out they'd be required to opt back in by M3 (3 weeks later) or else miss being included in that quarterly GA release. Exceptions of course on a case-by-case basis if they grovel well enough to the EMO or PC. :D

#actionsHaveConsequences #soDoesInaction


On Thu, Aug 15, 2019 at 3:22 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Greetings Eclipse Planning Council.

The entire purpose of having an opt-in process is to ensure that project teams are paying attention so that issues can be identified and remediated.

As of now, we have 26 projects that participated in the previous release that have not formally opted-in to participate in the 2019-09 release.  Clearly 26 project teams aren't paying attention. 

What is the consensus of the Eclipse Planning Council regarding what we do about that? Shall we disable these projects' aggrcon files?

Perhaps we need to account for (Northern hemisphere) summer vacations in our process...

Note that I noticed today that Eclipse PMF has no committers. I've scheduled a termination review for that project and will ask Fred to remove that project's aggrcon file.


Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.


Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: CodeReady Workspaces 

IM: @nickboldt / @nboldt /

“The Only Thing That Is Constant Is Change” - Heraclitus

Back to the top