ZopeEvaluator
An Evaluator:
- Is a curious user, or a technician in a company who was appointed to evaluate Zope for their projects.
- Doesn't know how Zope works or how to use it.
- May not know anything about Python.
- Usually is savvy with regard to web/internet technologies.
- May not have any OOP background, or perhaps just Java.
- May need to prepare a presentation and mockups.
- May need to teach other people to use Zope.
Goals:
- LearnHowToUseZope
- Jim
- I'm not sure an evaluator would want to learn how to use Zope
- Tom
- Agree, he doesn't need to know how to use it, but he should get a global idea
- LearnHowZopeIsUsed?
- LearnWhatZopeCanDo?
- CreateADemoSite?
- LearnHowToCustomizeComponents?
- Jim
- Again, I think they want to know at a high level how this is done. I don't think they really wantto learn how to do it.
- Tom
- Agree, they only need to say how easy it is to customize, extend and create components
- and a case-by-case selection of Goals from all other users.
- Jim
- I'd be careful here. I think that once they have the other goals, they are no longer evaluators.
- Find some ready-to-use examples of website type
- PaulT? (Jan 4, 2003 7:16 pm; Comment #1) Editor Remark Requested
- The easiest thing to attract Zope Evaluator is to give him a broad
list of
- attractive - complex - general purpose
Web applications. (Being complex helps, because chances are that there would be not too much competition).
Examples of such applications could be (in no partucular order) :
Squishdot Blog Forum Portal LiveJournal? clone Image Album VirtualHosting Plug and Play Ecommerce Groupware for editing, say, PDF documents
The old rant http://www.pault.com/X/983148775/index_html Consisted of two parts:
- Componentization of Zope ( partialy addressed by DC with Zope v 3 - great job )
- Applications sell the paltform. Applications is what made Windows a success. ( that part was not really addressed by DC during last year )
