[Yanel-dev] organization of data

Michael Wechner michael.wechner at wyona.com
Mon Feb 25 21:15:56 CET 2008


Josias Thöny wrote:

> Evaldas Taroza wrote:
>
>> Hi,
>> Maybe we should think about how to better organize data in the 
>> repository. I mean we need some conventions. Currently we just put 
>> everything into /data and that's it. So javascripts, xslt, jelly, css 
>> together with the actual content gets there. I don't think it is 
>> nice. Because some of the scripts (like jelly, xslt) belong to some 
>> of the content and is not reusable, so they should lie somewhere 
>> logically close to each other.
>
>
> I see your point but I think there are always different ways to group 
> things.
> In one of our projects most of the js/xslt/css/img is reused between 
> different resource types/usecases, and only the jelly is completely 
> specific. In this case I don't know if it makes sense to group the 
> different files according to resource type.
>
> Anyway, if you think the reorganization is useful for you, feel free 
> to do it.
>
> Maybe something related:
> Would it make sense to split the repo content into actual 
> user-editable content and application-specific stuff?
> Let's say we add two folders to the repository:
> /content/
> /app/
> Now all the xslt/jelly/js/css goes somewhere into /app/ and the 
> user-editable content goes into /content/
>
> This would simplify upgrades of an installation where one needs to 
> upgrade e.g. some xslt but wants to keep the content which was created 
> by the users.
>
> I know in some projects the application files like xslt or css may be 
> editable for users. In this case this separation doesn't make much 
> sense, but on the other hand many projects don't allow users to edit 
> xslt.
>
> Or should we use two separate repositories?
>
> I'm not sure if this is a good solution but I consider the current mix 
> a real problem for upgrading.


I also see the problem, that it depends very much on the situation.

First of all I like the idea of using/introducing protocols/schemes to 
resolve "files".

Second I would suggest to write some best practice documentation.

Third I would suggest to introduce a file describing what files need to 
be upgraded (e.g. could also be an ant based file, e.g. upgrade.xml) 
which is standardized and can be used by an automatic build process.

Fourth I still believe CHANGELOG files are useful for humans to 
understand what needs to be upgraded.

Fifth I like the idea of a dedicated repository as Josias is suggesting, 
but I am not sure either if it is really necessary if the above 
suggestions are done properly.

WDYT?

Michi

>
> WDYT?
>
> josias
>
>>
>> I saw Josias is using some layout according to usecases.
>>
>> Has anyone suggestions about the conventions?
>>
>> Evaldas
>>
>
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management - Yanel, Yulup
http://www.wyona.com
michael.wechner at wyona.com, michi at apache.org
+41 44 272 91 61



More information about the Yanel-development mailing list