The back story of this series is Greg Wilson's quest to elevate design thinking in software. Beautiful Code, the book, was also part of this quest.
Back story:
The architecture of explaining how open source applications are architected may need a revamping itself?
What might be useful is an approach of live collections that keep evolving / added to. Maybe some sort of extension of the Journal of Open Source Software [1] where authors focus purely on architectural aspects.
Having a classification (by technology, functionality etc.) would also make it easier to make the most out of this wonderful collection.
A lot of these might be organically grown more than planned in advanced. There's some survivor bias in picking some big open source project and copying its architecture, as if that was the reason for its success.
It's still interesting to look at, but more as a curiosity. Maybe some of those ideas might come in handy someday. But I wouldn't start learning these as super successful design pattern and start forcing them onto your next project.
[2011]
v2 is 2012 and I think some of the other books linked are more recent.
Nice