Sakai Summer of Code - OhioLINK

On Apr 26, 2006, at 10:02 PM, Peter Murray wrote:

[SNIP]

> If there is a way OhioLINK could be
> of help by sponsoring a Summer of Code intern to complete a roughly
> 12-week chunk of work, please let me know.

Peter - this bit stuck in my head all night long :)

There are a bunch of things that can be done with this type of  
resources.  So I grabbed a cup-o-joe this morning and core-dumped a  
list of Summer-of code projects.  It is in my blog at http://www.dr- 
chuck.com/csev-blog/000150.html but I include it here as well.

Thanks for pushing this idea.

/Chuck

April 27, 2006

Sakai Summer of Code Projects

Here is a list of projects in Sakai that coudl be done by a talented  
individual in a fixed period. All of these efforts are on Sakai's  
long-term roadmap but none are on the short-term roadmap. Generally  
these are not in the "Sakai core" areas - they add functionality  
rather than trying to refactor existing mature technology so they can  
be done without requiring much coordination with the rest of Sakai.

Each of the tasks would be useful even if partially completed. Each  
of the tasks would naturally fit in a Sakai contrib area. Each of the  
tasks are relatively simple to describe at a high level but would  
require any individual to do a lot of research to figure things out.  
That individual should not expect to be "spoon fed" all the decisions  
and design - and just sit and code. Part of the challenge is to truly  
figure out "what to do" and "how to do it".

The individual should expect reasonable mentoring to get high level  
questions answered but should expect to be looking at a lot of code  
in the beginning of the effort. A key aspect of the sumer of code is  
that people taking these tasks cannot be a "drag" on existing  
resources executing the short-term roadmap. High level mentoring can  
come from me and others and tactical mentoring should come from the  
Programmer's Cafe group.

If folks want more detail - let me know - I am perfectly happy to  
have an hour-long phone call with anyone who is ready to spend a  
sumer or more working on any of these tasks - but until a resource  
shows up - these will continue to sit on the back-burner.

At least now I have a list. Someday I should put these into the  
requirements - but they are hardly "requirements" at this point -  
they are "things that would be cool to have".

Sumer of Code Task List from Chuck

Build a set of HTTPUnitTests for Sakai Functionality

Integrate JackRabbit's WebDav in Sakai

Add Pluto to Sakai (JSR-168 Support)

Extend the Sakai JSR-168 portlets to implement delegated security

Add Charon-like functionality to Sakai's WSRP Producer

Set of Joomla Utilities to gateway between Joomla and Sakai

Set of Plone Utilities to gateway between Plone and Sakai

Build a Working with Sakai in PHP kit

Build a Working with Sakai in Python Kit

Build a Working with Sakai in Ruby kit

A Sakai Portal that does HTTP Proxy (i.e. eliminates iFrames)

Build support for IMS Tool Interoperability Producer into Sakai

Build support for IMS Tool Interoperability Producer into Moodle

Build support for IMS Tool Interoperability Producer into ATutor

Build support for IMS Tool Interoperability Producer into Boddington

Work on the Sakai Apple Desktop
[see attachment: "message0.html", size: 9918 bytes]


Attachments:

message0.html
http://collab.sakaiproject.org/access/content/attachment/9fcfa687-8f17-44c8-80e2-7ad2aebf91c8/message0.html

----------------------
This automatic notification message was sent by Sakai Collab 
(http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace > Preferences.