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. 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. :) 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 tools such as UML We may also be able to pull in content by aggregrating in blogs from various people. Anything I'm missing? 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. 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? Regards, Martijn
Hosting: Nuxeo: Zope service provider