The application for the Google Summer of code has been submitted.
http://www.sakaiproject.org/soc2008/

Some Basic Ideas for Projects
The basic ideas focus on building simple but fully functional IMS LTI Consumer applications in a wide variety of environments as well as developing simple reference implementation(s) of the IMS LTI Producer. Depending on the skills and number of the selected students we may actually do quite a number of these projects.
Many of these tasks consist of downloading the software, learning the pattern for developing an extension for the program and then producing an LTI extension compatible with the Learning Management System.
Build an IMS LTI Consumer for Moodle
Moodle is a very popular open source Learning Management System written in PHP. Moodle is widely used in K12 and higher education. We would hope to produce a contributed tool which implements LTI Consumer for the Moodle community. Language: PHP
http://www.moodle.org (Ohloh)
Build an IMS LTI Consumer for ATutor
ATutor is an open source Learning Management System developed by the University of Toronto. ATutor pays particular attention to learners with different capabilities and is designed with accessibility and adaptability in mind. Language: PHP
http://www.atutor.ca/ (Ohloh)
Build an IMS LTI Consumer for Elgg
Elgg is a flexible social networking system which provides organizations with their own locally controlled instance of many common web tools such as WIki, Blogs, social networks etc. Language: PHP
http://elgg.org/ (Ohloh)
Build an IMS LTI Consumer for the Chisimba Framework
Chisimba is a web 2. 0 application environment particularly focused on functionality mash-up. Chisimba is developed at the University of the Western Cape in South Africa and is a follow on to the KEWL Learning Management System. Language: PHP
http://avoir.uwc.ac.za/ (Ohloh)
Build an IMS LTI Consumer for Drupal
Drupal is a content management system that has support for social networking. Drupal is used in many situations where an organization wants a portal with social networking capabilities.
http://drupal.org/ (Ohloh)
Build a Ruby Reference Implementation of LTI Consumer
This will truly be simply a reference implementation of the LTI software. This is some very initial work with an intent to build simple reference implementations for all IMS Specifications. Ruby Toozday is not intended as production-ready software – it is only a technology demonstrator. Language: Ruby
http://www.rubytoozday.org/ (Ohloh)
Build a Ruby Reference Implementation of LTI Producer
One of the advantages of being only a demonstrator is that it is much easier to modify and experiment. Ruby Toozday already has simple support for IMS TI Producer but this needs to be improved. We can use this effort to experiment with adding and using some run-time capabilities to IMS LTI. Another key focus of this effort is to understand and document the unique architectural, performance, and data modeling aspects of building an application to be mashed up using IMS LTI. Language: Ruby
http://www.rubytoozday.org/ (Ohloh)
Build an IMS LTI Consumer for Google Android
Dr. Chuck taught a Java class in Fall 2007 which experimented with building simple Google Android applications (www.si543.com) – we could expand the sample applications produced by this course to be a simple IMS LTI Consumer. Language: Java
Ideas: Advanced
Build IMS LTI Producer for Sakai
This effort will add the necessary capabilities for Sakai to export individual Sakai tools and sites as IMS LTI Producer endpoints. This will be significant work because of the changes to internal Sakai structures to support the new course provisioning demands which Sakai must handle to support LTI producer. Language: Java
Build IMS LTI Producer for Moodle
This effort will add the necessary capabilities for Moodle to export individual Moodle tools and sites as IMS LTI Producer endpoints. This will be significant work because of the the new course provisioning demands which must be handled to support LTI producer. Language: PHP
Explore Proxied Access for IMS LTI
Currently the IMS LTI standard describes provisions for iframe, popup and proxied access to LTI tools. However there is no specifications far for *how* the proxy version of tools would be accomplished. This work would start with a survey of the variaous proxy approaches such as ad hoc HTML proxying, Web Services for Remote Portlets (WSRP), Facebook Markup Language, Google Widgets, and other approaches. Based on this survey we would build simple proof of concept code demonstrating feasibility of the selected approach(es). Language: Various