-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martijn Faassen wrote: > Julien Anguenot wrote: > [snip] > >> Find below a proposal for the portal : > > > [snip long list] > > I am somewhat worried that doing all of this now will spread the content > too thin. I.e. that there will be so many areas but with little actual > content, so that someone visiting the site can click around a lot and > not get to the meat quickly enough. This is not a good impression. yup we can create the structure and open it to the public when we'll have some content to put within. (rights restrictions) It's just a working structure. > > Could we focus initially on getting the content in a few limited places > and see what shape it takes, then broaden out? I'm not saying this to > limit technical requirements, for those who have followed the previous > discussion. :) ok no problem. > > Concerning design content, we seem to have the following kinds of > artifacts: > > * mailing list. > > * images, such as graphs and the like. > > * textual documents. > > * perhaps output of some design tµµols such as UML yup forgot this. > > We may also be able to pull in content by aggregrating in blogs from > various people. Anything I'm missing? Don't see anything else right now. > > I myself tend to prefer restructured text documents in a svn repository > for lightweight design that's tied in with code, as that is easy to > edit, diff and version control, and easily accessible developers. Having > the other artifacts near that makes it easier to manage. The advantage > is that it's simple and that most people involved already know to deal > with this. > - -1 for me on rst documents for specifications and design docs. My idea with Dockbook and OOo is that we'll be able to have a documentation quite easily in various formats and provide it directly to the public while writing them. Nobody's in the Zope commnunity is really good at documentation because we don't have a lot of available ressources for writing it. (maybe Plone is an exception on this ;) ) As well, we have in here style sheets and helpers for OOo that can help us generating dockbook directly from OOo. It's just a methodology to adopt. And Dockbook is more sexy than rst while targeting outside developers ;) This is an open question we need to discuss I agree. > As for the website, my personal preference would be that we see this as > a publication medium primarily and not as a collaboration medium. We > could for instance use CPS for publishing "finished" design content to > the web for public consumption and the like, and to draw new people into > the project. > > The alternative which I think is presented is to use the collaboration > features of CPS to do this. I myself do not have a lot of experience > with these. What do others think? yup Why CPS ? Because : 1. It proposes everything almost out of the box. (Just need to add the specific content types and the layout) 2. Jean-Marc and I proposed to setup the portal and we can have it running by this week-end. 3. it proposes both collaborative and publication features all in one. Let's not fight again for the the portal technology... :( but let's focus on the functional aspect of this portal to have a productive environement for us with a nice professional looking skin that can allow us to start working next week. The ultimate goal will be to migrate all this to a Zope3 / ECM technology in couple of months for dog food ;) J. - -- Julien Anguenot | Nuxeo R&D (Paris, France) CPS Plateform : http://www.cps-project.org mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFChPcsGhoG8MxZ/pIRApPvAJoCbiG4C1g7S4BfXE3T7gTc+qXZkQCeIFEH iuXbkOC8dkfE7FHkOZ2f1UU= =q9KI -----END PGP SIGNATURE-----
Hosting: Nuxeo: Zope service provider