| 1 |
On 2018-04-16 17:28, Michał Górny wrote: |
| 2 |
> Hello, everyone. |
| 3 |
> |
| 4 |
> The following packages are up for grabs due to the Enlightenment |
| 5 |
> project |
| 6 |
> being disbanded: |
| 7 |
> |
| 8 |
> app-doc/edox-data |
| 9 |
> dev-libs/efl |
| 10 |
> dev-python/python-efl |
| 11 |
> media-libs/elementary |
| 12 |
> media-libs/imlib2 |
| 13 |
> media-plugins/emotion_generic_players |
| 14 |
> media-plugins/evas_generic_loaders |
| 15 |
> media-plugins/imlib2_loaders |
| 16 |
> x11-misc/e16keyedit |
| 17 |
> x11-misc/e16menuedit2 |
| 18 |
> x11-plugins/epplets |
| 19 |
> x11-terms/terminology |
| 20 |
> x11-themes/ethemes |
| 21 |
> x11-wm/enlightenment |
| 22 |
> |
| 23 |
> (+ enlightenment.eclass) |
| 24 |
> |
| 25 |
> The packages have a large number of bugs open. They are outdated, both |
| 26 |
> in terms of releases and EAPI. The eclass needs either a major |
| 27 |
> overhaul, or preferably removal as obsolete boilerplate. |
| 28 |
> |
| 29 |
> On the bright side, there is a certain interest in Enlightenment |
| 30 |
> (including open PRs) from proxied maintainers, so the packages |
| 31 |
> shouldn't |
| 32 |
> have much trouble finding a new maintainer. |
| 33 |
|
| 34 |
Hi. |
| 35 |
|
| 36 |
As stated before I don't mind taking (some of the) e17 stuff - i have |
| 37 |
efl and enlightenment in my dev overlay and been using it for several |
| 38 |
weeks now. |
| 39 |
The question is .. who wants the e16 stuff / how would maintainership |
| 40 |
work for x11-wm/enlightenment which is both e16 and e17 ? |
| 41 |
|
| 42 |
Regards |
Archives