[Building Sakai] Google Summer of Code is on again

[Adrian Fish]

Could we big CLE up a bit more on the confluence page? The way the page is
written just makes CLE sound like a dinosaur and nobody is going to want to
write GSOC code for it.

Cheers,
Adrian.


On 29 March 2013 22:53, Matthew Jones <matthew at longsight.com> wrote:

> This sounds better to me now. The Dave Adams hitlist is pretty serious
> taken as-is. I just didn't expect that someone new to the project (GSoC
> student) would have much luck where Ian, Antranig, Horwitz and Whyte
> (Project #1), Dan McCallum (Project #2), and Zack/Githens/Botimer (Project
> #3) put a lot of time in and really don't have much recent to show for it.
> (At least not in core Sakai) I know there has to be some code produced, so
> investigate and improve upon what's there. Sometimes all it takes is a
> little push to get the ball rolling that none of us have the time for.
>
> @Carl I didn't respond initially because I didn't want to be an
> asynchronous mentor to a GSoC student. I know in the past the vast majority
> of students have been from India or other parts of Asia making coordination
> extra difficult. I've mentored students at local universities with projects
> that have turned out great and our best project (Lessons) was from a
> student Charles Hedrick mentored, but I believe that Eric was also local to
> Chuck. I'd be happy to help out someone from any school in Central Florida
> once a week, but I didn't think you could make that restriction on GSoC
> students. ;)
>
> @Zach I attended that Grails session back in 2009 and was really excited
> by it. I never ended up writing anything in Grails, though did a few
> console apps in Groovy and a few webapps in ZK that almost made production.
> Specifically it was a project to improve some of the existing and
> non-existing admin tools, but I just never had the time to finish it. I'm
> happy to see you involved on the list again and I think a project like #3
> would have the best chance of being accomplished.
>
> I think idea #4 would have to be expanded upon but it sounds kind of like
> an item (that I don't see on Dave's list) concerning a background
> processing server for long running jobs. Some standard way that an internal
> or external service can make a request, that it might not have any
> expectation of completing for awhile, then be notified when it is
> completed.
>
>
>
>
> On Fri, Mar 29, 2013 at 5:43 PM, Aaron Zeckoski <azeckoski at unicon.net>wrote:
>
>> On Fri, Mar 29, 2013 at 4:30 PM, Matthew Jones <matthew at longsight.com>
>> wrote:
>> > The 3 things mentioned for #2 (elasticity, failover and rolling
>> updates) are
>> > nice to have but rarely a problem in practice. Most clients are okay
>> with
>>
>> I strongly agree with that point.
>>
>> I also think there were some solid options on Dave Adams hitlist that
>> are a lot more bitesized and maybe better options.
>>
>> That said, students can provide a lot of value in exploring options
>> and testing proof of concept (even if the code they produce is
>> questionable). So maybe a slight scope adjustment to "investigate"
>> some of these things would be another option.
>>
>> -AZ
>>
>>
>>
>>
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>
>
>
> _______________________________________________
> 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/91f65334/attachment.html