[Building Sakai] 2.7 Release Discussion - Basic LTI Portlet

[Clay Fenlason]

In addition to having doubts about how quickly the PC process can be
accomplished, I guess I'm also assuming that since the explicit goal
of 2.7 is the refinement of existing tools (i.e. those already in 2.6)
by the end of 2009, that working in a new tool or capability or tool
on that timeframe is unlikely.  It doesn't rule it out, but I don't
think the QA and release management folk are going to feel that they
have more than enough time to deliver on that former goal.

So no, not automatically, but as things stand it seems to me the most
realistic expectation (with possible exceptions) that 2.x things that
go to the PC are generally on a track toward 2.8 or later.  wdyt?

~Clay

On Mon, Aug 3, 2009 at 4:51 AM, Stephen
Marquard<stephen.marquard at uct.ac.za> wrote:
> Hi Clay,
>
> I'm not clear on why a referral to the PC automatically pushes this into a 2.8 rather than 2.7. Are you making some assumptions about how long this process would take?
>
> Regards
> Stephen
>
>
>
>
> Stephen Marquard, Learning Technologies Co-ordinator
> Centre for Educational Technology, University of Cape Town
> http://www.cet.uct.ac.za
> Email/IM/XMPP: stephen.marquard at uct.ac.za
> Phone: +27-21-650-5037 Cell: +27-83-500-5290
>>>> Clay Fenlason <clay.fenlason at et.gatech.edu> 8/3/2009 8:03 AM >>>
> Thanks for filling in some of the gaps, Chuck, and now just a
> follow-up to say that I've got this on the list of things to be
> considered [1].  As a new tool this needs to go to the Product
> Council, and with the release roadmap being pursued for the coming
> year [2] it could be reviewed in time for a Q2 release in 2010, but
> that will be 2.8 and not 2.7. The PC still needs to lay out clearer
> criteria, but the upshot is that there is a little more time to work
> this out.
>
> I've also heard from John Leasia that there are a couple
> department-specific apps being supported by this in production at
> Michigan, and that it would be fair to say that other Michigan
> resource would support this work if the need arises. I think he said
> that Matthew Jones is familiar with it - hope I didn't hear that
> wrong.
>
> ~Clay
>
> [1] http://confluence.sakaiproject.org/x/j4LgAw
> [2] http://confluence.sakaiproject.org/x/CoLgAw
>
> On Wed, Jul 22, 2009 at 11:08 AM, csev<csev at umich.edu> wrote:
>> Clay/Stephen:
>> With a few cups of coffee in hand I made good progress this morning on
>> nailing my "missing bits" on my self-assessed BasicLTI scorecard.
>> o I internationalized everything in the portlet
>> o I wrote some administrator documentation - which roughly doubles as a
>> simple test script
>> o Further cleanup and turning debugging into log.debug
>> What I have yet to do is:
>> o Write the help entry - this should be easy because the tool is so simple
>> and the help is pretty much a subset of the admin doc - but I don't exactly
>> know our process for doing this.
>> o Engage in getting some non-English translations before release (nice to
>> have)
>> I would think that it would be easier to get internationalization resources
>> if the PM/PC indicated that this "had a decent chance" of getting in.
>> We will put this into production at Michigan in the next roll after 2.6
>> comes up - I am happy to interact with folks (and make a tag) if anyone
>> wants to put this in their build and do some further testing.
>> There is little likelihood that this will cause a performance problem
>> because (a) it only uses tool properties and has no additional tables or
>> SQL, and (b) the SimpleLTI version of this approach has been in production
>> for nearly a year at Michigan with no ill effects.
>> I expect that with the extremely small code size and low complexity of this
>> addition that I can commit to at least two years or more of fully supporting
>> this tool to the community with assistance and bug fixing.  I also fully
>> expect to add similar capabilities to Sakai 3 when the time is right.  I
>> already did a feasibility experiment of how to add this feature to Sakai 3.
>> http://www.dr-chuck.com/csev-blog/000626.html
>> https://source.sakaiproject.org/contrib/csev/trunk/sling/
>> So I am open to comments from the PM, the PC, or the community - and I
>> propose to include this in 2.7 and am awaiting being told where to start.
>> Here is the source code:
>> https://source.sakaiproject.org/contrib/csev/trunk/basiclti/
>> Here is the documentation:
>> https://source.sakaiproject.org/contrib/csev/trunk/basiclti/docs/sakai_basiclti_portlet.doc
>> Let me know.
>> /Chuck
> _______________________________________________
> 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"
>
>