[Building Sakai] New Sakai 2.9 Portal Trial Run - Video / Demo Server

[csev]

Earle,

That would be technically feasible but I would think it would be maddening for users and tech support alike (as well as developers maintaining the code) so I have avoided going down that path.  I also would like to in some future version only have one portal - so if we get users hooked on the switching back and forth - then we will need to wean them from the feature when we might want to do things in say 2.10 where tools increasingly depend on features that are only in the new portal.  I want the old portal to be frozen in time, not having to back-port new features/ideas.   Those new features would likely alter the skinning of the old portal - so that would make the old portal folks angry.  etc etc...

For 2.9, we won't make tool changes that only work with the new portal - but once we get experience with how the portal functions, we may want to make those changes to tools.  (i.e. like Adrian's suggestions about making profile sub menu items available in the portal).

The slippery slope would be that soon teachers would want sites to be able to switch and then ...gurgle....

My model is that this *is* the portal for 2.9 - but we are nice and allow people to delay the portal upgrade perhaps if they don't have time to reskin the new portal as part of an upgrade (the skin will be different).

Does that make sense?

/Chuck

On Mar 14, 2011, at 11:37 PM, Earle Nietzel wrote:

> Maybe there could be a toggle that is user controlled that way you could let them opt in to the "new" look and feel.
> 
> This will also give organizations a chance to get more feedback and a warm fuzzy instead of just throwing the old switch!
> 
> Very nice work,
> Earle