Gentoo's best peace of art is Portage, which is written on Python. I guess that may let me to consider Gentoo community as a Python-centric one. Why Gentoo web site is not done with Zope, the best content and community management technology, which is also the best Python application? Forums are PHP-based, the main site I heard is Perl based. Why? Why not use Zope (especially with its best product Plone) and thus having the most customizable system? Why not let people to leave comments (paragaph or page bound) and thus to participate in content development of the site? Why not integrate issue tracking with forums and news (see: CMFCollectorNG)? Why not have both thread and board based forums (see Squishdot and fcForum)? Why not have portal member folders where regular mortals (not only core team developers) can host their software projects (aka Sourceforge)? If you have a lack of free Zope hands for it then I for one is ready to devote as much time as I can to help migrating Gentoo web site to Zope. And I call for everyone who knows (and thus loves) Zope to stand up and say so, if you agree to help somehow with it. Reproducible: Always Steps to Reproduce: Actual Results: www.gentoo.org Expected Results: www.plone.org www.squishdot.org Other Zope products: CMFCollectorNG, ZWiki, fcForums, Ape
I will put in one specific comment about this, from my experiences with Zope and Plone. In a previous job, we were building some sites in Zope with Plone, and we were having issues trying to scale them up to handle reasonable loads like what you would expect on medium web sites. They quite simply couldn't handle it. We brought in Andy McKay (one of the Plone developers) and the end answer from him was we were hitting memory leaks that had never been fixed and probably weren't going to be fixed anytime soon. We re-wrote the site in PHP. It was more of a Plone problem than a Zope problem. Zope/Plone was eating 400Mb+ of RAM. As an end result, Zope/Plone is great to prototype sites in, but you need something that doesn't eat resources for breakfast for production use.
our sreve
our www.g.o server rely on AxKit (axkit.org) and a set of custom shell scripts. We are extremely happy with the performance and scalability offered by AxKit (a Dual-PII 400 was able to withstand a slashdotting recently) and have no plans to migrate away from this platform in the near future.
