> I think everyone is in agreement that they fulfill the letter of the
> license. The spirit may be lacking especially in regards to access.
> Being an enormous, interdependent hairball simply puts the code out of
> reach for all practical purposes as well as restricting use. Again,
> that's spirit and not letter and the license does not address that.
> There is however one large, long running project which does take code
> legibility and quality and those kinds of things into account, in
> addition to license. Maybe that's something for GPLv4, or maybe not.

RMS admits that he wrote GCC as an interdependent hairball, simply to
make it impossible to reuse parts of it in commercial applications. So
I doubt that RMS will end up condemning "hairballs" in GPLv4 (or
later). That change would require him to fight a project he started
and to push it into a direction he is not at all comfortable with.