Re: [Zope-dev] Introducing ZopePrints.
Erik Enge <erik@esol.no> wrote:
Some of us over at ZopeZen.org (<URL:http://www.zopezen.org>) have been discussing the fenomena that is called ZopePrints. I'll give a brief explanation, and would appretiate feedback as to whether this a good idea or not.
A ZopePrint is a document, or maybe a set of documents, which describes a part of, or the complete development process for a Zope application. This could include the whole process from when the customers tell you they want to do project X with you, till you actually finish it and it's up and running in the customers offices.
Some points may be:
* Problem definition * Problem analysis * Project management (Resource allocation) * Design phase * Zope design * Test phase
(Have a looksy at <URL:http://www.zopezen.org/SDot/981475769/index_html> to check out all the suggestions, and my initial post.)
The rationale behind this is that the community at large would benefit from this by having _real_life_ case studies so when their time has come to implement an application in Zope, they don't fall into the same traps and pitfalls we did. Instead of benchmarks, the Zope community would use implementation documents to decide whether Zope is up for the job or not, that's what really helps.
I'm quite sure that it will also work as a tool for finding gaps and holes in either Zope or its tools and Products.
We would like to start a project going in the Fishbowl which aims at creating the right tools to document a project as described above.
Feel free to make suggestions!
Funny you should mention that :) We have been working on just such a site, using the PTK^H^H^HCMF as a tool for managing its own project artifacts. We are calling the project the "CMF dogbowl", as it is a cross between the Fishbowl process and the "eat your own dogfood" mantra made famous by the Mozilla team. Please see: http://dev.zope.org/Projects/PTK for our work-in-progress. Note that this is a separate Zope instance from the rest of 'dev', and that your existing zope.org membership is not (yet) valid there. Tres. -- =============================================================== Tres Seaver tseaver@digicool.com Digital Creations "Zope Dealers" http://www.zope.org
[Tres Seaver] | Please see: | | http://dev.zope.org/Projects/PTK | | for our work-in-progress. Hey, looks like what I'm after. I can see that it's a work in progress, so if you need any help, give me a shout. It didn't say too much about the project itself, do you have any such information on a page somewhere? Timescales? Goals?
On 12 Feb 2001, Erik Enge wrote:
[Tres Seaver]
| Please see: | | http://dev.zope.org/Projects/PTK | | for our work-in-progress.
Hey, looks like what I'm after. I can see that it's a work in progress, so if you need any help, give me a shout. It didn't say too much about the project itself, do you have any such information on a page somewhere? Timescales? Goals?
Thanks for pointing out the empty "Overview" -- in moving from the last, "PTK" version to the new, "CMF" version, I inadvertently left the description behind. As for timescale, we are planning to release CMF 1.0 at the end of this month. The exact deatils of the dogbowl site are still in flux (some want it to be at "cmf.zope.org", for instance). We also expect to have the membership integrated with the main zope.org stuff Real Soon Now. The core of the idea is that project artifacts are content, just like other content, and can be managed using the same tools. Tres. -- =============================================================== Tres Seaver tseaver@digicool.com Digital Creations "Zope Dealers" http://www.zope.org
participants (2)
-
Erik Enge -
Tres Seaver