Comments on: Marc Laporte coming to town http://djst.org/blog/2009/08/24/marc-laporte-coming-to-town/ David Tenser's brand new microblog Fri, 18 May 2012 02:14:38 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Thomas http://djst.org/blog/2009/08/24/marc-laporte-coming-to-town/comment-page-1/#comment-51480 Thomas Mon, 14 Sep 2009 21:34:40 +0000 http://djst.org/blog/?p=480#comment-51480 Hi, if it's possible to make a tikiwiki "SUMO productization suite" (an enhanced tikiwiki with some "modules" or something else to get SUMO as it is) then I would wish to do Plan A. Forking is waste of resources and migration - what could it do for SUMO? Hi,
if it’s possible to make a tikiwiki “SUMO productization suite” (an enhanced tikiwiki with some “modules” or something else to get SUMO as it is) then I would wish to do Plan A. Forking is waste of resources and migration – what could it do for SUMO?

]]> By: Majken "Lucy" Connor http://djst.org/blog/2009/08/24/marc-laporte-coming-to-town/comment-page-1/#comment-51105 Majken "Lucy" Connor Tue, 25 Aug 2009 22:58:10 +0000 http://djst.org/blog/?p=480#comment-51105 Well, I'm not sure if anyone is familiar with drupal *and* tiki, for example, who might be able to provide some insight as to which product is "superior" I think what it really comes down to is whether Mozilla would prefer a more modular product, like drupal or deki, or if we prefer the tiki philosophy, which has the trade off of knowing every feature we use will be compatible with the new version. Forking is almost inevitable, especially with the idea of productization. I think Tiki gives the highest chance of not needing to fork (or at least not having to maintain forks indefinitely), the issue with tiki is working out the development process so that everything is included upstream in the next release. If we go with something like drupal, chances are high that we'd end up maintaining our own modules, which is what's happening for SFx. In terms of user experience, any software we choose has the capability to have the same features, with the same layout and same design. IMO this decision is really one for webdev, esp if all options are open. Well, I’m not sure if anyone is familiar with drupal *and* tiki, for example, who might be able to provide some insight as to which product is “superior”

I think what it really comes down to is whether Mozilla would prefer a more modular product, like drupal or deki, or if we prefer the tiki philosophy, which has the trade off of knowing every feature we use will be compatible with the new version.

Forking is almost inevitable, especially with the idea of productization. I think Tiki gives the highest chance of not needing to fork (or at least not having to maintain forks indefinitely), the issue with tiki is working out the development process so that everything is included upstream in the next release. If we go with something like drupal, chances are high that we’d end up maintaining our own modules, which is what’s happening for SFx.

In terms of user experience, any software we choose has the capability to have the same features, with the same layout and same design. IMO this decision is really one for webdev, esp if all options are open.

]]>