[xwiki-devs] Which skins do we want to support?
Hi, We need to decide which skins we want to support/maintain. By support/maintain I mean fixing bugs and improving them. Right now we have 3 skins in the platform: - Albatross - Toucan - Colibri We still need to keep it in platform for now since others depend on it but the question of knowing if we support it or not is independent IMO. Several questions: * Are we still supporting the Albatross skin? * Same question for Toucan? * We could decide not to support it but to apply contributor patches for it. * We could also decide that we don't support it and close jira issues related to it with won't fix. My feeling: - Keep it in platform for now, keep jira issues, apply patches, don't break what exists (when we change template files or CSS files for ex). WDYT? Thanks -Vincent
On 01/23/2010 10:00 AM, Vincent Massol wrote:
Hi,
We need to decide which skins we want to support/maintain. By support/maintain I mean fixing bugs and improving them.
Right now we have 3 skins in the platform: - Albatross - Toucan - Colibri
We still need to keep it in platform for now since others depend on it but the question of knowing if we support it or not is independent IMO.
Several questions:
* Are we still supporting the Albatross skin?
Not really. There are several UI components that don't work well in Albatross, although I usually check before committing new stuff, so that it looks acceptable, if not perfect. The problem is that other skins still depend on images from Albatross, and we need to hunt down all such code and update it to link to images from resources/icons/
* Same question for Toucan?
Toucan is supported but not maintained, meaning that innovation does not happen in Toucan, but new stuff that should be skin-independent should (strong should) be checked in Toucan, too.
* We could decide not to support it but to apply contributor patches for it.
I think we should keep the current strategy for a few more releases (full drop in 2.5?)
* We could also decide that we don't support it and close jira issues related to it with won't fix. My feeling: - Keep it in platform for now, keep jira issues, apply patches, don't break what exists (when we change template files or CSS files for ex).
+1 (for Toucan). For Albatross, we can just close old issues. -- Sergiu Dumitriu http://purl.org/net/sergiu/
On Sat, Jan 23, 2010 at 10:00 AM, Vincent Massol <[email protected]> wrote:
Hi,
We need to decide which skins we want to support/maintain. By support/maintain I mean fixing bugs and improving them.
Right now we have 3 skins in the platform: - Albatross - Toucan - Colibri
We still need to keep it in platform for now since others depend on it but the question of knowing if we support it or not is independent IMO.
Several questions:
* Are we still supporting the Albatross skin?
I usually check that it still works well before commiting stuff, recent apps which use ssx usually looks weird in albatross though.
* Same question for Toucan? * We could decide not to support it but to apply contributor patches for it. * We could also decide that we don't support it and close jira issues related to it with won't fix.
My feeling: - Keep it in platform for now, keep jira issues, apply patches, don't break what exists (when we change template files or CSS files for ex).
I agree with Sergiu, +1 for toucan. Related post: http://markmail.org/message/45dh7hhot7uefk66
WDYT?
On Feb 1, 2010, at 2:39 PM, Jean-Vincent Drean wrote:
On Sat, Jan 23, 2010 at 10:00 AM, Vincent Massol <[email protected]> wrote:
Hi,
We need to decide which skins we want to support/maintain. By support/maintain I mean fixing bugs and improving them.
Right now we have 3 skins in the platform: - Albatross - Toucan - Colibri
We still need to keep it in platform for now since others depend on it but the question of knowing if we support it or not is independent IMO.
Several questions:
* Are we still supporting the Albatross skin?
I usually check that it still works well before commiting stuff, recent apps which use ssx usually looks weird in albatross though.
I've added a warning on http://code.xwiki.org/xwiki/bin/view/Skins/AlbatrossSkin Thanks -Vincent
* Same question for Toucan? * We could decide not to support it but to apply contributor patches for it. * We could also decide that we don't support it and close jira issues related to it with won't fix.
My feeling: - Keep it in platform for now, keep jira issues, apply patches, don't break what exists (when we change template files or CSS files for ex).
I agree with Sergiu, +1 for toucan. Related post: http://markmail.org/message/45dh7hhot7uefk66
WDYT?
participants (3)
-
Jean-Vincent Drean -
Sergiu Dumitriu -
Vincent Massol