Here's my proposal for dealing with modular X entering ~arch.

Yes, some packages are going to break. But I intend to keep this to a
minimum on packages people care about, as measured by the existence of
an open porting bug.

So here's my plan: Before modular X enters ~arch, I will ensure that all
porting bugs blocking #112675 are closed. As new bugs are filed, I will
ensure that they are closed within 2 days, giving their maintainers that
long to respond and close it themselves. After 2 days, I, or other
members of the x11 team and any volunteers, will jump in and fix it
ourselves.

Earlier tonight, I discussed with halcy0n our differing opinions of the
need for modular X to enter ~arch and break trees for some ~arch users.
In my opinion, this is acceptable and beneficial, as ~arch users should
already be those willing to help out. It will assist in learning which
of the still-unported apps are actually in use and help compile a
possible list of tree removal candidates. halcy0n, on the other hand,
feels that any breakage of the ~arch tree is anathema.

Please contact me if you'd like to be one of these volunteers. Requirements:

A) You have commit access to gentoo-x86, AND
B) you're comfortable with the porting process OR are adept with ebuilds
and would like to help

It's my earnest hope that this proposal makes everyone happy, because I
refuse to let modular X get old and rusty in package.mask while hundreds
of unmaintained (or undermaintained, for whatever reason) applications
hold it back.

Thanks,
Donnie

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to