[Building Sakai] 2.8 potential scope

[David Horwitz]

This is a not a comment on the merits of any of the functionality
mentioned, but can we please actually consider what we have the capacity
to support, qa, and release? We seem to always run away with what we
would like to see in the release without pausing to consider that the
release is already larger and more complex than we can deal with ...

D

On 05/25/2010 03:34 PM, Speelmon, Lance Day wrote:
> 1) I would push strongly to include all hybrid related code in the 2.8 release. The hybrid code will run on many previous versions of Sakai, but it would be nice to include it in a release.
>
> 2) I find the statement about "LTI producers at the tool-level" confusing, but I think we are in the same ballpark.  There are some things we can do in Sakai 2 which will not only make it a better product but will also make for a better migration path to Sakai 3. This may include additional LTI work, but should also include entity picker-like [1] functionality.
>
> Thanks, L
>
> [1] http://wiki.sakaiproject.org/display/SAKDEV/Entity+Picker
>
> Lance Speelmon
> Scholarly Technologist
>
> On May 25, 2010, at 9:15 AM, Clay Fenlason wrote:
>
>   
>> LTI producers?: the success of hybrid mode experimentation using LTI
>> suggests we might make real progress for community migrations paths
>> and early S3 adoption. I may be wrong about this, but I'm under the
>> impression that we'd want to write LTI producers at the tool-level in
>> 2.x, and some of them may be appropriate for 2.8.
>>     
> _______________________________________________
> 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"
>