Chris, thanks for bringing this up, it's too important a topic to let languish. We've been discussing this internally for the past week, so the timing is good to bring it up more broadly. That said, this note is simply to acknowledge receipt and to set expectations of timing for a deeper response from us. Rob and I are both out of the office this week. We'll be together on Tue/Wed, so we can certainly discuss it, but we might not have a chance to respond in writing until late in the week, or early next week at the latest. Again, thanks for bringing it up, and expect a response in no more than a week. Of course, the above isn't meant to suppress comments in the meantime from anyone else who would like to weigh in with thoughts on the current problems, and possible solutions going forward! P.S. Speaking only for me, I am subscribed to zope-annce@zope.org, but not to zope@zope.org or zope-web@zope.org, so if anyone continues this thread, I'd be very appreciative if you could continue to copy me directly, rather than just the lists. Chris Withers wrote:
Hi Guys,
What can we do about Zope.org?
I've heard so much about it's problems but so little seems to happen :-(
The site seems to be totally unresponsive a fair bit of the time now, which is pretty appalling in what should be the flagship of a stable and reliable web application server.
I know it was a less-than-minor hamper to the bug day on Friday that people often couldn't view or update bugs due to Zope.org taking over a minute to respond to requests, when it responded at all. There's also the fact that it purports to run on a version of Zope with known security issues (2.6.2)
For once, I'm trying to approach this with an open mind so just wanted to ask some questions:
- What are the problems with Zope.org? Why does is appear to be so unstable and unresponsive? (I could suggest why, but then I accept I have an unpopular opinion at the base of that suggestion ;-)
- What do people have to do to help out? I have a perceptionthat there are people who want to help out but that they feel the barrier to entry is too high. (For example, who can actually get in and restart the clients, should they be suffering from memory bloat?)
- Where should this be discussed? (zope-web@zope.org has been dead for 4-6 months now)
I hope the above can at least kick off some discussion but I'd really like to see some solutions. I know Zope.org is a perenial problem, but there's got to be a way we can sort it out...
cheers,
Chris