Re: PloneSoftwareCenter DOAP

[Ramon Navarro Bosch <ramon epsem upc edu>]

There are two different aspects that must be maintained separatelly :

* DOAP xml template : It should be done with PSC equipment and on trunk
version. We can begin a new thread about the implementation .

  - doap_feed  : Simone do you have some first version of this template
? Do you have access to collective to upload it to trunk skin directory
? I think that is much better is we create it throw a Z3 Browser View on
a python script ( so we can use xmllib to parse it )

 ( DOAP definition :
http://www-128.ibm.com/developerworks/xml/library/x-osproj3/
   DOAP webpage : http://usefulinc.com/doap/ )

* LinguaPlone PloneSoftwareCenter : As I saw, PSC is not on LinguaPlone
product adapted, is it true Martin ? Can you help us adapting PSC on
LinguaPlone so we can use the same translation workflow in all WGO.

* PSC GnomeProduct adapt :

  - Skin : we should create a WGOSetup product where we can put all
PloneSetup xml stuff and the skinning necessary to adapt the different
products to WGO skinning. If we use PSC specific skinning on gnometheme
then we will not be using correctly on other plone site with this theme
and without PSC. Is anybody interested on create this configuration and
skining product ?

  - Fields : I think that we don't need to make any modification to
Archtype fields on PSC so we can use skinning to hide the fields we
really don't need. ( psc_project_view.pt ) .

  - Workflow, as Simone saig I think that we can use standard behavour
and play on plone-setup stuff to adapt PSC to our grups/workflows

As the version to use I suggest to use the trunk version that is working
fine.

Ramon


En/na Simone Deponti ha escrit:
> Okay,
>
> taking in consideration what Martin said, I've rethought some things,
> so my new proposal is:
>
> 1. The svn used for developement will be the collective (if you want
> to contribute and upload on the svn you'll have to obtain access there
> through the methods explained by Martin)
> 2. Branch the 1.0 Release on the collective svn as 1.0-doap-enabled.
> This branch will merely focus on giving doap support to PSC-1.0
> (meaning that our changes could be easily ported to 2.0 once it's out)
> 3. We will need to tweak lightly the workflows and the permissions,
> but I think those thing can easily be done in the ZMI and later
> exported/saved through the setuptool, so this work won't take place on
> the product itself.
> 4. All the modifications to meet the look & feel and interface
> guidelines of wgo (see http://live.gnome.org/GnomeWeb/GnomeProducts)
> will be added by either merging templates and styles in gnometheme or
> through the creation of those into another similar product
> (PloneSoftwareCenterGnome?), that acts like an extension to PSC in
> order to provide aesthetic/workflow customizations to PSC needed by
> wgo. Because as far as I can see, excepting DOAP, workflow and "how is
> the content displayed" seems to me that PSC meets all our needs.
>
> I still have a doubt about what version use as base to implement our
> template customizations (workflow tweaking is extremely simple to
> implement even by a non-plone guy, the only relevant matter might be
> auto-installation, which is why I proposed the creation of a product
> PloneSoftwareCenterGnome). My preference would go for bleeding edge
> svn in the hope to be able to have PSC 2.0 installed on our final release.
>
> Greetings,
>
> -- 
> <Ivyshaur> No, we've been informed that listening to Rammstein is the
> best way to learn German.
> <mrPants> You learn it very quick
> <mrPants> The problem is that you only know how to talk about sodomy,
> canibalism, incest, and death
> <granola> there are other things to talk about?
> <mrPants> Not in germany
> ------------------------------------------------------------------------
>
> _______________________________________________
> gnome-web-list mailing list
> gnome-web-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-web-list
>