[Building Sakai] Google Summer of Code is on again

[Zach A. Thomas]

I agree with Matthew that these are probably too ambitious for a single summer project, but maybe some subset is reasonable.

I wrote a Sakai plugin for grails back in 2009, so I'd be happy to see that work go forward again.
http://grails.org/plugin/sakai

This is the first year I've participated in any GSOC activities, so I'm flexible as to the makeup of the projects.

Zach
On Mar 29, 2013, at 3:44 PM, Carl Hall <carl at hallwaytech.com> wrote:

> Hey Matthew,
> 
> The ideas list is a living document for the next week, so please feel free to add project ideas that you feel are more achievable as a summer project.  I've been beating the drum on this to very little response, so I greatly welcome any suggested projects before we nail down summer goals (assuming we're accepted to GSoC).  Better Grails & JRuby integrations have been discussed at conferences and would make great projects; again, please submit your ideas.
> 
> The GSoC process is very flexible and it's up to the student(s) and mentor(s) to determine deliverables for the summer.  While Zach's projects may be seen as lofty, they allow students to perform discovery in directed areas.  It is up to the student to submit what project they would like to work on.  Our ideas are just suggestions to give students a jumping off point.
> 
> 
> On Fri, Mar 29, 2013 at 1:03 PM, Matthew Jones <matthew at longsight.com> wrote:
> This is a cool list, but I feel like some of these projects as-is would be impossible for a typical GSoC student. AFIAK the CLE hasn't gotten one line of code committed from GSoC, so if a project is accepted it would be useful if the goals within these ideas were achievable. 
> 
> For instance for #2 eliminating state from the entire code base entirely isn't achievable in a summer project, but doing it from a few key tools may be. When Unicon worked on Terracotta a few years ago they documented how to clean up the announcements tool, but some of the heavier tools would be more work. (https://confluence.sakaiproject.org/display/TERRA/How+to+Terracotta+Cluster+Enable+a+Sakai+Tool). It would be great for many reasons for sure if this work was built upon again.
> 
> Also in #1, I don't think we can have an easy package manager without better backward compatibility guidelines and work on that. On Android, there is a lot of work a developer has to do to make their app compatible across all versions, but they've also got thousands of developers (we have a dozen?) [1]. And all of the developers do it so they can make sure to sell their app to the most amount of people running all of the devices. For instance you can't take trunk of a tool and drop it into 2.8 or often even 2.9. None of the tools detect what version they're running in or do any reflection to workaround api changes. Things like kernel-util have gotten better (much of it moved into a service rather than the api) but the component manager without architecture changes discussed 5 years ago by Ian and Antranig [2] (implemented in the original OAE) this doesn't seem *entirely* possible? There might be some creative workarounds though to improve development, like making components re-loadable (something I've discussed with Noah) but this would *really* only benefit developers and a full Sakai on an SSD does start up in around 30 seconds now. ;)
> 
> I'd like to see the work on Grails/JRuby picked back up again. I know Noah experimented a little on that too but don't remember him ever writing up anything about it? Writing a full tool using the "standard Sakai workflow" is for sure a turnoff.
> 
> [1] http://developer.android.com/training/backward-compatible-ui/index.html
> [2] https://confluence.sakaiproject.org/display/SAKDEV/Component+Manager+Requirements
> 
> 
> On Fri, Mar 29, 2013 at 3:29 PM, Carl Hall <carl at hallwaytech.com> wrote:
> Our application is in.  Thanks to Zach for adding some really sweet projects to our ideas page[1].  Please feel free to add more projects over the next few days.  Organizations will be notified of acceptance/rejection in about a week (April 8).
> 
> 1 https://confluence.sakaiproject.org/display/MGT/Google+Summer+of+Code+2013+ideas+list
> 
> 
> On Wed, Mar 27, 2013 at 12:49 PM, Carl Hall <carl at hallwaytech.com> wrote:
> Just a friendly reminder that we have about 48 hours to get everything together for our application to Google.  The ideas list and application template are available[1][2].  Please add your ideas or list yourself as a mentor.  Thanks!
> 
> 1 https://confluence.sakaiproject.org/display/MGT/Google+Summer+of+Code+2013+ideas+list
> 2 https://confluence.sakaiproject.org/display/MGT/GSoC+2013+application+template
> 
> 
> On Mon, Mar 25, 2013 at 11:44 AM, Carl Hall <carl at hallwaytech.com> wrote:
> The 2013 Sakai GSoC information pages have been posted[1][2] as we ready ourselves to apply to Google.  Please take a look at these for any updates or corrections.  If you have any ideas or would like to be a mentor, please add your details to the ideas list[1].
> 
> Thanks to everyone for helping us prepare for GSoC!
> 
> 
> 1 https://confluence.sakaiproject.org/display/MGT/Google+Summer+of+Code+2013+ideas+list
> 2 https://confluence.sakaiproject.org/display/MGT/GSoC+2013+application+template
> 
> 
> On Mon, Mar 18, 2013 at 1:37 PM, Carl Hall <carl at hallwaytech.com> wrote:
> And now registration for mentoring organizations has opened (see email below).  I wouldn't mind being the org admin again if there are no objections.  I can get the organization application submitted by the deadline.  Google usually asks for how many slots we would like.  Have there been any proposed projects or ideas collected?  I'll dig up our old confluence page for this to get the ball rolling.
> 
> Everyone, please toss in your ideas for projects or project areas.  It's great to have public brainstorming to help us drive interest to the right areas of the application.  It is the "Summer of Code", so Google requires that the project produce actual code but this is a beautifully broad opening for us.
> 
> We need ideas as well as mentors and everyone is invited to participate.  Please let us know if you'd like to mentor and/or have ideas.  The two are not mutually exclusive or inclusive.  I look forward to your input!
> 
> 
> -----
> Hi all,
> 
> We're pleased to announce that applications for mentoring organizations for Google Summer of Code 2013 are now being accepted [1]. If you'd like to apply to be a mentoring organization you can do so via Melange [2]. If you have questions about how to use Melange, please see our User's Guide [3].
> 
> Please note that the application period [4] closes on 29 March at 19:00 UTC [5]. We will not accept any late applications for any reason.
> 
> [1] - http://google-opensource.blogspot.com/2013/03/mentoring-organization-applications-now.html
> [2] - http://www.google-melange.com
> [3] - http://en.flossmanuals.net/melange/
> [4] - http://www.google-melange.com/gsoc/events/google/gsoc2013
> [5] - http://goo.gl/xmQMJ
> 
> 
> On Tue, Feb 12, 2013 at 3:23 AM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> FYI:
> 
> We're pleased to announce that Google Summer of Code will be happening for its ninth year this year. Please check out the blog post [1] about the program and read the FAQs [2] and Timeline [3] on Melange for more information. 
> 
> [1] - http://google-opensource.blogspot.com/2013/02/flip-bits-not-burgers-google-summer-of.html
> [2] - http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page
> [3] - http://www.google-melange.com/gsoc/events/google/gsoc2013
> 
> Anyone interested in participating this year, as either mentors or students? What about running our efforts? Ideas for projects? Would be good to get this one planned out early.
> 
> cheers,
> Steve
> 
> _______________________________________________
> 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"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130329/17e2b202/attachment.html