I'm amused by Alex's way of keeping students interested after a
project ends, by bribing them with gigs!
Um, looking at the Pd page for this Thor linked to, it's clear that
they're much more advanced here, with multiple proposals. I'm sure
the SC community could come up with a few, but time is the real
killer here.
I just checked the GSOC details again. Mentoring applications happen
between 9 and 13 March, ie next week. The student applications (if
you get that far) happen with decisions expected to be resolved over
Easter. So I can tell you now I'm not available to be an admin from
that timing alone. There is also the fact that TOPLAP is not an open
source project in itself; SC, ChucK etc are, but then they'd apply
independently. There also seem to be assumptions on when students can
code based on US terms (they start in May!), and tax forms to fill
out. So whilst Alex has made a good start at the questions, not
convinced... perhaps working on Netclock doesn't need a student.
From the SC side, happy to be involved, particularly for 2010, but
couldn't cope with doing much for next week.
best,
N
On 5 Mar 2009, at 18:38, Artem Baguinski wrote:
> On Thu, Mar 5, 2009 at 3:28 PM, gabor papp <gabor.lists_at_mndl.hu>
> wrote:
>>> The question is do any supercollider/chuck/fluxus people have
>>> some ideas
>>> to contribute and the time to do so? It's kind of all or nothing I
>>> think.
>> i'm in for fluxus. i don't have much time these days, but i think
>> it's
>> really important to apply. we have a list of planned tasks for fluxus
>> here: http://savannah.nongnu.org/task/?group=fluxus
>> most of them are probably not big enough for a student project,
>> but they
>> can be used as a basis. some of them can fit better like
>> improving the
>> audio system to have more than 16 fft bins, and to add beat
>> detection.
>
> I would like to mentor improving the editor (related task:
> http://savannah.nongnu.org/task/?8316), REPL and context driven help
> by cleverly integrating a toolkit / into a toolkit.
>
> I think this task is stretchable enough to fill a summer: think
> auto-complete / API reference as you type, cut and paste with other
> applications, REPL/error stream on the same screen as the script
> editor etc and all that without cluttering the rendering window with
> "widgets" and without breaking record/playback functionality.
>
> I have my ideas how this could be approached but I'm open for
> discussion.
>
> --
> cheers,
> artm
>
> http://lab.v2.nl/
Received on Thu Mar 05 2009 - 21:29:29 GMT