[Zope3-Users] Re: Re: Re: Please Guido, pick me, pick me!

2006-02-06 Thread Martin Aspeli
On Mon, 06 Feb 2006 06:15:45 -, Brad Allen  
[EMAIL PROTECTED] wrote:



By new website, do you mean a Zope 3 advocacy site, or a general
documentation site? Making a separate site for advocacy seems like
a no-brainer (ala Pythonology.org), but the documentation site is
another matter. Have the Zope 3 core developers decided to split
Zope 3 documentation onto a completely separate site? Maybe this
has already been discussed on the Zope3-dev list, which I haven't
yet looked at.


I think it's best if the documentation (esp. in the form of easy-access  
tutorials) is part of the advocacy. If you're advocating a development  
framework, the only thing that's going to sell it to developers is actual  
code - examples, demos, and a demonstration that there is sufficienet  
documentation there to make it possible for them to learn it (which  
includes pointers to the ++apidoc++ stuff!).


I'd say make a site that works on message, but make it possible to slot  
documentation in there. Also, solicit the help of the wider community -  
I'm sure many other people have thought about how this may work and how  
it'd best be presented to them.


Martin

--
(muted)

___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


[Zope3-Users] Re: Re: Re: Please Guido, pick me, pick me!

2006-02-02 Thread Martin Aspeli
On Thu, 02 Feb 2006 21:05:32 -, Stephan Richter  
[EMAIL PROTECTED] wrote:



No-one who doesn't  
already read this list has heard of Zope 3 (as in, they understand what  
 

it's all about, and they understand the distinction between Zope 2 and  
Zope 3) and very few have heard of Zope in general. They have, however,  
 

seen all the Ruby-on-Rails demos and are talking about it all the time.


Yeah, but honestly I don't care. If people choose a technology on name
recognition and not on technical merit, then it is their bad. However, I
question the RoR hype. I wonder whether big companies seriously  
considering
it; it has absolutely no track record. Zope 2 (and even 3) on the other  
hand

is deployed on many huge sites and the risk of deploying it is low. Even
deploying Zope 3 is a smaller risk than RoR.


And what if they've never heard about Zope 3 at all, what if it doesn't  
even come up in their discussions? The people that make the decisions  
don't necessarily have the time to research and try out every single  
framework out there. In fact, they almost never do.


The presumption that people will just find your technology may hold when  
there are only a few contenders, but there are dozens of web frameworks  
even in the python space, dozens more in the Java space, and don't even  
try to count the PHP ones. And there are many, many people who are  
approaching the search thinking they'd be more comfortable with PHP or  
Java (which they are more likely to have experience with than python) and  
think that, if they don't even promote this on their own web site, it  
must be marginal thing that I shouldn't bother with.


This happens. Every single day. I think it's short sighted not to care.  
How much better would Zope be if it had more real use cases, more  serious  
users and ultimately more contributors?


Why does Plone have so many users and such an active community? (hint:  
It's not because it's technology is de facto better than say CPSs...)


Note that I'm not saying that the same people who produce the code (and  
great code it is, which is why I care so much about this) should be doing  
this. In fact, the Plone experience tells us they probably shouldn't. But  
*someone* ought to, because it's a shame each time someone picks a less  
appropriate framework just because they didn't know Zope 3 existed or that  
it was complete (I didn't know it was complete until after Zope 3.1 was  
released, and I was actively writing Plone code at the time).


Martin

--
(muted)

___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users