[Using Sakai] [Building Sakai] Playing with the 'Neo Portal' from Sakai 2.9

[Nate Angell]

Sorry for the long delay Chuck...that all sounds like good news. What
I really like is the way you've integrated courses into the
development process, thus introducing a new generation of folks to
Sakai development, where they may be fueled by curriculum to look at
these cross-cutting issues—hopefully the curriculum for UM SI622 -
Evaluation of Systems and Services includes evaluation of major
crosscutting concerns like accessibility. That way they are less
siloed activities. We can't all be experts in every area, so it's
great to see something like usability being addressed by new folks
near the beginning of development rather than as yet another task for
someone like Brian farther down the road.

- Nate

On Sun, Apr 3, 2011 at 8:31 PM, csev <csev at umich.edu> wrote:
> Nate,
>
> For the portal, Internationalization and accessibility are simply essential.  This is why I wanted to get working designs in folks hands so early in the 2.9 process.  In essence, most of the portal change work is now done (6 months before code freeze) so the reviews and details can be dealt with without rushing.  It is also why I made videos and put up example systems to play with - so we get a broad of a review of the work as possible and have plenty of time to adjust if things come up in the testing.  I don't want to be panicking in August.
>
> Actually next week we will get some feedback on the usability of the new portal.  Another class at UM (SI622 - Evaluation of Systems and Services) http://www.si.umich.edu/courses/description.htm?passCID=622 has one of its groups analyzing the existing and new Sakai 2.9 portal and doing user testing of the new portal as part of their class project all next week.   I think the 622 group might have as many as 23 people from a broad range of backgrounds who are experienced users of the current 2.x software taking a look at the neo portal.  They will be seeing it for the first time, unlike my SI791 (http://www.dr-chuck.com/si791-sak/) independent study class that designed and helped build the neo portal.  The feedback from a fresh set of eyes in a formal evaluation will be really helpful.
>
> In terms of accessibility, the portal team added Brian Richwine of Indiana as a committer for the portal.   Brian has made a lot of strong contributions to our accessibility both in the portal and across many of the tools.   Now that Brian has commit, he can just fix things directly in the branch (SAK-19813) or in trunk whenever he decides to take a look at the neo portal and do his analysis.   This way he does not have to submit a patch and wait until someone notices - he can just check it right in so we can move forward more effectively.
>
> Adrian also has commit on portal as that is where the neo chat lives - so he will be able to respond directly to issues as they are identified.
>
> /Chuck
>
>
> On Apr 3, 2011, at 3:05 PM, Nate Angell wrote:
>
>> Sounds good! I love it when things like accessibility and
>> internationalization are seen as central parts of the development
>> effort rather than afterthoughts. It may help with development if an
>> accessibility review is conducted earlier in the process in case
>> improving accessibility turns out to be more than just cleaning up
>> bugs. I'm betting the Sakai accessibility community would be glad to
>> help someone from the development team conduct a review sooner rather
>> than later.
>>
>> The chat work probably warrants a separate effort, but I'm betting
>> Adrian has that on his radar.
>
>