Hi,

We have <438 EAPI 0 ebuilds left (I've removed a few more since [1]). 
We're nearing the time when we can finally get rid of EAPI 0.  For this
reason, I'd like to set a 'media goal' of getting EAPI 0 by the end
of 2019.

Why getting rid of EAPI 0 is important?  Because there's a huge leap
between EAPI 0 and EAPI 4+ (though 4 is also close to being gone). 
Removing EAPI 0 means we can finally start cleaning up eclasses
and documentation.  Just to name a few things, we're finally going
to have consistent '||die' in helpers, phase function set, USE flag
dependencies, no implicit RDEPEND...  Just take a look at [2],
and you're going to be surprised how many things have changed.

What's been done?  I've taken care of cleaning up old versions
and requesting stabilization of newer ones whenever feasible.
I've treecleaned a lot of dead packages (and a few of them have been
revived and updated).  I've filed bugs for probably all the packages
left and collected them on the tracker [3].

What needs to be done?  The maintainers need to port remaining packages
or send last rites for them.  Some of those packages are not being cared
by the maintainers anymore, so if you see something valuable, take it. 
If you see something obviously dead, let treecleaners know.  Any and all
help will be appreciated!

The rough plan is to have a clear vision of what to do with
the remaining packages one month from now -- either have them bumped
to a newer EAPI and waiting for stabilization, or last rited for removal
in mid-December.

[1] https://qa-reports.gentoo.org/output/eapi_usage.txt
[2] https://projects.gentoo.org/pms/7/pms.html#x1-172000E
[3] https://bugs.gentoo.org/657150

-- 
Best regards,
Michał Górny