On Wed, 01 Mar 2006 21:28:38 +0000, Jens Vagelpohl wrote:
> As someone who has done years and years of large-scale sysadmin work,
> unless the software is supported or has been chosen by the people who
> will have to deal with it day after day after it has been put in
> place it simply will not succeed. The current zope.org suffers from
> that same problem. It became an immediate orphan because those people
> who were tasked with maintaining the setup on a daily basis *hated*
> it from Day 1.
I would be truly surprised and disappointed if it were true that those
responsible for zope.org would put an emotional reaction to a piece of
code above the needs of the community that helps to sustain them.
Regardless, if the issue is primarily one of support, perhaps the Plone
community could help out until a solution that people love comes along?
For instance, if the Plone Foundation were to come up with resources in
the community to support a PloneHelpCenter/PloneSoftwareCenter-based
interim zope.org site, could that be made to happen? One possible
division of labor would be to have the existing volunteers be responsible
for the infrastructure they do not have a problem with (e.g. Zope / Python
/ Squid / LDAP / etc) and backups, and some Plone people could keep the
Products directory up to date? At this point I have no idea if this can
be made to happen on the Plone side, but I would guess that enough people
would find the prospect sufficiently important that the resources could be
found. If the idea is feasible, I would be happy to take the matter up in
the Plone community.
If the proposed alternative will be ready for production in the near-term,
though, this is all a moot point. Is there a solid timeline on the
replacement under discussion?
Zope-web maillist - Zopefirstname.lastname@example.org