On Thu, 09 Feb 2006 14:28:22 -0000, Andrew Sawyers <[EMAIL PROTECTED]>
On Thu, 2006-02-09 at 14:09 +0100, Max M wrote:
Chris Withers wrote:
If we cannot make it work in Zope 2 or 3, maybe we should use rails ;-)
I know Max is kidding; but to comment to Chris. One of the main
problems to avoid is 'kruft' and bit-rot. zope.org suffers this to the
point of atrophy. People can put products for distribution on
sourceforge or private sites.
Sourceforge is probably the worst way to make your software available from
an end-user perspective. sf.net has done amazing things for hundreds of
open source communities by making resources available, but the process of
obtaining a project status (whilst necessary to avoid project spam) is a
barrier to many, and the poor usability of their systems (we had to
explain to experienced developers how the sf.net tracker worked, they
didn't understand it, and the way they organise downloads is so confusing
people just give up) makes it difficult for many who are just looking for
things to download.
I would presume some crafty community
member might even come up with something; and then we can get feed data
or the like from them for display on the site.
Something like http://plone.org/products? We've had *huge* success by
making this tool available to people. By giving products a place to
organise themselves, people find them much easier. By giving them tools to
manage releases and roadmaps, and individual issue trackers that notify
the project owners when people submit bugs (all of this is optional)
maintainers are better at keeping their software up-to-date and more
responsive to their users.
zope.org should not be a member login based site IMNSHO.
Why not have a members.zope.org that is a community site, with wikis and
the lot, where the community can play their games, and a zope3.org and/or
a zope.org that is the outward facing part of the community, much more
tightly controlled for quality and consistency?
Zope-web maillist - Zopefirstname.lastname@example.org