ooc-dev team mailing list archive

[Amos Wenger <amoswenger@xxxxxxxxx>]

Hi,

I definitely think we should apply. And by we, I mean me (you guys probably
either 1) don't have enough ooc experience to be mentors 2) prefer to be
paid students, right?).

>From the recent IRC discussions, here are a few suggestions for project
ideas.

   - *Text manipulation*: Add full UTF-8 support, integrate regex tighter
   (named captures, etc.), formatted strings (e.g. "Hi, #{name} println()")
   - *Web* framework, build on Josh's work, provide solid implementations
   with a pure ooc HTTP server?
   - *Crypto* support? digests,e.g. MD5/SHA1 and friends, and then others.
   Mostly a matter of finding public domain/BSD/MIT C libs and binding to them.
   - *User interface* lib in pure ooc, text rendering (freetype2?), event
   handling, etc.
   - *IDE* support, tightly integrated with rock, with good highlighting,
   incremental compilation, auto-complete.. yet lightweight
   - Complete the *documentation* of the SDK, review the design, ensure
   consistency, see and document the 'big picture'
   - Write a *manual* for the language
   - Polish reincarnate+nirvana+meatshop, our packaging system (courtesy of
   Fred)

More into compiler work:

   - Alternative rock *backends* (assembly, generate Makefiles?)
   - Implement *methodMissing*, fieldMissing
   - Implement *properties* in rock
   - Improve *error detection and reporting* in rock (errors, warnings)
   - Implement *closures* fully, with yajit for baking-to-C-functions
   - *Meta-programming* in rock (macros exploring+modifying the AST)
   - *Introspection* in rock, retrieving operator overloads at runtime, etc.
   - *Backport* rock features into j/ooc (meta-classes, interfaces, other
   things)

Some may take a few weeks, other could last for years (e.g. IDE), the point
is, as Josh said, keeping people busy for the full 3 months.

Also, some items on the list above require intimate knowledge of rock
internals, etc. As a mentor, I'll obviously make my best to answer
as precisely as possible every engaged student's questions.

Otherwise, I recommend everyone in the ooc community to read the Advice for
GSoC mentors page<http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors>.
It provides guidance for everyone,
and gives hints on how to organize ourselves. Especially, we should write &
publish a document on how we'll handle GSoC, e.g. who
students will be referring to, the resources they have available, licensing
issues, IRC/the mailing list, etc. etc.

Comments welcome, as always

Amos Wenger, aka nddrylliog

On Wed, Mar 3, 2010 at 12:42 AM, Josh Roesslein <jroesslein@xxxxxxxxx>wrote:

> Hello,
>
> Starting soon this month is the Google Summer of Code (GSOC). Google is
> sponsoring students to code on
> open source projects and get paid ($5000) for doing so! As well each
> mentoring organization also gets $500.
>
> I think this is a great chance to draw in new talents to the world of ooc.
> It is also a great opportunity for students
> wanting to learn more about compiler development. This is a great chance to
> gain some full time coders to help further
> the development of Rock.
>
> Part of the application process involves submitting a list of project
> ideas. Please reply back with any ideas you might have.
> Ideas should be able to keep the student busy for the whole coding period
> (about 3 months). We can also combine smaller
> tasks together.
>
> So do you guys think this is something ooc should pursue? If you are a
> student I highly suggest you look into applying as well.
>
> Josh
>
> Google Summer of Code Homepage:
> http://socghop.appspot.com/gsoc/program/show/google/gsoc2010
> FAQ:
> http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs
> Organization Application Requirements:
> http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_apply
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ooc-dev<https://launchpad.net/%7Eooc-dev>
> Post to     : ooc-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ooc-dev<https://launchpad.net/%7Eooc-dev>
> More help   : https://help.launchpad.net/ListHelp
>
>