[Building Sakai] 2.8 potential scope

[Clay Fenlason]

Right, there's the old chicken and egg thing ... actually more than
two, so maybe chicken, egg and shell. In our case, the what, when, and
who. Whos don't commit themselves without knowing what and when, while
it's hard to know when without knowing what and who, and so forth.

As Anthony says, start with the aspirational, and then afterward
assign a ballpark figure of resources and timeline, which I expect
will serve as a dash of cold water. And then we pare back to
achievable desirables and timeframes. The aim will be to march us to
the point where we can get firm institutional commitments at or around
the conference, and a credible plan proposal coming out of it with
known resources, scope and calendar (or alternative options of same).

I'll work more of this into the wiki, including notes about process,
and will return to ask for more help fleshing it out.

~Clay

On Tue, May 25, 2010 at 11:33 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
> I think it is important to first capture aspirations and then sync them to reality.  Of course, this presupposes that a general frame exists in which to align one's thoughts regarding needs, scope and likely resources.  In this regard, I think it important to propose up front one or more release timelines.  A December 2010 2.8.0 release (impossible you say) will I suspect look a lot different than an April 2011 2.8.0 release.  But I think it useful to stake out potential time blocks for folks to consider.  What are your thoughts here?
>
> I recognize that this is the jump off point for our 2.8 discussions but I recommend that you send your "2.8 potential scope" to all lists, not just sakai-dev.  It's important to engage the entire Community right from the start regarding 2.8, not just the technical crowd.
>
> Cheers,
>
> Anth
>
>
> On May 25, 2010, at 9:48 AM, Clay Fenlason wrote:
>
>> Yes, David, that's going to be part of the discussion and planning.
>> Just trying to bite off one thing at a time for now.
>>
>> ~Clay
>>
>> On Tue, May 25, 2010 at 9:39 AM, David Horwitz <david.horwitz at uct.ac.za> wrote:
>>> 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"
>>>>
>>> _______________________________________________
>>> 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"
>>
>>
>
>