Fabian Guisset wrote:
...
> moz.zope.org is currently being developed by a (very) small group of 
> people. We are working to get a demo of the site (layout, framework, and 
> content) up and running, so that mozilla.org can decide whether it is 
> suitable for production use.
> So moz.zope.org is currently not the "future mozilla.org" but it might 
> become soon.

I sincerely hope so, Fabian - it's a good framework for content 
development - but given the current state of affairs, it won't happen 
without some heavy lifting, IMO.  Still, i'm up for the challenge, if 
you-all are!  |/|/

> What's already there:
> - The Zope server fully configured
> - The framework to add/edit content (still needs some tweaking)
> - The workflow (i.e. permissions and privileges)
> - The URI structure

W/r/t your points 1 and 4: i don't doubt it.

W/r/t point three, i have to say:  if the basic workflow is what's 
implemented, then i don't get it.  Within the realm of "my stuff," i've 
created a few objects (two news items, and a mod. to my default index 
page), but can't publish them:  When i select the items and command 
"publish", i get a response of "No workflow provides the "publish" 
action."  And, while i can view the list of members (only when logged 
in, but not when anonymous - as it should be, IMO), i cannot see anybody 
else's stuff;  i have clicked on several users' names (e.g. yourself, 
Gervase, random others), and i get  only an authentication screen, which 
does not allow me to pass (FYI: my username is "wludwick"), i get the 
"unauthorized" error msg in response ("You are not allowed to access 
listFolderContents in this context").

W/r/t your point 2:  True enough that there *is* a framework for adding/ 
editing content - and it *does* need "some tweaking."  I've already got 
several pages of notes on tweaks that appear to me as necessary, on the 
basis of my own quite superficial experience with the app thus far. 
But, in light of the last pgph, i'm wondering how i'm supposed to share 
this stuff in context (or as close to it as possible)?  Am i to post 
such minutae to this list?  Or rather, in the "eat your own dogfood" 
spirit (a concept that mozilla.org has done much to propegate; i for one 
have certainly drunk the kool-aid), would it not be better to get 
workflow enabled at moz.zope.org to facilitate such sharing?  |/|/


> What still needs to be done:
> - The layout (template + css + python scripts)
> - Add more content

Amen on both counts.  I want to help on both these scores, but i think 
that a certain amount of action on the latter score must precede 
constructive work on the former - which obviously can't happen until 
these workflow problems are ironed out.  I for one would much rather see 
crude-but-effective at this point, rather than pretty-but-useless.  To 
invoke a quote that's become axiomatic in CMS circles "It's about the 
content, stupid!"  :-)   |/|/

> That's basically the status of the project.
> 
> Hope I "shed some light" :-)
> 
> -Fabian

Thanks for the update, Fabian, it was indeed illuminating.  I hope you 
feel likewise about my feedback, and will accept it in the constructive 
spirit intended.  NB:  I'm commmitted to both Mozilla as a browser and 
Zope as a platform for content management - moreover, i believe that 
they can make such beautiful music together as the world is still dying 
to hear - so whatever it takes to make this moz.zope.org project work, 
i'm with ya, dude.


|/|/alt


Mozilla 1.0 Release Candidate 1
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0rc1) Gecko/20020417




Reply via email to