Julien Anguenot wrote:
> Stefane Fermigier wrote:
>   
>> Fermigier Stefane wrote:
>>     
>>> There is also one important thing we plan to do: change a bit the way
>>> the packages are delivered. We plan to have the following packages:
>>>
>>> - CPSPlatform (or "CPS the framework"): minimal set of CPS components
>>> that enable the development of CPS applications (this is what is called
>>> currently "CPS-3-base", and contains mostly CPSCore, CPSDefault,
>>> CPSSchemas, CPSDocument, CPSUserFolder, CPSDirectories, CPSWorkflow,
>>> CPSRelation, CPSComment, and the CMF and other dependencies).
>>>
>>> This will be delivered only as .tgz.
>>>
>>> - CPS (or "CPS the application"): CPSPlatform + CPSBlog + CPSWiki + CPSOOo
>>>
>>> This one will be delivered as .tgz + .exe (Windows installer) + .dmg
>>> (for Mac OS).
>>>
>>> - Additional, complex to set up components like CPSSharedCalendar,
>>> CPSMailAccess and CPSCourier will be delivered separately.
>>>   
>>>       
>> To be more specific:
>>
>> CPSPlatform 3.4 will contain:
>>    CPSCompat
>>    CPSCore
>>    CPSDefault
>>    CPSDirectory
>>    CPSDocument
>>    CPSInstaller
>>    CPSNavigation
>>    CPSPortlets
>>    CPSRelation
>>    CPSRemoteController
>>    CPSRSS
>>    CPSSchemas
>>    CPSSkins
>>    CPSSubscriptions
>>    CPSUserFolder
>>    CPSUtil
>>    CPSWorkflow
>>    CPSI18n
>>    Zope Products
>>        Localizer
>>        PortalTransforms
>>        TranslationService
>>        CMF
>>        GenericSetup
>>        ExternalEditor
>>        FCKeditor
>>
>> CPS 3.4 will contain:
>>    CPSPlatform
>>    CPSBlog
>>    CPSWiki
>>    CPSForum
>>    CPSOOo
>>  
>>     
>
> What about CPSNewsLetters, CPSChat and CPSCollector ?
>   

OK, they seem to have been forgotten somehow.

>> And the following packages will live separated lives:
>>    CPSMailAccess
>>    CPSSharedCalendar
>>    CPSGeo
>>
>> We will also release, as separated packages, when they are releasable:
>>    Courrier
>>    OpenSpace
>>    WebPublisher
>>
>> Please comment.
>>     
>
> We need to think about the BBB layer (including CPSBoxes). Should we
> distribute it as CPS-3.4-compat like gcc does it with gcc-compat ? It
> could include CPSInstaller / CPSBoxes , the old CPSWebMail, CPSCalendar
> and whatever product needed to migrate ?
>
> What do you think ?
>   
Nice idea. 

BTW, I have a minor issue with the names (everybody knows that I tend o give a 
lot of thought about naming).

Should we name the packages with a dash, or not (CPSPlatform vs. CPS-Platform)?

I don't want people to confuse packages (= zope products) names with packages 
(= archives, like .tgz, etc.) names. Oups, that's already confusing :(

  S.

-- 
Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile).
Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps
Gestion de contenu web / portail collaboratif / groupware / open source!

_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel

Reply via email to