On Thu, 2005-11-24 at 18:28 +0100, Lennart Regebro wrote: > Rakotomandimby Mihamina wrote: > >>- How will CPS 3.4.0 be bundled? A big tarball with every supported > >>product like currenly? Or a smaller bundle, with add-ons available on > >>the side? And in that case, what do we put in the bundle? > > I vote for a smallest bundle as possible, then people include what they > > want. > Well, there are two "targets" for the CPS bundle. People who want to try > it out,
CPS-Full > and people who have tried it out and want to use it. smallest/minimal bundle + one by one installed products/components. > To increase the interest, and make people go "hey this is pretty good", > I'm guessing a big bundle with loads of features would be good. Or? Because of the dependencies, it could hurt. I remember the times I had installed CPSOo: I did not noticed I needed pyxml and all the things. It's the same for CPSBlog/lxml. Yes, reading the doc/README before installong would ease the thing, but only few people read the doc. Too much bundled components require too much dependencies. Unless you will provide them in the bundle. -- A powerfull GroupWare, CMS, CRM, ECM: CPS (Open Source & GPL). Opengroupware, SPIP, Plone, PhpBB, JetSpeed... are good: CPS is better. http://www.cps-project.org for downloads & documentation. Free hosting of CPS groupware: http://www.objectis.org. _______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel
