[Scons-dev] GSOC this year?
Kenny, Jason L
jason.l.kenny at intel.com
Fri Mar 29 12:03:57 EDT 2013
I tried to add to the section for Parts some idea that should be good enough in Parts to move to SCons. I tried to keep the items mostly infrastructure related, where each items has a little work to move to SCons and has some possible improvements that could be made.
Jason
-----Original Message-----
From: scons-dev-bounces at scons.org [mailto:scons-dev-bounces at scons.org] On Behalf Of William Deegan
Sent: Thursday, March 28, 2013 3:40 PM
To: SCons developer list
Subject: Re: [Scons-dev] GSOC this year?
We need to submit by end of day tomorrow.
So of you can take a few minutes and flesh out something on the ideas page, that would be awesome.
https://docs.google.com/a/baddogconsulting.com/document/d/1FoRgJD23UDJ1Hk4P5xE3dCIU8AIgUJ3qojCMSgEkbOU/edit
-Bill
On Mar 28, 2013, at 1:34 PM, "Kenny, Jason L" <jason.l.kenny at intel.com> wrote:
> This could be possible.
>
> I can think of about 4 -5 item that would might work.
>
> Jason
>
> -----Original Message-----
> From: scons-dev-bounces at scons.org [mailto:scons-dev-bounces at scons.org] On Behalf Of William Deegan
> Sent: Thursday, March 28, 2013 1:52 PM
> To: SCons developer list
> Subject: Re: [Scons-dev] GSOC this year?
>
> Jason,
>
> Perhaps a GSoC student can help migrate some of your monkey patches from parts into the core where we can agree that such wouldn't be too complex for a student to understand?
>
> -Bill
> On Mar 28, 2013, at 11:50 AM, William Deegan <bill at baddogconsulting.com> wrote:
>
>> All,
>>
>> We need to turn in the proposal by tomorrow.
>> I've put up a google doc for the proposal here:
>> https://docs.google.com/document/d/1wOQGgUfdLlY355IC24YyB74i5Kg7uw-35A1Lsdos5aE/edit?usp=sharing
>>
>> I've copied/pasted from the FAQ on what we should put in our proposal:
>> http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page#1._How_does_a_mentoring_organization
>>
>>
>> So for mentors we have:
>> * Myself
>> * Russel Winder
>> * Gary O (as a backup only)
>>
>> For projects:
>> * ? Please fill in on the doc.
>>
>> I'm looking at Anatoly's list below and trying to figure out if this is reasonable for a student to complete in 12 weeks and/or how to partition the tasks below into chunks which are sized for completion.
>>
>> Here's some other thoughts I have:
>> * Change SCons code to be runnable on py2.7 and py3.0
>> * Get SCons to work better/at all on cygwin
>> * Change code to use more modern constructs (slots, generators/iterators)
>> * Improve packaging (get it into pypy and make it work with python setup.py and also in virtualenvs)
>>
>> -Bill
>>
>> On Mar 28, 2013, at 10:37 AM, William Deegan <bill at baddogconsulting.com> wrote:
>>
>>> Russel,
>>>
>>> Today's the last day to file.
>>> I'll go ahead and do that.
>>>
>>> -Bill
>>> On Mar 28, 2013, at 4:08 AM, Russel Winder <russel at winder.org.uk> wrote:
>>>
>>>> Bill,
>>>>
>>>> Did you put an entry in? I can be a mentor if you would like me to.
>>>>
>>>> --
>>>> Russel.
>>>> =============================================================================
>>>> Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder at ekiga.net
>>>> 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel at winder.org.uk
>>>> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
>>>> _______________________________________________
>>>> Scons-dev mailing list
>>>> Scons-dev at scons.org
>>>> http://two.pairlist.net/mailman/listinfo/scons-dev
>>>
>>
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev
_______________________________________________
Scons-dev mailing list
Scons-dev at scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev
More information about the Scons-dev
mailing list