[Building Sakai] Core tools with significant planned 2.7 changes

[Clay Fenlason]

I see this going up now - http://confluence.sakaiproject.org/x/tIHgAw

Terrific, and thanks for setting a good example.

~Clay

On Wed, Jul 22, 2009 at 4:27 PM, Michael
Korcuska<mkorcuska at sakaifoundation.org> wrote:
> I would say this should go into the Forum tool space.  It can be tagged
> appropriately so all like documents can get pulled into one space somewhere
> else. Just an opinion, though, and happy to have it come out another way.
>
> Michael
>
> On Jul 22, 2009, at 12:01, David Haines wrote:
>
>> We are ready to start generating some pages to document the 2.7 Forums
>> changes from Michigan.  We plan to base the information on the
>> scorecard and the OSP feature template and to keep it in Confluence.
>>
>> Any suggestions on the proper location for these pages in Confluence?
>> We probably want a standard location for such documentation so that it
>> is easy to find.
>>
>> - Dave
>>
>> David Haines
>> CTools Developer
>> Digital Media Commons
>> University of Michigan
>> dlhaines at umich.edu
>>
>>
>>
>>
>> On Jul 20, 2009, at 11:39 AM, Clay Fenlason wrote:
>>
>>> Re: Forums, perhaps "sweeping set of changes" goes too far, but if I
>>> start digging into JIRAs and just read through SAK-13736 [1] I find a
>>> fair bit of back and forth about what's really happening, and what
>>> looks like a complex set of UI changes in a subtask (SAK-15535),
>>> issues raised off-list, etc. Just a first impression, but it reads
>>> like a significant volume of activity with some challenge of
>>> coordination, and a not inconsiderable refinement of the UX.
>>>
>>> Is there someone who would be in a position to fully document the
>>> user-facing change represented? It's not clear what every change
>>> listed means, exactly. It looks like Gonzalo might be the authority,
>>> but a number of things are happening there in parallel, and David made
>>> some attempt to knit them together in another umbrella JIRA ... I'm
>>> not sure who's in a position to draw it all together.
>>>
>>> ~Clay
>>>
>>> [1] http://jira.sakaiproject.org/browse/SAK-13736
>>>
>>> On Mon, Jul 20, 2009 at 11:19 AM, John Norman<john at caret.cam.ac.uk>
>>> wrote:
>>>>
>>>> The description of Forums in this message seems at odds with the
>>>> following quote from the page "A final release, Sakai 2.7 [...]  The
>>>> user experience will not undergo any drastic changes and will remain
>>>> relatively consistent through the end of the 2.x series to provide
>>>> stability for local documentation and training materials and
>>>> customizations"
>>>>
>>>> Looking at the page though, the changes listed read like less than
>>>> "sweeping set of feature and UI changes" - but that doesn't mean such
>>>> changes are not in the code...
>>>>
>>>> The K2 JIRA roadmap link appears to take me to the K1 JIRA
>>>>
>>>> The link to the preview of Sakai 3 functionality will need to be
>>>> updated from 3akai. I think Nico is going to update the demo server
>>>> for the 131.111.21.17 server in the next day or so. That will then
>>>> become the preferred preview for Sakai 3. At that point 3akai will
>>>> become a 'Proof of Concept' for which aspects of Sakai 3 work on
>>>> Sakai
>>>> 2. Some server renaming may be appropriate at that point.
>>>>
>>>> John
>>>>
>>>> On 20 Jul 2009, at 14:33, Clay Fenlason wrote:
>>>>
>>>>> I'm reviewing the list Peter collected of planned feature changes
>>>>> across various tools. [1]  The focus of this list is changes to
>>>>> existing code and capabilities, not, e.g., entirely new tools (I'm
>>>>> bracketing and setting aside that latter concern right now). So far
>>>>> the following stand out to me as areas of particular risk:
>>>>>
>>>>> (1) Forums - an apparently sweeping set of feature and UI changes,
>>>>> with involvement from IU, Michigan, and UCT
>>>>> (2) Site Info/Worksite setup - a set of changes which, while not
>>>>> dramatic, carry a greater risk because they touch on matters of site
>>>>> membership and site creation workflows
>>>>> (3) Skin/markup changes - it's not clear how significant these
>>>>> changes
>>>>> are, or if they're backward compatible, but there seems to be a
>>>>> strong
>>>>> need for both documentation and some skin testing
>>>>>
>>>>> I suppose I have a few questions, for those who know more detail -
>>>>> is
>>>>> that page accurate, and are there other things there on that page
>>>>> that
>>>>> catch your eye?
>>>>>
>>>>> --
>>>>> Clay
>>>>>
>>>>> [1] http://confluence.sakaiproject.org/x/6ICTAQ
>>>>> _______________________________________________
>>>>> sakai-dev mailing list
>>>>> sakai-dev at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>
>>>>> TO UNSUBSCRIBE: send email to
>>>>> sakai-dev-unsubscribe at collab.sakaiproject.org
>>>>> with a subject of "unsubscribe"
>>>>
>>>> _______________________________________________
>>>> sakai-dev mailing list
>>>> sakai-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>
>>>> TO UNSUBSCRIBE: send email to
>>>> sakai-dev-unsubscribe at collab.sakaiproject.org
>>>> with a subject of "unsubscribe"
>>>>
>>>
>>>
>>>
>>> --
>>> Clay Fenlason
>>> Director, Educational Technology
>>> Georgia Institute of Technology
>>> (404) 385-6644
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org
>>> with a subject of "unsubscribe"
>>>
>>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>
> --
> Michael Korcuska
> Executive Director, Sakai Foundation
> mkorcuska at sakaifoundation.org
> phone: +1 510-931-6559
> mobile (US): +1 510-599-2586
> skype: mkorcuska
>
>
>
>