Re: [Tikiwiki-devel] [Fwd: SVN advice re users directory]

[Gary Cunningham-L. <ga...@cu...>]

Version info can be indicated now for files or packages in mods, as can 
be seen on http://mods.tikiwiki.org/ . The Admin Mods interface has a 
similar list. The version information can go in the "version" column 
(probably the best place) or in "description". Looking at the files 
there now, it's apparent that in some cases the version might have meant 
Tiki release compatibility, and in other cases the author had some 
version system going for his files separate from Tiki releases. The 
files could be tested and Tiki release compatibility could be indicated 
consistently.

The problem with themes (and potentially other things like modules or 
wikiplugins) is that when Tiki 3 is released, there will definitely be 
two distinct packages available for at least the themes I'm maintaining, 
the current Tiki 2 version and the coming Tiki 3 version. If some people 
do actually use the mods admin feature to get the files, then I guess 
both versions will have to be kept in mods svn. So should a naming 
system be used, like mods/trunk/themes/andreas08_TikiWiki2 and 
mods/trunk/themes/andreas08_TikiWiki3? Or should the mods hierarchy be 
changed, like mods/trunk/themes/TikiWiki2/andreas08 and 
mods/trunk/themes/TikiWiki3/andreas08? I think it was also said that the 
admin mods feature might be made smart enough to read the version info 
and only list the files compatible with the Tiki version being used at a 
site, which would solve the problem on the site admin side as long as 
the file authors know where to put the files in the hierarchy and how to 
identify them in the package info files or wherever. This needs to be 
figured out before the Tiki 3 release. In the meantime, I'll make a 
users/chibaguy directory for themes in progress for Tiki 3 (as described 
in my post) unless someone tells me this is not a good idea.

-- Gary

Xavier de Pedro wrote:
> Hi Gary and all:
>
> I think that version info for mods compatible with certain 
> version/branch of Tiki is needed, so that people with 2.x for some time, 
> should be able to find comaptible mods on mods.tw.o, and something 
> similar for tiki 3.x and mods compatible with that branch (when it will 
> be stable), etc. .
>
> For instance, nowadays, some sites still run 1.9.11 with some mods, and 
> some others with 2.x, and mods.tw.o doesn't say anything about wich tiki 
> version they work with (see the case with AulaWiki, 1.5 is the last one 
> working with 1.9.x, and 1.6 is kind of half broken but in process to 
> work with 2.x)
>
> My 2 cents
>
> Xavi
>
> -------- Missatge original --------
> Assumpte: 	[Tikiwiki-devel] SVN advice re users directory
> Data: 	Sun, 23 Nov 2008 18:07:20 +0900
> De: 	Gary Cunningham-Lee <ga...@cu...>
> Respon a: 	Tikiwiki developers <tik...@li...>
> A: 	Tikiwiki developers <tik...@li...>
>
>
>
> Hi Subversion gurus,
>
> I'd like to have an svn repository for my themes being worked on for 
> Tiki 3. This would be like mods except it would have file compatibility 
> with trunk rather than branch 2.0. Can I add an svn 
> tikiwiki/users/chibaguy/ directory for this? It doesn't need to be a 
> full branch, only a hierarchy similar to mods, something like
>
> chibaguy
>   themes
>     abse
>       styles
>         abse
>       templates
>         styles
>           abse
>     andreas08
>       ...
>
> It wouldn't need to be merged at any time. These theme files would be 
> moved to mods when Tiki 3 is released (and Tiki2-compatible theme files 
> now in mods probably will be compressed and moved to themes.tw.o file 
> galleries for archive purposes). In this connection, to make mods less a 
> graveyard, probably all old, unmaintained themes there could be archived 
> at themes.tw.o also, so in principle all themes at mods would be 
> compatible with current Tiki releases.
>
> -- Gary
>